Redis → Valkey
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
Neutral if you self-host — Valkey is a drop-in fork. Against Redis Cloud or Redis Enterprise the saving is the whole licence, and against managed Redis it is whatever your provider charges for the Valkey equivalent, usually less.
Moves cleanly
Everything. Valkey is the Linux Foundation fork of Redis 7.2.4, made after Redis moved to a source-available licence. Same protocol, same commands, same RDB and AOF files.
You rebuild
Nothing. Point your client at Valkey.
What Redis costs you today
The software is free to run. Redis Cloud starts around $5/month for a small instance and scales into four figures for production clusters with replication and persistence; AWS ElastiCache, Azure Cache and Google Memorystore price similarly per node-hour. Redis Enterprise is quoted. The bill is for memory and availability, and memory is the expensive kind of storage. Figures checked 2026-08-05.
What actually holds you in
Very low, and it is the reason this category moved so fast. The Redis wire protocol is the interface, and Valkey, DragonflyDB, KeyDB and Garnet all implement it — so your client library, your commands and your code stay as they are, and switching is a change of hostname. That portability is exactly why the fork succeeded where forks usually fail. What does not port is anything using Redis Ltd's proprietary modules: RedisJSON, RediSearch, RedisTimeSeries. Teams using plain Redis move in an afternoon; teams built on the modules are rewriting.
What you are moving to
Valkey is the community fork of Redis taken from the last BSD-licensed release, now under Linux Foundation stewardship with AWS, Google and Oracle contributing. It is the same codebase, so the protocol, commands and clients are identical and migration is a hostname change. BSD-3-Clause, around 27k stars. The argument for it is not technical — it is that no single company can relicense it, which is precisely the event that created it. Performance has since moved ahead of Redis in several published benchmarks through multi-threaded I/O work the fork prioritised.
Free and open source. Managed offerings from AWS, Google and others.
Valkey strengths
- Drop-in for Redis — same protocol, same clients, hostname change
- BSD-3-Clause under Linux Foundation governance; no vendor can relicense it
- Backed by AWS, Google and Oracle with real engineering behind it
- Faster than Redis on several published benchmarks after multi-threading work
What you give up
- Does not include Redis Ltd's proprietary modules — no RedisJSON or RediSearch
- Younger brand, so some managed providers still list only Redis
- Documentation still catching up with Redis's two decades
- Divergence from upstream Redis will grow over time
The migration, step by step
- 1Confirm your Redis version — Valkey forked at 7.2.4, so anything at or below that is a straight swap
- 2Stop Redis, start Valkey against the same data directory
- 3Verify with redis-cli, which works unchanged
- 4For zero downtime, run Valkey as a replica of Redis and promote it
- 5Update client libraries only if you want Valkey-specific features; existing clients work
The gotcha
Redis Stack modules — RediSearch, RedisJSON, RedisTimeSeries — are not in Valkey. If you use them, this is not a drop-in and the equivalents are separate projects at different maturity.
When to stay on Redis
You depend on Redis Stack modules or have Redis Enterprise support you use.
More Layer 3 migrations
Figures verified 2026-08-05 against vendor pricing pages. Prices change and migrations differ by estate — treat the cost delta as a starting model, not a quote. Rankings and recommendations here are merit-only; affiliate income never changes a verdict. See our methodology.