Redis and Valkey Support Providers Compared (Self-Managed and Managed)

The short answer

For Redis or Valkey that you run yourself, four companies publish support: Percona (24x7 support for both, plus its own Valkey packages), Canonical (Ubuntu Pro security maintenance for the Redis and Valkey packages in Ubuntu), Redis Ltd (support for its commercial Redis Software, rather than community builds) and OSSeva (backported security fixes for Redis 6.2 and 7.0, and support for Redis 7.2 and Valkey 7.2 and 8.x). If you would rather not run the cluster at all, Amazon ElastiCache and MemoryDB, Google Memorystore for Valkey, Aiven for Valkey and Redis Cloud are managed services.

The split that matters is self-managed versus managed. A managed service patches the engine inside its own platform and does nothing for Redis on your own servers or Kubernetes. A self-managed support contract is the reverse.

Redis and Valkey support providers compared

Each row reflects what the vendor publishes on its own site as of 6 October 2026. Where a vendor does not list versions, the table says so instead of guessing.

Two of the self-managed options are narrower than they first look. Canonical maintains the package Ubuntu ships, so a Redis built from source or pulled from a Docker image is outside it. Redis Ltd's support plans name Redis Cloud and Redis Software; a cluster of community Redis OSS is a different product from the one those plans cover.

What each provider is best at

Percona

Percona is the broadest choice when you want a support desk for Valkey or Redis alongside MySQL, PostgreSQL or MongoDB. It says its team includes contributors to the Valkey project, it builds its own Valkey packages, and it offers migration consulting for teams moving from Redis. It does not publish a list of Redis versions it backports fixes into. Our OSSeva vs Percona comparison covers the overlap in more detail.

Canonical

If your Redis or Valkey comes from Ubuntu's own repositories, Ubuntu Pro is the low-friction option: fixes arrive through apt like any other package. Canonical announced Valkey coverage on Ubuntu 24.04 LTS in December 2024 and says Valkey 7.2.5 will be supported for up to 12 years. The limit is the version: you get the one your Ubuntu release ships, on Ubuntu.

Redis Ltd

Redis Ltd develops Redis and sells Redis Software, which runs on your infrastructure, and Redis Cloud, which it runs for you. It is the only route to the Redis Ltd product features and modules under a commercial agreement. Redis Software has its own lifecycle: cluster version 7.4 reaches end of life on 30 November 2026 and 8.0 on 31 July 2028.

OSSeva

OSSeva for Redis backports security fixes into Redis 6.2.x and 7.0.x, the BSD-licensed lines, with priority on the heap overflow and memory corruption bugs that recur in a server written in C. It also supports Redis 7.2.x and Valkey 7.2.x and 8.x, so one subscription covers an estate before, during and after a move to Valkey. Builds are binary-compatible with upstream and support Redis Cluster, Sentinel and standalone mode. The Assure tier adds ACL, persistence and TLS configuration reviews with SOC 2 and PCI DSS attestation material, and Operate adds 24/7 monitoring with a 15-minute P1 response.

The managed services

ElastiCache, MemoryDB, Memorystore and Aiven all patch the engine for you, and all now offer Valkey. If you are already on one of them and happy to stay, upgrading within the service is almost always simpler than moving to self-managed. None of them help with Redis you host yourself.

Redis or Valkey for new projects

The licence usually decides it. Redis up to and including 7.2 was BSD-3-Clause. Redis 7.4 moved to a dual RSALv2 and SSPLv1 licence, and Redis 8 added AGPLv3 as a third option. Valkey, the Linux Foundation fork of Redis 7.2, stays BSD-3-Clause.

• Choose Valkey if your organisation bans AGPL or you offer a hosted service built on the engine, or if you want foundation governance. ElastiCache, MemoryDB, Memorystore, Aiven, Percona, Canonical and OSSeva all support it.
• Choose Redis 8 if AGPLv3 is acceptable and you depend on Redis Ltd modules such as Redis Search or JSON, or you want a commercial agreement with the company that writes Redis.
• Check the release you pick. Redis 8.0 reaches end of life on 1 December 2026, while 8.2 is an extended release supported to 1 September 2030.

Our Valkey vs Redis comparison and guide to the Redis licence change go through the licences clause by clause.

Migrating from Redis to Valkey

Valkey keeps the RESP protocol and the core command set, so most clients connect unchanged. Help is available from several directions:

• On ElastiCache, AWS supports an in-place cross-engine upgrade from Redis OSS to Valkey that keeps the endpoint name.
• For self-managed clusters, Percona sells migration consulting, and OSSeva supports both the Redis line you leave and the Valkey line you land on.
• Doing it yourself, a replica-based cutover is the usual pattern: Valkey replicates from the Redis primary, you verify, then promote. Our step-by-step Redis to Valkey cutover covers it with rollback.

The hard cases are Redis Ltd modules. Valkey has its own module ecosystem, and an application built on Redis Search query syntax needs a rewrite of that layer, not a cutover.

What is cheaper than ElastiCache Extended Support for Redis OSS 6?

Usually, upgrading inside ElastiCache. Standard support for ElastiCache Redis OSS 6 ends on 31 January 2027. From 1 February 2027, caches still on version 6 are enrolled in Extended Support automatically and charged for it. The way the charge works explains the cheaper options:

• It is a premium on top of each node's on-demand hourly price, applied to every node in the cluster, replicas included.
• The premium rises in the third year, and Extended Support ends after three years.
• Reserved nodes do not reduce it: the premium is calculated on the on-demand price even when the node itself is reserved.
• It stops as soon as the cache runs an engine version in standard support, or is deleted.

The alternatives, roughly in order of how often they come out cheaper:

1. Upgrade to ElastiCache for Valkey. No Extended Support premium, and AWS lists Valkey node prices below Redis OSS. For most ElastiCache customers this is the cheapest route.
2. Upgrade to Redis OSS 7 on ElastiCache. Also removes the premium, if you want to stay on the Redis OSS engine.
3. Run Redis or Valkey yourself with a support subscription. This makes sense when the cache already runs, or could run, outside ElastiCache, or when an embedded product pins the version. OSSeva prices Redis per instance cluster rather than per node or per GB of memory, so the cost does not grow with node size the way the premium does. You take on hosting, failover and backups, so compare the whole bill, not only the support line.

Moving a cache off ElastiCache only to avoid the premium is rarely worth it on its own. Our ElastiCache Extended Support cost breakdown works through the dates and a worked example, and OSSeva vs ElastiCache Extended Support sets out when each fits.

Which upstream Redis lines still get fixes

Before buying support, check whether upstream still patches your line. Redis Ltd's version management page lists Redis Open Source 6.2 as supported to 1 April 2027, 7.2 and 7.4 to 1 December 2029, and 8.2 to 1 September 2030. Redis 7.0 is no longer on that list, so it gets no upstream fixes. Our Redis 6.2, Redis 7.0 and Redis 7.2 lifecycle pages track the dates, and Redis vulnerabilities by version lists what is open on each line.

Where OSSeva fits

OSSeva covers self-managed Redis and Valkey: patched Redis 6.2 and 7.0 builds under the BSD licence, Redis 7.2 and Valkey 7.2 and 8.x, delivered as GPG-signed Docker images and apt or yum packages. See Redis extended support for the offer and the extended support vendor roundup for how OSSeva compares across other technologies.

Frequently asked questions

Which companies offer Valkey support?

For self-managed Valkey: Percona, Canonical (Ubuntu Pro, on Ubuntu 24.04 LTS) and OSSeva (Valkey 7.2 and 8.x). As managed services: Amazon ElastiCache and MemoryDB, Google Memorystore for Valkey and Aiven for Valkey.

Which companies offer Redis support for self-managed clusters?

Percona offers 24x7 support for Redis. Canonical maintains the Redis packages in Ubuntu through Ubuntu Pro. Redis Ltd supports its commercial Redis Software. OSSeva ships patched builds of community Redis 6.2 and 7.0 and supports 7.2, with 24/7 operations on its Operate tier.

Who can help migrate from Redis to Valkey?

On ElastiCache, AWS supports an in-place upgrade to Valkey. For self-managed clusters, Percona offers migration consulting, and OSSeva supports both the Redis line you leave and Valkey 7.2 and 8.x. The usual method is a replica-based cutover.

How do Redis and Valkey support compare?

Valkey has more independent providers, because its BSD licence lets anyone package and host it. Redis 7.4 and later is supported commercially by Redis Ltd under its own licences. For the BSD-licensed Redis 6.2, 7.0 and 7.2, support comes from Percona, Canonical's Ubuntu packages and OSSeva.

What is cheaper than ElastiCache Extended Support for Redis 6?

Upgrading within ElastiCache, to Valkey or to Redis OSS 7, removes the premium entirely, and Valkey nodes are priced below Redis OSS. Running Redis or Valkey yourself with a per-cluster support subscription can cost less where the cache can live outside ElastiCache, once hosting and operations are counted.

Does Redis Ltd support community Redis OSS?

Its published support plans are for Redis Cloud and Redis Software. Redis Open Source lines get upstream fixes until their end-of-life dates, without a support contract.