On this page
Short answer
Yes, you can buy commercial support for open-source Redis without buying Redis Enterprise. Providers fall into four categories: the vendor (Redis Ltd), cloud providers with support bundled into a managed service, generalist open-source support firms, and independent Redis and Valkey specialists, and the best way to choose is to ask what happens during an incident.
Which companies offer Redis support? Four kinds of provider: the vendor (Redis Ltd), cloud providers that bundle support into a managed service (AWS, Azure, Aiven), open-source support firms (Percona, Ksolves, nextbrick), and independent Redis and Valkey specialists such as AceMQ.
You can buy commercial support for open-source Redis without buying Redis Enterprise. Those are two separate decisions, even though they usually arrive as one conversation. The four categories are genuinely different, and the right answer depends on what you need during an incident rather than on which has the largest logo. If Valkey is on the table, our valkey consulting page covers it.
Redis and Valkey support providers compared: coverage, SLA and price model
The Redis, Percona, Ksolves and nextbrick rows were checked against each provider's own public pages on 17 November 2026, and the AWS, Azure and Aiven rows on 22 October 2026. Prices are in US dollars; list prices vary by region and commitment, and response times are defined differently by each provider, so read the contract definition of P1 before comparing. Sources: Redis software support policy, Redis pricing, ElastiCache pricing, ElastiCache SLA, Azure Managed Redis, Azure retirement FAQ, Aiven for Valkey, Aiven support, Percona Valkey announcement, Percona Redis and Valkey support, Ksolves Redis support and nextbrick Redis support.
| Provider | Covers | Published SLA or response time | Price model | Not a fit for |
|---|---|---|---|---|
| AceMQ | Open-source Redis and Valkey wherever they run: self-managed, on-premises or cloud | 24/7, response targets from 15 minutes (by plan), written root cause analysis on every P1 | Quote on cluster count and SLA; no list price | Teams that want only a cloud provider's SLA on a managed cache |
| Redis Ltd | Paid Redis Software and Redis Cloud. The support policy covers paid Software, not Redis Open Source as a server | Software support: P1 response 8 business hours (Developer), 1 hour (Business), 30 minutes (Enterprise), 15 minutes (Premium Enterprise); 24x7 from Business. Redis Cloud Pro: up to 99.999% uptime | Redis Cloud Essentials from $0.007 an hour; Pro from $0.014 an hour with a $200 monthly minimum; Redis Software by annual plan, on request | Open-source Redis or Valkey that you run yourself |
| AWS ElastiCache | Managed Valkey and Redis OSS on AWS | Service credits start below 99.99% uptime for Multi-AZ and serverless, below 99.5% for single-AZ | Node-hours or serverless usage; Valkey is listed 20% lower than Redis OSS on node-based and 33% lower on serverless. Support comes through your AWS Support plan | Anything outside AWS, and application-level incidents |
| Azure Managed Redis | Managed Redis built on Redis Enterprise software, on Azure. Azure Cache for Redis Enterprise tiers retire on 31 March 2027, Basic, Standard and Premium on 30 September 2028 | Up to 99.99% uptime, higher with geo-replication; applies only to caches using replication | Per-SKU pricing on Azure's pricing page | Anything outside Azure |
| Aiven for Valkey | Managed Valkey service | 99.99% monthly uptime under Aiven's SLA | Free $0; Startup from $60 a month; Business from $70. Support: Advanced is the greater of $2,500 or 10% of monthly charges (30-minute P1), Premium the greater of $10,000 or 10% (response targets from 15 minutes, by plan) | Redis you run yourself; Basic and Essential support tiers have no P1 cover |
| Percona | Paid Valkey support since 4 February 2025 (Advanced and Premium tiers), Redis OSS health assessments and migration help | 24x7x365, response times "as fast as 15 minutes" | Quote only; no public price | Buyers who need a published price |
| Ksolves | Redis consulting and support in Standard, Advanced and Platinum plans, all 24x7; also advises on staying on Redis or moving to Valkey | Critical issues 30 minutes on every plan; 10, 15 or 25 tickets a year by plan | Custom; no public price | Teams that need unlimited tickets: plans carry 10, 15 or 25 a year |
| nextbrick | Redis Community, Redis Enterprise, Redis Stack, ElastiCache, Memorystore, Azure Cache for Redis and Redis on Kubernetes; Valkey is not mentioned on its page | Standard plan next business day, Professional 4-hour P1, Enterprise 1-hour P1 with 24/7/365 cover. The page also lists a 1-hour response for every Critical issue, so confirm which applies | No public price | Valkey estates (not mentioned on the page) |
How these Redis and Valkey support providers were chosen
We included the vendor, the cloud and managed-service providers, and the independent firms that publish a Redis or Valkey support offer on their own pages. We compare four things for each: what is covered, the published response time, the price model, and who it is not for. Every row uses only facts from the provider's own pages, read on the dates shown above. Where a page does not state a fact, the table says so instead of filling the gap. AceMQ is listed first because this is AceMQ's site: it is one of the providers compared, not a neutral party.
Provider notes: what each one is good for
- Redis Ltd. Its software support policy covers paid versions of Redis Software, with P1 response from 8 business hours (Developer) to 15 minutes (Premium Enterprise) and 24x7 cover from Business. Choose it if you run, or plan to run, Redis Software. The policy does not describe support for open-source Redis that you run yourself.
- Cloud and managed-service providers. AWS ElastiCache, Azure Managed Redis and Aiven publish uptime targets for their services, and support comes with the service. Choose one if you run on that platform and want a single bill; the support stops at the service boundary.
- nextbrick. Publishes Redis support plans from business hours to 24/7/365, across Redis Community, Redis Enterprise, Redis Stack and the main cloud services. It shows no prices and does not mention Valkey, and its page lists both a 1-hour and a 4-hour P1 response for different plans, so ask which applies.
- Ksolves. Three 24x7 plans (Standard, Advanced, Platinum) with a 30-minute critical response on each, 10, 15 or 25 tickets a year, and advice on whether to stay on Redis or move to Valkey. No public price.
- Percona. Valkey support in Advanced and Premium tiers, 24x7x365, with response times as fast as 15 minutes, plus Redis OSS health assessments and Valkey migration help. Percona announced it on 4 February 2025. No public price.
Where AceMQ is not the right fit
AceMQ is not the right fit in three cases. First, if you want only your cloud provider's SLA on a managed cache such as ElastiCache or Azure Managed Redis, that support already comes with the service. Second, if you need a fix to a product defect in Redis's commercial distribution, only the vendor can ship a patched binary; AceMQ works that escalation alongside you but cannot replace it. Third, if you need a published list price: AceMQ quotes by scope, at $24,000 to $72,000 a year (USD) for support, set by SLA, scope and deployment. Redis support from AceMQ covers open-source Redis and Valkey wherever they run.
Redis support pricing comparison
Redis support pricing splits three ways: percentage-of-spend fees on cloud services (AWS Support and Aiven take the greater of a minimum or a share of monthly charges), annual plans sold on request by the vendor, and quote-only contracts from independents such as Percona, Ksolves and AceMQ. Only the first group publishes numbers. The cost ranges behind each model are in Redis support pricing.
Best teams for Redis incident response
For a 3am Redis incident, compare the published first-response time and who answers, not the logo. Redis Ltd lists 30 minutes at Enterprise and 15 minutes at Premium Enterprise for paid Redis Software, Aiven 15 minutes at Premium, Percona as fast as 15 minutes and AceMQ with response targets from 15 minutes, by plan, Ksolves 30 minutes for critical issues; cloud providers cover their managed service only. Ask each one to name the escalation path in writing. AceMQ runs a single escalation path across Redis and RabbitMQ for a global quantitative trading firm, and describes its 24/7 Redis support scope in full.
The Four Categories
- The vendor. Redis Ltd supports its own commercial products, and its engineers know the code as well as anyone. The orientation is naturally toward its commercial offering, so if your intention is to stay on open-source Redis indefinitely, be clear about that early. The comparison is in Redis Enterprise support vs community.
- Cloud providers. If you run a managed Redis-compatible service, support comes with it and is generally good — within the boundary of that service. It stops where your application and your architecture begin, and it does not travel if you move platform.
- Generalist open-source support firms. Companies supporting dozens or hundreds of open-source packages, Redis among them. Genuinely useful when you want one contract covering a broad stack. The trade-off is depth: breadth that wide rarely comes with a Redis specialist on the rota.
- Independent specialists. Firms that support Redis and Valkey specifically, wherever you run them — on-premises, cloud, self-managed. Narrower coverage, deeper knowledge, and no incentive attached to which distribution you run.
| Provider | Best when | Trade-off |
|---|---|---|
| Redis Ltd (the vendor) | You are on, or moving to, its commercial products | Oriented toward its own offering |
| Cloud provider | You run their managed service and stay there | Stops at the service boundary; does not travel |
| Generalist open-source firm | You want one contract across a broad stack | Rarely a Redis specialist on the rota |
| Independent specialist | Self-managed, on-prem or multi-cloud | Narrower coverage, deeper knowledge |
The Question That Separates Them
Who answers at 3am, and how much Redis do they know?
That is the whole comparison, because Redis incidents are unforgiving of shallow familiarity. Memory pressure triggering eviction of data the application assumed was durable. A failover that half-completed and left clients pointed at a demoted node. Client-side timeouts against a server that is objectively healthy — an investigation that goes badly wrong if the first responder does not know to check connection pooling before the broker.
Those are covered in eviction policy, high availability patterns and client timeouts with a healthy server. An engineer who has seen each of them before resolves in an hour what a generalist works through overnight.
The Valkey Filter
A quick and genuinely revealing test: ask how the provider handles Valkey.
Since the fork, estates increasingly run one, the other, or both. The operational surface is largely shared — memory management, replication, failover, persistence, client behavior — so a provider who really knows Redis should support Valkey comfortably and be able to name specifically where behavior has diverged.
Two answers should give you pause. "We don't do Valkey" suggests the practice is tied to a vendor relationship rather than to the technology. "They're identical" is not true and gets less true with each release. The useful answer is a specific one. More detail in Valkey support options.
What Should Be in Scope
Break-fix alone is the least valuable half of a support contract. A useful one also includes:
- Incident response with a defined out-of-hours path and a named escalation — see Redis incident response.
- Memory and eviction design, before the eviction happens rather than after.
- Replication and failover architecture, including an actually-executed failover test rather than a documented one.
- Upgrade planning across versions and, where relevant, across forks.
- Periodic health checks — see what a Redis health check covers. These prevent incidents, which is why cheaper break-fix contracts often cost more overall.
AceMQ supports open-source Redis and Valkey in production, wherever you run them. See how we support Redis or get in touch.
This is step three of six in the Redis and Valkey support buyer's guide; for where a managed cache, Redis Cloud or self-managed Redis fits, see managed Redis options compared, and for Redis run by AceMQ on your own infrastructure, managed Redis services.
FAQ
Can I get commercial support for open-source Redis without buying Redis Enterprise?
Yes. Generalist open-source firms, database consultancies and independent specialists all support open-source Redis on infrastructure you already run.
What are the actual categories of provider?
The vendor, cloud providers bundling support with a managed service, generalist open-source support firms, and independent Redis and Valkey specialists.
How do I choose between them?
Ask who answers during an incident and how deep their Redis knowledge goes. Breadth and depth trade off directly.
Does the licensing change affect who can support Redis?
No. It changed distribution and prompted the Valkey fork; it did not restrict who may provide support services.
Should a provider support Valkey too?
Yes, and it is a good filter. They should support both and name specifically where the two have diverged — not refuse, and not claim they are identical.
What should be in scope?
Incident response with an out-of-hours path, memory and eviction design, replication and failover, upgrade planning, and periodic health checks.
Talk to an engineer
Need a hand with Redis?
Senior engineers who run it in production. Get a quote or a free consultation, no sales pitch.
Guides, comparisons and research
Go deeper on Redis
Guides
7- Redis in Production: The Reliability and Operations Guide
- How to Choose a Redis Support Provider (2026 Buyer's Guide)
- The Redis Backup and Disaster Recovery Guide
- Redis for AI: Vector Search, Agent Memory and MCP in Production
- Redis licensing explained
- Redis memory and latency field guide

