Valkey vs DragonflyDB
Both are alternatives to Redis. Here's how they stack up — verified facts, no spin.
Also searched as DragonflyDB vs Valkey — same comparison, one verdict.
Valkey
TOP PICKThe Linux Foundation fork — same Redis, governance that cannot be revoked.
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.
DragonflyDB
Redis-compatible, built for modern multi-core machines.
DragonflyDB is a ground-up reimplementation of the Redis and Memcached protocols designed for the hardware people actually run now: it scales across all cores rather than being effectively single-threaded, and reports substantially higher throughput per machine with lower memory use. Around 31k stars. That means fewer, smaller instances for the same load, which is a real cost line rather than a benchmark. The licence is Business Source License 1.1 — source-available, converting to Apache-2.0 after a delay — so it is not open source today and should not be described as such.
Side by side
| Valkey | DragonflyDB | |
|---|---|---|
| Sovereignty Score | 96 | 70 |
| Open source | Yes | No |
| Self-hostable | Yes | Yes |
| Local-first | Yes | Yes |
| License | BSD-3-Clause | Business Source License 1.1 (source-available, converts to Apache-2.0 in time) |
| Pricing | Free and open source. Managed offerings from AWS, Google and others. | Free to self-host within BSL terms. Dragonfly Cloud is paid. |
Valkey is Macrostack's recommended Redis alternative, so it's our pick here.
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
Trade-offs
- −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
DragonflyDB
Strengths
- +Uses every core — far higher throughput per machine than Redis
- +Lower memory footprint for the same dataset
- +Speaks both Redis and Memcached protocols
- +Fewer, smaller instances for the same workload
Trade-offs
- −Business Source License — not open source today, whatever lists say
- −Cannot be offered as a competing managed service
- −Younger codebase with a shorter production record
- −Some rarely used Redis commands are unimplemented
Related alternative guides
Facts verified 2026-08-05. Licenses and pricing change — spotted something out of date? That's a correction we want.