Which Companies Offer Valkey Support? Managed, Self-Hosted and Java Options

No single company owns Valkey, so there is no one vendor that sells "Valkey support". The project, run under the Linux Foundation, ships the releases and the security fixes. Commercial support comes from three kinds of company. Cloud providers such as AWS, Google Cloud, Oracle, Aiven, DigitalOcean and Heroku run Valkey for you. Vendors such as Percona, NetApp Instaclustr, Canonical and Red Hat support Valkey that you run yourself. And the maintainer of your client library supports the code inside your application. Microsoft is the notable absence: Azure has no first-party managed Valkey service.

This guide sets out who offers what as of October 2026, which versions each managed service runs, how long each release is supported, and the layer most lists leave out: the Java client. Redisson is our product and PRO includes commercial support, so that section says plainly where the other clients stand.

The Short Answer

Most of these names come from the Valkey project's participants page, where 18 participants list a Valkey offering, a few of them tools rather than services. The operating-system vendors and the client libraries are not on that page, so they are added here.

IONOS Cloud, Momento, Tencent Cloud, UpCloud, Vultr and anynines also list managed Valkey services on the participants page. AWS counts more than ten managed Valkey offerings from cloud providers, Alibaba's among them.

Support Comes in Layers, and No Vendor Covers All of Them

"Valkey support" can mean four different things, and a contract usually covers one or two of them:

• The engine. Bugs and security flaws in valkey-server itself. The project fixes them upstream. A managed provider applies the fix for you. A support vendor helps you apply it, and may backport it to an older version.
• Operations. Provisioning, replication, failover, backups, upgrades and monitoring. A managed service does this as part of the product. On your own clusters your team does it, with a support contract as the escalation path.
• Packages and images. The binary you install. Linux distributions build and patch their packages, and container images are maintained by whoever publishes them.
• The client. The library inside your application that discovers nodes, follows redirects and reconnects after a failover. Its maintainer supports it, not your cloud provider.

The boundaries matter when something breaks. If a failover completes on the server in seconds but your application fails for minutes, the provider's case will show a healthy cluster, and it will be right. The delay is in how your client reconnects, which is a question for the client's maintainer and for you. In the same way, a support vendor can diagnose your replication problem but cannot speed up a managed provider's patch rollout.

Managed Valkey Services

A managed service is the most common way to get Valkey support. The provider runs and patches the engine and takes cases about it under the support plan you already pay for. The services differ mainly in which versions they run and how fast they adopt new ones. For what managed hosting changes in your configuration, such as disabled commands, see managed Redis, which covers the Valkey services too.

Azure Has No Managed Valkey

Azure Managed Redis, generally available since May 2025, runs Redis Enterprise. It replaces Azure Cache for Redis, which retires in two stages: the Enterprise and Enterprise Flash tiers on 31 March 2027, and the Basic, Standard and Premium tiers on 30 September 2028. Neither product is Valkey, and Azure offers no first-party managed Valkey service.

Microsoft publishes a guide to deploying a Valkey cluster yourself on AKS, and it is explicit about support: "Software that you deploy is excluded from AKS service-level agreements, limited warranty, and Azure support." That leaves three routes for Valkey on Azure:

• Self-managed on AKS or virtual machines, with your own team on call. For an escalation path, add a support contract from Percona or NetApp Instaclustr, or from Canonical if your nodes run Ubuntu.
• A third-party managed platform. Aiven and NetApp Instaclustr both list Azure among the clouds they run on. Not every service is offered in every region, so confirm that Valkey is available in yours.
• Azure Managed Redis, if Redis Enterprise's licence and feature set suit you. This route means running Redis, and Valkey vs Redis compares the two.

Support Contracts for Valkey You Run Yourself

If you run Valkey on your own servers, in your own Kubernetes clusters or on cloud virtual machines, support comes from a contract. Four companies publish one.

Percona

Percona announced Valkey support on 4 February 2025 and sells it alongside Redis support. It covers on-premises, cloud and hybrid deployments with 24x7x365 access to specialists, in two tiers. Its datasheet puts the initial response to a severity 1 issue at 30 minutes on Advanced and 15 minutes on Premium. Percona also offers structured migration from Redis OSS to Valkey, with readiness assessments. It does not host Valkey, but its ExpertOps service puts Percona engineers in charge of the day-to-day operation of databases on your own infrastructure, Valkey included.

NetApp Instaclustr

Instaclustr added Valkey to its managed platform in November 2024 and offered enterprise support packages for Valkey from the start, with 24x7 coverage. It is the one company here that both hosts Valkey and supports clusters it does not host. Its platform covers AWS, Azure, Google Cloud and on-premises deployments.

Canonical

Canonical supports Valkey through Ubuntu Pro. It ships maintained Valkey as deb packages, snaps and OCI container images, including minimal chiselled images, with security maintenance for up to 15 years per release track. Support is 24/7 or weekday, and Canonical commits to a one-hour response for the most critical issues. When the offer launched in December 2024, the covered release was Valkey 7.2.5 on Ubuntu 24.04 LTS.

Red Hat

In RHEL 10, Valkey replaces Redis. RHEL 10.0 shipped Valkey 8.0 as the valkey package, and Red Hat publishes security advisories for it as it does for any other package. If your servers run RHEL 10, Valkey arrives with the operating system and is patched through the same channel.

Smaller consultancies also sell Valkey support, usually bundled with Redis. The checklist at the end of this guide applies to them as much as to the larger names.

Kubernetes Operators and Charts

On Kubernetes, the chart or operator needs support too. Bitnami's charts were a common way to deploy Valkey until Broadcom changed the catalog on 28 August 2025. The free tier now carries a limited set of images on the latest tag only, intended for development. Versioned tags moved to an unsupported legacy archive, and pinned versions in production need a paid Bitnami Secure Images subscription. If your Valkey came from a Bitnami chart, check which images it pulls today.

The Valkey project answered with an official Helm chart in January 2026, maintained in the valkey-io/valkey-helm repository. Its official operator is not there yet: the README says it "is in active development and not ready for production use." Third-party operators and platforms such as Solanica fill the gap, and whoever supports your cluster needs to support the chart or operator too. For the client side, see connecting Redisson to a Valkey cluster on Kubernetes.

How Long Each Valkey Version Is Supported

The project's own policy is the baseline every vendor works from. Valkey provides "patch releases for bug fixes and all security fixes, for 3 years from when a minor version was first released," and "extended security support for the latest minor version of each major version for 5 years." The latest stable release is always maintained.

Only the newest minor of each major gets the longer security window, so 8.0 and 9.0 lose all support on the day their maintenance ends, while 8.1 and 9.1 get two more years of security fixes. Valkey 7.2, the line that matches Redis 7.2.4, leaves maintenance in April 2027. Treat the 9.1 security date as provisional. The project picks the minor for extended security only "once the next major version has been launched," and with 9.2.0 in release candidate since 16 September 2026, that date may pass to 9.2. The latest stable release is 9.1.2.

Paid support can stretch these windows. Canonical's 15-year window, or a vendor that backports fixes, keeps a version covered long after upstream stops. A managed provider can move the other way: Aiven retired 9.0 more than two years before upstream will. For moving between versions without downtime, see how to upgrade a Valkey cluster with zero downtime.

Who Supports the Java Client?

A managed service's support stops at the endpoint. Everything between your code and that endpoint belongs to the client library: node discovery, MOVED and REDIRECT handling, reconnection after failover, and whether new Valkey features are reachable from Java at all. Support for that layer comes from whoever maintains the library.

Jedis and Lettuce still work against Valkey for the commands both engines share, because Valkey kept the protocol. But neither library's code mentions Valkey, and the features Valkey added are missing from both. They include the CLIENT CAPA REDIRECT handshake, added in Valkey 8.0, which lets a node send a client to the current primary after a failover in standalone and Sentinel deployments, and the availability-zone metadata that Valkey nodes report.

Redisson has added Valkey-specific support as the server features shipped:

Turning on the redirect capability is one line of configuration:

Config config = new Config();
// Valkey 8.0+: follow REDIRECT replies to the current primary after a failover
config.setValkeyCapabilities(EnumSet.of(ValkeyCapability.REDIRECT));
config.useSentinelServers()
      .setMasterName("mymaster")
      .addSentinelAddress("valkey://sentinel-1.example.com:26379");

RedissonClient redisson = Redisson.create(config);

Redisson PRO adds 24x7 technical support with an SLA and priority fixes delivered as intermediate releases. It covers the client, and the engine still needs its own support from your provider or one of the vendors above. The Valkey GLIDE to Redisson migration guide covers a move from GLIDE, the AZ affinity guide explains the 4.8.0 read modes, and Valkey Java clients surveys the wider field.

Frequently Asked Questions

Which Companies Offer Valkey Support?

Three groups. Cloud providers run Valkey as a managed service: AWS with ElastiCache and MemoryDB, Google Cloud with Memorystore for Valkey, Oracle with OCI Cache, and Aiven, DigitalOcean, Heroku, NetApp Instaclustr, IONOS, Momento, Tencent Cloud, UpCloud, Vultr and anynines. Percona, NetApp Instaclustr, Canonical and Red Hat support Valkey that you run yourself. Client libraries are supported by their maintainers, and Redisson PRO includes 24x7 support for the Java client.

Does Microsoft Azure Support Valkey?

Not as a managed service. Azure Managed Redis runs Redis Enterprise, and Azure Cache for Redis is being retired. Microsoft documents how to deploy Valkey yourself on AKS, but software you deploy is excluded from AKS service-level agreements and Azure support. On Azure, the options are self-managed Valkey with a third-party support contract, or a managed platform that runs on Azure, such as Aiven or NetApp Instaclustr.

Does AWS Support Valkey?

Yes. Amazon ElastiCache offers Valkey 7.2.6 through 9.1 and prices it below its other engines, and Amazon MemoryDB offers Valkey 7.2.6 and MemoryDB version 7.3. Support for both comes through your AWS support plan. It covers the managed cluster, not the client library in your application.

Is There Commercial Support for Self-Hosted Valkey?

Yes. Percona sells 24x7x365 Valkey support for on-premises, cloud and hybrid deployments, and NetApp Instaclustr sells enterprise support packages. Canonical supports Valkey on Ubuntu through Ubuntu Pro, with security maintenance for up to 15 years per release track. Red Hat ships and patches Valkey as part of RHEL 10.

How Long Is Each Valkey Version Supported?

The Valkey project maintains each minor version with bug and security fixes for three years from its first release, and gives the latest minor version of each major release five years of security fixes. Valkey 9.1, released in May 2026, is maintained until May 2029. Its listed security end of May 2031 is provisional, because the project confirms which 9.x minor gets the extended window only after the next major version launches. Managed providers set their own dates, which can be shorter.

Next Steps

If you are still choosing an engine, start with Valkey vs Redis. If you have chosen, migrating from Redis to Valkey in Java covers the move for each topology, managed services included. Redisson connects with the same API to every service here that exposes the full Valkey command set. The feature comparison lists what PRO adds to the community edition, support included, and a PRO trial lets you test it against your own cluster.