Back to blog

OSSeva Blog

Operations

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

Randall McClureUpdated 10 min read

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, 8.x and 9.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.

For the OSSeva offer itself, Redis extended support covers patched Redis 6.2 and 7.0 builds, Redis 7.2 and Valkey. Running Redis from the Ubuntu archive? Ubuntu Pro compared with OSSeva shows which Redis version each LTS release carries and what Pro covers.

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.

In short:

  • Choose the engine first: Valkey is the BSD-licensed, Linux Foundation fork of Redis 7.2.4; Redis 7.4 and later carries source-available licences, with AGPLv3 added in Redis 8.
  • Self-managed estates buy support from Percona, Canonical, Redis Ltd or OSSeva; managed services patch the engine only inside their own platform.
  • Failover and backup design stays with you on self-managed clusters, while ElastiCache, MemoryDB, Memorystore and Aiven build it into the service.
  • OSSeva is not the right fit for every case. The section on when OSSeva is not the right fit says when to pick someone else.

OSSeva publishes this list and is one of the eight providers in it. Every other provider fact comes from that provider's own site, checked 8 November 2026. OSSeva's row comes from our own Redis and Valkey page.

Running Redis in production? OSSeva patches and supports it, end-of-life versions included.

Redis extended support: what is covered

Best for: which provider fits which situation

ProviderBest forVersions coveredSupport model
PerconaA 24x7 support desk for Redis and Valkey, especially if you already buy Percona support for other databasesRedis and Valkey; Percona publishes no version listSupport subscription, plus Percona Packages for Valkey
Canonical (Ubuntu Pro)Redis or Valkey that you install from Ubuntu's own packagesValkey 7.2, for which Canonical offers up to 15 years of security maintenance; the Redis version each Ubuntu release ships (7.0.15 on 24.04 LTS)Ubuntu Pro subscription priced per node per year; 24/7/365 support with a one-hour response for the most critical issues
Redis LtdA commercial agreement with the company that writes Redis, for Redis Software or Redis CloudRedis Software cluster versions 7.4 to 8.2 (7.4 ends 30 November 2026)Support plans from Developer (Redis Cloud only) to Premium Enterprise; 24x7 on Business and above
OSSevaSelf-managed Redis 6.2 or 7.0 that cannot move yet, or a Redis to Valkey migration that should sit on one contractRedis 6.2.x, 7.0.x and 7.2.x; Valkey 7.2.x, 8.x and 9.xSubscription in three tiers (Patch, Assure, Operate), priced per cluster; Operate adds 24/7 monitoring and a 15-minute P1 response
Amazon ElastiCacheCaches that already run on AWSValkey, Redis OSS and Memcached; Redis OSS 4 and 5 in Extended Support since 1 February 2026, version 6 from 1 February 2027Managed service on AWS; Extended Support charged per node
Amazon MemoryDBA durable primary database on AWS rather than a cacheCompatible with Valkey and Redis OSSManaged service on AWS
Google Memorystore for ValkeyValkey on Google CloudValkey 7.2, 8.0, 9.0 and 9.1Managed service on Google Cloud
Aiven for ValkeyManaged Valkey that has to span more than one cloudValkey; its page names 9.1Managed service on AWS, Google Cloud and Azure; its page shows a 99.99% uptime SLA

How we chose these providers

This list is for someone who has to keep Redis or Valkey patched and supported in production. We kept a provider if it passed all three tests below. OSSeva had to pass the same ones.

Several products at once? End-of-life middleware patching providers compares Redis with Kafka, ZooKeeper and RabbitMQ coverage.

  1. A published Redis or Valkey offer. A page on the provider's own site that names Redis or Valkey and describes security patching, support or operation of it. A general claim about "open source databases" does not count.
  2. On sale on 8 November 2026. The offer is current, not an announcement or a retired product.
  3. Checkable by you. Every row rests on a public page listed under Sources. Where a provider publishes no version list, as Percona does not, the table says so and the gap becomes a question for the sales call. We did not fill it in.

Three limits apply. The managed services here are the ones on AWS and Google Cloud, plus Aiven, which spans several clouds. valkey.io lists more than twenty participants, among them Oracle Cloud Infrastructure, DigitalOcean and Alibaba Cloud, and we did not review each one. Redis Ltd appears for Redis Software and Redis Cloud only, because its support page does not mention community Redis Open Source. And we compared what providers publish. We did not run their services or audit their claims. The order of the rows carries no ranking, and a provider in the table is not a recommendation.

Redis and Valkey support providers compared

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

ProviderWhat it coversVersionsDelivery modelSelf-managed?
Percona24x7x365 support for Redis and Valkey, performance tuning, architecture design, health assessments and migration consulting. Ships Percona Packages for Valkey with LDAP authentication and ACLsRedis and Valkey; no version list published on its Valkey pageSupport subscription and packagesYes
Canonical (Ubuntu Pro)Security maintenance for the Redis packages in the Ubuntu archive, and for Valkey on Ubuntu 24.04 LTS, with 24/7/365 support and a one-hour response for the most critical issuesThe Redis version each Ubuntu release ships (7.0.15 on 24.04 LTS); Valkey 7.2 (7.2.5 when Canonical announced it); Canonical's Valkey page offers up to 15 years of support and security maintenanceAPT packages; Valkey also as snaps and container imagesYes, on Ubuntu
Redis LtdSupport plans for Redis Software (its self-managed commercial product) and Redis Cloud, with 24x7 coverage on the Business plan and aboveRedis Software cluster versions 7.4 to 8.2, which bundle Redis database versions 6.2 to 8.8Licensed software or managed cloudYes, for Redis Software
OSSevaBackported security fixes for community Redis under the original BSD licence, Valkey support, configuration audits and 24/7 operationsRedis 6.2.x, 7.0.x and 7.2.x; Valkey 7.2.x, 8.x and 9.xSigned Docker images, apt and yum packages; Bitnami-compatible imagesYes
Amazon ElastiCacheManaged Valkey and Redis OSS caches, with paid Extended Support for Redis OSS versions past standard supportValkey; Redis OSS 4 and 5 in Extended Support, 6 from 1 February 2027Managed service on AWSNo
Amazon MemoryDBDurable in-memory database compatible with Valkey and Redis OSS, with a Multi-AZ transaction logValkey and Redis OSS enginesManaged service on AWSNo
Google Memorystore for ValkeyFully managed Valkey, cluster mode enabled or disabledValkey 7.2, 8.0, 9.0 and 9.1Managed service on Google CloudNo
Aiven for ValkeyManaged BSD-licensed Valkey with automated setup, patching and scalingValkey; its page names 9.1Managed service on AWS, Google Cloud and AzureNo

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 its Valkey page now offers up to 15 years of support and security maintenance. 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, 8.x and 9.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.

What is Valkey, and how does it differ from Redis?

Valkey is an open source, BSD-licensed key-value datastore backed by the Linux Foundation. The Linux Foundation announced it on 28 March 2024 as a continuation of Redis 7.2.4, after the Redis licence change. Redis 7.4 and later moved to RSALv2 and SSPLv1, and Redis 8 added AGPLv3 as a further option.

Pick the engine before the provider, because the licence usually decides it. Redis up to and including 7.2 was BSD-3-Clause. Valkey stays BSD-3-Clause.

RedisValkey
LicenceBSD-3-Clause up to 7.2; RSALv2 and SSPLv1 from 7.4; AGPLv3 added as an option in Redis 8BSD-3-Clause
Origin and governanceDeveloped by Redis, which also sells Redis Software and Redis CloudAnnounced by the Linux Foundation on 28 March 2024, continuing Redis 7.2.4; the project says it is backed by the Linux Foundation
Releases on 8 November 2026Redis Open Source 8.10, 8.8, 8.6 and 8.4 (standard), 8.2 (extended, to 1 September 2030), 8.0 (to 1 December 2026), 7.4 and 7.2 (extended, to 1 December 2029), 6.2 (to 1 April 2027)Valkey 9.1.3 (26 October 2026), with 9.0.7, 8.1.11, 8.0.12 and 7.2.15 listed as the latest supported releases of earlier lines
Who supports itRedis Ltd for Redis Software and Redis Cloud; Percona, Canonical and OSSeva for community buildsPercona, Canonical and OSSeva for self-managed; ElastiCache, MemoryDB, Memorystore and Aiven as managed services
CompatibilityRedis Ltd modules such as Search and JSON are Redis productsCanonical describes Valkey 7.2 as the drop-in replacement for Redis 7.2; Percona describes Valkey as wire-compatible with Redis

What that means when you choose:

  • 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.

The engine decision has its own pages: Valkey vs Redis compares versions, compatibility and managed services, and the Redis licence change goes through the licences clause by clause.

How do high availability and disaster recovery differ across these options?

A managed service builds failover into the product: Multi-AZ replicas on ElastiCache, a Multi-AZ transaction log on MemoryDB, zone-distributed replicas on Memorystore. On a self-managed cluster you design high availability and disaster recovery yourself, so ask each support provider what it reviews.

OptionHigh availabilityDisaster recovery
Self-managed Redis or ValkeyReplication, with Sentinel for non-clustered setups and Cluster mode for sharding. Both projects document Sentinel as the high availability mechanism.Backups: both projects describe RDB snapshots as suited to disaster recovery, copied to another data centre or to Amazon S3.
Redis SoftwareReplication, clustering and rack-zone awarenessActive-Active databases, which Redis documents as providing disaster recovery
Amazon ElastiCacheMulti-AZ spreads replicas across Availability Zones and promotes a replica automatically if the primary failsGlobal Datastore replicates across AWS Regions, and a secondary cluster can be promoted
Amazon MemoryDBA Multi-AZ transactional log, which AWS says enables fast failover, database recovery and node restartsSame log; no separate disaster recovery claim on the page we reviewed
Google Memorystore for ValkeyEach shard can have replica nodes, distributed across zonesCross-region replication with secondary instances
Aiven for ValkeyReplication across availability zones and automatic failover, under a 99.99% uptime SLAPoint-in-time recovery and automatic backups
Percona, Canonical, OSSevaThese are support contracts, so the failover design stays with you. Percona lists architecture design among its services, OSSeva builds work with Cluster, Sentinel and standalone modes without changing replication topology, and Canonical delivers fixes through apt.Backup and restore stay your responsibility on self-managed clusters.

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.

When OSSeva is not the right fit

Pick another row of the table when one of these describes you:

  • Your cache already runs on ElastiCache, Memorystore or Aiven and you are happy there. The provider patches the engine inside its platform, and OSSeva's Redis and Valkey support is for clusters you run yourself.
  • You depend on Redis Ltd modules or want a commercial agreement with the company that writes Redis: that is Redis Software or Redis Cloud.
  • Your Redis or Valkey comes from Ubuntu's own packages and you want fixes through apt only: Canonical's Ubuntu Pro covers that.
  • You want one support desk across MySQL, PostgreSQL, MongoDB and Valkey: Percona sells all of them.
  • You run a line upstream still fixes, such as Redis 7.2, 7.4 or 8.x, and you can take new releases as they ship. Extended support only matters once a line stops getting upstream fixes.

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, 8.x and 9.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

What is Valkey, and how does it differ from Redis?

Valkey is an open source, BSD-licensed fork of Redis 7.2.4, announced by the Linux Foundation on 28 March 2024. Redis 7.4 and later is licensed under RSALv2 and SSPLv1, with AGPLv3 added as an option in Redis 8. Valkey keeps BSD-3-Clause and is governed under the Linux Foundation.

Do managed Redis and Valkey services cover high availability and disaster recovery?

Yes, in different ways. ElastiCache offers Multi-AZ failover and Global Datastore, MemoryDB uses a Multi-AZ transactional log, Memorystore for Valkey has zone-distributed replicas and cross-region replication, and Aiven lists automatic failover and point-in-time recovery. On self-managed clusters you build both yourself.

Which companies offer Valkey support?

For self-managed Valkey: Percona, Canonical (Ubuntu Pro, on Ubuntu 24.04 LTS) and OSSeva (Valkey 7.2, 8.x and 9.x). As managed services: Amazon ElastiCache and MemoryDB, Google Memorystore for Valkey and Aiven for Valkey. For a Valkey-only buyer's guide, with the community maintenance policy and what to ask a vendor, see Valkey enterprise support.

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, 8.x and 9.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.

Sources

All pages below were checked on 8 November 2026. No prices are quoted.

Tags

RedisValkeyExtended SupportAmazon ElastiCacheVendor Comparison

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call