24/7 Valkey Support with a 15-Minute Emergency SLA

It depends where Valkey runs. AWS supports ElastiCache and MemoryDB for Valkey, Google Cloud supports Memorystore for Valkey, and other hosting providers support their own managed services. For self-managed, Kubernetes and on-premises Valkey, support comes from independent providers. AceMQ covers Valkey and Redis under one 24/7 contract with a 15-minute emergency SLA. The Linux Foundation project offers community channels, not a support contract.

Valkey is an open-source, in-memory key-value data store used as a cache, session store, message broker and primary database, and it speaks the same protocol as Redis, so existing Redis clients connect to it unchanged. It exists because Redis changed its licence in 2024: the Linux Foundation forked Redis 7.2.4 to keep a BSD-licensed version, with backing from AWS, Google Cloud and Oracle. Teams adopt it to avoid licensing changes, because AWS ElastiCache and Google Cloud Memorystore now offer it as a managed engine, or because new releases such as Valkey 8 and 9 add threading and cluster improvements.

24/7 incident response with a 15-minute SLA for P1 incidents, a written root cause analysis for every P1, upgrades and performance tuning, cluster and high availability operations, Redis to Valkey migration, and security patching advice for the versions you run. Every ticket goes to a named senior engineer. There is no per-incident charge.

Yes. The Linux Foundation launched Valkey in March 2024 as a fork of Redis 7.2.4, and it remains under the BSD 3-clause licence. It is developed by a community of contributors under the project's technical steering committee rather than by one company.

The project currently maintains Valkey 7.2, 8.0, 8.1, 9.0 and 9.1, each with three years of maintenance support from its first release, and extended security support for the last minor version of each major line. AceMQ supports all of them, and older 7.2 and 8.x deployments can get backported CVE fixes through OSSeva while an upgrade is planned.

Yes, for everything the cloud provider does not own. AWS and Google run the nodes, but key design, eviction and memory policy, client configuration, cluster sizing and most incident causes remain yours. We work alongside the provider's support on those, and on migrations into or out of the managed service.

Yes. Teams running Broadcom's Tanzu for Valkey get the same 24/7 engineering support, and as Broadcom's Expert Advantage Partner of the Year for the Americas we also handle Tanzu subscriptions. The details are on our Tanzu Valkey support page.

Usually, yes. We start with a compatibility review of commands, Lua scripts, modules and client library versions, because that is where problems appear, not in the data. The move then runs by replication or RDB transfer with key-level validation and a shadowed cutover with a rehearsed rollback. Workloads that depend on Redis modules or commands added after the fork are the exception, and the review finds them before the cutover does.

Yes. Managed Valkey is part of our managed Redis service: AceMQ operates Valkey on your own infrastructure, including monitoring, patching, upgrades, failover and on-call, while the cloud account and data stay yours.

As an annual contract based on deployment size, SLA tier and coverage hours, not per incident. Calling us during an outage never carries a cost decision. Quotes come back within 24 hours.