Valkey vs Memcached
Both are alternatives to Redis. Here's how they stack up — verified facts, no spin.
Also searched as Memcached 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.
Memcached
The one that only caches — and does it without ceremony.
Memcached predates Redis and does one thing: a distributed in-memory key-value cache. No persistence, no data structures, no pub/sub, no clustering logic. BSD-3-Clause, and stable for so long that it is genuinely boring, which for infrastructure is a compliment. Listed because a great many Redis deployments are caching a string against a key and nothing more — and for that job Memcached uses less memory, has fewer failure modes, and gives you nothing to misconfigure. Ask what you are actually storing before you assume you need Redis.
Side by side
| Valkey | Memcached | |
|---|---|---|
| Sovereignty Score | 96 | 95 |
| Open source | Yes | Yes |
| Self-hostable | Yes | Yes |
| Local-first | Yes | Yes |
| License | BSD-3-Clause | BSD-3-Clause |
| Pricing | Free and open source. Managed offerings from AWS, Google and others. | Free and open source. |
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
Memcached
Strengths
- +BSD-3-Clause and completely uncontroversial for two decades
- +Lower memory overhead than Redis for simple key-value caching
- +Very few moving parts, so very few ways to break it
- +Supported by every major managed cloud
Trade-offs
- −Caching only — no persistence, no data structures, no pub/sub
- −No replication or failover built in
- −Cannot serve as a queue, session store or message bus
- −Wrong tool the moment you need more than a cache
Related alternative guides
Facts verified 2026-08-05. Licenses and pricing change — spotted something out of date? That's a correction we want.