Valkey Enterprise Support: Options for Production Valkey

The short answer

Valkey has no vendor of its own. It is a BSD-licensed project backed by the Linux Foundation, and the community publishes a maintenance policy but sells nothing. Enterprise support comes from two directions: managed services such as Amazon ElastiCache, Google Memorystore for Valkey and Aiven, which run Valkey for you; and support subscriptions for Valkey you run yourself, from Percona, Canonical, OSSeva and others. Choose a managed service if you are happy for a cloud provider to run the cache. Choose a support subscription if Valkey runs on your own servers, VMs or Kubernetes, and check that the vendor covers the exact Valkey versions you run.

What the Valkey community already gives you

Valkey publishes its maintenance policy on valkey.io. The community provides bug and security fixes for each minor version for three years from its first release, and security fixes for the latest minor of each major version for five years. Only security issues the Technical Steering Committee believes are possible to exploit get patched, at its discretion.

Two dates in that table deserve a plan. Valkey 7.2, the line most Redis migrations landed on first, leaves maintenance on 16 April 2027 and gets security fixes only until 16 April 2029. Valkey 8.0 gets no extended security window at all: both its dates fall on 15 September 2027. Teams on 8.0 should plan the move to 8.1, which keeps security fixes until 31 March 2030, or to the 9.x line.

So most teams are not buying Valkey support to get patches that would otherwise not exist. They buy it for three other reasons: someone to call when production breaks, a written commitment on how fast fixes reach their servers, and audit evidence. A fourth reason is the estate around Valkey. Teams moving off Redis often still run Redis 6.2 or 7.0 beside it, and those lines are a different story.

Valkey commercial support options

valkey.io lists further participants, including Oracle Cloud Infrastructure, DigitalOcean, Alibaba Cloud and NetApp Instaclustr. Broadcom has also announced TrueSource Data Services covering Valkey alongside PostgreSQL, RabbitMQ and MySQL; see our TrueSource comparison.

Managed Valkey services

AWS describes ElastiCache for Valkey as "a serverless, fully managed caching service with full Valkey compatibility". It bills serverless caches for data stored and for processing units, and node-based caches by the hour, with one- and three-year reserved nodes. AWS prices Valkey below Redis OSS on ElastiCache, which is one reason many teams have switched engines inside the service. Google's Memorystore for Valkey supports Valkey 7.2, 8.0, 9.0 and 9.1. Aiven runs Valkey on AWS, Google Cloud and Azure and automates maintenance and patching.

These services are the simplest answer if you want the cache run for you. None of them helps with Valkey you run yourself, and each ties the cache to one provider's platform and version calendar.

Support for self-managed Valkey

Percona sells 24x7x365 support for Valkey and Redis from a team it says includes Valkey contributors, and ships Percona Packages for Valkey with LDAP authentication, ACLs and security scanning on each release. It suits teams that already buy Percona support for MySQL, PostgreSQL or MongoDB. Its Valkey page does not list the versions it covers, so ask.

Canonical covers Valkey through Ubuntu Pro. Its Valkey page offers up to 15 years of support and security maintenance, 24/7 support with a one-hour response for the most critical issues, and packages as debs, snaps and containers, priced per node per year. The coverage is for the Valkey that Ubuntu ships, on Ubuntu.

OSSeva supports Valkey 7.2.x and 8.x and keeps community Redis 6.2.x and 7.0.x patched under the original BSD licence. That combination is the point: one contract covers the Redis lines you are leaving and the Valkey lines you are moving to.

Managed or self-managed: how to decide

The choice usually comes down to where the applications that use the cache already run. If they live in one cloud account and your team would rather not run cache servers, a managed service removes most of the operational work, and its patching is part of the price. You accept the provider's version list, maintenance windows and limits on configuration.

Self-managed Valkey makes sense when the cache sits next to applications on your own hardware, when it runs on Kubernetes across several clouds, when data must stay in a particular place, or when you need settings a managed service does not expose. Then the work of patching, upgrades and incidents is yours, and a support subscription is how you share it. Many estates have both: managed caches for cloud-native services and self-managed clusters for everything else. A support vendor that works across bare metal, VMs and any Kubernetes covers the self-managed part wherever it lives.

How Valkey support is priced

The pricing models differ more than the services do:

• Usage-based for managed services: node-hours, or data stored and requests processed.
• Per node per year for Ubuntu Pro.
• Monthly plans for Aiven.
• Quoted per contract for Percona.
• Per cluster for OSSeva, so adding replicas or shards to a cluster does not change the support bill.

Caches tend to grow in node count faster than databases do, so the unit matters. Run your own numbers in the database support cost calculator.

What to ask a Valkey support vendor

• Which Valkey versions are covered, by number? Valkey 9.0 and 9.1 are current; not every vendor lists them.
• How do fixes reach my servers? Signed packages, container images, or advice to upgrade.
• What happens after the community's security date for the version I run?
• Are Redis lines covered too, if you still run Redis 6.2 or 7.0 during a migration?
• Which deployment modes: standalone, Sentinel and cluster mode.
• What audit evidence you will get: SBOMs, signed builds and CVE remediation records.

Coming from Redis Enterprise

Teams that move to Valkey from Redis Software (Redis Enterprise) change more than their servers. Redis Ltd's support plans cover Redis Cloud and Redis Software, not Valkey, so the support contract has to change too. If you depend on Redis Ltd modules such as Redis Search, plan for a rewrite of that layer; the rest of the command set carries over. Our Redis Enterprise comparison, Redis Enterprise alternatives, Valkey vs Redis and Redis to Valkey cutover guide cover the move.

Which option fits

• A managed service if you want the cache run for you on one cloud and accept its version calendar.
• Percona if Valkey sits beside databases you already support through Percona.
• Canonical if your Valkey comes from Ubuntu's own packages and you want long security maintenance on Ubuntu.
• OSSeva if you run Valkey 7.2 or 8.x yourself, still have Redis 6.2 or 7.0 to keep patched, or want Valkey on the same contract as PostgreSQL, MySQL, Kafka and RabbitMQ.

Where OSSeva fits

OSSeva for Redis and Valkey supports Valkey 7.2.x and 8.x and ships CVE-patched Redis 6.2.x and 7.0.x builds under the BSD licence, binary-compatible with upstream, for standalone, Sentinel and cluster mode. OSSeva Patch delivers signed artifacts through Docker, apt and yum. OSSeva Assure adds ACL, persistence and TLS reviews and a SOC 2 and PCI DSS attestation package. OSSeva Operate adds 24/7 monitoring, a 15-minute P1 response and a named senior engineer. If you run Valkey 9.x, ask us on the discovery call how we cover it before you sign. Pricing is per cluster, not per GB of memory; book a discovery call for a quote. See Redis and Valkey support providers compared and Redis extended support.

Frequently asked questions

Does Valkey have enterprise support?

Not from the project itself. Valkey is a Linux Foundation project that publishes a maintenance policy but sells nothing. Enterprise support comes from managed services such as ElastiCache, Memorystore and Aiven, and from support vendors such as Percona, Canonical and OSSeva for self-managed Valkey.

Who offers Valkey commercial support?

For self-managed Valkey: Percona, Canonical through Ubuntu Pro, and OSSeva, among others listed as participants on valkey.io. For managed Valkey: AWS, Google Cloud, Aiven, Oracle Cloud Infrastructure and other cloud providers.

Is Valkey free for commercial use?

Yes. Valkey is licensed under the BSD 3-Clause licence, which permits commercial use, including offering it as a hosted service.

How long is each Valkey version supported?

Three years of bug and security fixes for each minor version, and five years of security fixes for the latest minor of each major. Valkey 8.1 gets security fixes to 31 March 2030 and 9.1 to 19 May 2031.

Does Redis Ltd support Valkey?

No. Redis Ltd's support plans cover Redis Cloud and Redis Software. Valkey support comes from the providers above.

Is Valkey ready for production?

AWS, Google Cloud and Aiven all run it as a managed service, and the project publishes multi-year maintenance dates. Test your own clients and commands, especially if you use Redis Ltd modules, which Valkey does not include.

Is Valkey cheaper than Redis OSS on ElastiCache?

AWS prices Valkey below Redis OSS on ElastiCache, which is one reason many teams switch engines inside the service. Check the current ElastiCache pricing page for your region and node types.

Can one contract cover Redis and Valkey during a migration?

Yes, with a vendor that supports both. OSSeva covers community Redis 6.2 and 7.0 and Valkey 7.2 and 8.x under one contract, so the cutover does not need two vendors.