Choosing Valkey Over Redis OSS

Decision drivers

Whether any current or planned feature depends on Redis-specific modules (vector sets, RedisSearch-descended functionality, Enterprise active-active)
Client library's confirmed (not assumed) Valkey compatibility
Node-based price delta at your specific instance type/region (20% below Redis OSS is AWS's stated rate; confirm the exact current hourly figure, since AWS pricing pages do change)
Existing operational tooling/monitoring's Valkey support maturity

Production premise

Valkey forked from Redis 7.2.4 in April 2024 after Redis Ltd's license change (BSD-3 → SSPL/RSALv2), is governed by the Linux Foundation with AWS as a founding contributor, and is wire-compatible with existing Redis clients (redis-py, ioredis, Jedis) without code changes. AWS made it the default engine for new ElastiCache and MemoryDB clusters in October 2024, and prices it 20% below Redis OSS on node-based deployments and 33% below on Serverless — both confirmed directly by AWS's own Valkey launch post, not a third-party estimate.

Failure mode & inflection point

By 2026 the two projects have genuinely diverged — still roughly 90% command-compatible, but Redis 8 added vector sets and continued iterating on the Redis Query Engine (search/vector functionality descended from the old RediSearch module) in ways Valkey's compatible modules haven't fully matched yet. A team that picks Valkey purely for the cost/licensing story and later needs Redis's vector-search or Redis Enterprise active-active replication features discovers the gap mid-project, not during planning.

Production guardrail

Default to Valkey for new deployments unless a specific, named feature (vector search, a particular Redis Enterprise module, a compliance tool that hasn't validated Valkey yet) requires Redis OSS — the "check your client library's Valkey compatibility explicitly" caution from production migration reports is real: "Redis-compatible" doesn't guarantee "tested against Valkey," so verify the specific client library version, not just the protocol family, before assuming a drop-in swap. For existing Redis OSS clusters, AWS supports an in-place engine swap to Valkey without changing the endpoint, and existing Reserved Nodes carry over automatically to the new engine — there's no urgency, but it belongs on the roadmap given Redis OSS's murkier long-term licensing trajectory and (since February 2026) Extended Support surcharges that apply to aging Redis OSS versions but not Valkey.