Buying Redis and Valkey Support: The Guide

Server incidents, memory and persistence problems, replication and failover, configuration and tuning are in scope on any serious contract. Client library behaviour, connection pooling, the application's data model and the managed platform underneath are where contracts differ, and where most incidents originate. Put the boundary in writing with examples.

Redis Enterprise is a product: active-active geo-distribution, enterprise modules, a management layer, and vendor support for all of it. If you need those features, that is the purchase. If you run open-source Redis, Redis Stack or Valkey and what you need is an engineer at 3am, a support contract for the build you already run is the purchase, and it is a separate decision from the licence.

Redis Ltd, for Redis Enterprise and Redis Cloud. The cloud platforms, for their managed offerings inside their own accounts: ElastiCache, Azure Cache for Redis, Memorystore. Independent firms, for open-source Redis, Redis Stack and Valkey wherever they run. And the community, for everything except an incident response plan. Which one fits is set by where Redis runs and whether you need a licence or an engineer.

Priced on the number of instances or clusters and the response tier, from business hours to 24/7 with a 15-minute emergency response. The comparison that matters is not against a licence but against the cost of the last unexplained latency incident and the engineer days spent on it.

A named senior engineer as the first responder, a defined trigger for the response clock, severity definitions that treat a latency spike with no traffic correlation as an incident, and read-only access agreed in advance so the first fifteen minutes are diagnosis rather than paperwork. A ticket queue with a 15-minute acknowledgement is not incident response.

If the estate is moving to Valkey, or might, the contract should cover both builds, because the operational surface is largely shared and a migration is the moment you most need cover. Whether to move is a governance and licensing decision; the technical distance is small and knowable.