COMPARISON
Redis vs Valkey compared for enterprises.
Redis vs Valkey is the choice many teams now face after the Redis relicense. This comparison sets out the license, governance, compatibility, and risk trade offs from the buyer side, and ends with a clear way to decide which one fits your deployment.
Redis vs Valkey is not a feature beauty contest. The two are close cousins, because Valkey was forked from the last open source release of Redis. The real difference is license posture and governance, and that is exactly where enterprise risk lives. This comparison keeps the focus there: what each one is, how they differ on the points that matter for exposure, and how to choose. For the wider context, see the Redis and Elastic database licensing pillar.
What Redis and Valkey are
Redis is the original in memory data store, widely used as a cache, message broker, and lightweight database. As of March 2024 Redis moved from an open source license to a model that includes the Redis Source Available License and the Server Side Public License, and later added an open license option. Source available is not open source, and the Server Side Public License is not approved by the Open Source Initiative.
Valkey is the community fork created from the last open source version of Redis in response to that change. It is governed by a foundation rather than a single company and continues under a permissive open source license. Its stated aim is to remain a drop in alternative for the large base of existing Redis users. The fork background sits in the OpenTofu and Valkey fork story.
Redis vs Valkey at a glance
| Dimension | Redis | Valkey |
|---|---|---|
| License posture | Source available editions plus a later open license option. Not fully open across all editions. | Permissive open source license, approved family, held by a foundation. |
| Governance | Single commercial company directs the project. | Foundation with multiple corporate backers and community contributors. |
| Compatibility | The reference implementation. Defines the protocol and feature set. | Forked from the last open Redis release, aims to stay protocol and client compatible. |
| Managed service use | Source available terms can restrict offering Redis as a service to third parties. | Open license places no field of use restriction on managed service offerings. |
| Commercial support | Vendor commercial editions, support, and enterprise features. | Community support plus commercial support from foundation members and providers. |
| Roadmap risk | Future terms set by one vendor, which can change again. | Direction set by foundation governance, lower single vendor risk. |
License and governance, the decisive points
For most enterprises the deciding factor is not raw performance but who controls the terms and whether those terms restrict your use. Redis under source available editions carries a competitive and service restriction that can apply to deployments already running, and the terms are set by a single company that has already changed them once. Valkey removes the field of use restriction and spreads governance across a foundation, which reduces the chance of another unilateral change. If your concern is predictability and freedom from future commercial demands, governance favors Valkey.
Compatibility and migration
Because Valkey began as a fork of the last open Redis release, compatibility is strong at the fork point, and the project aims to keep the protocol and common client libraries interoperable. That makes migration straightforward for typical cache and data store use, often a configuration change rather than an application rewrite. The caution is that two independently governed projects can diverge over time, so test Valkey against your own workload and client versions rather than assuming permanent parity. For the method of moving safely, our open source remediation advisory sequences the cutover and validates parity before anything critical moves.
How to decide
The right answer depends on how you deploy, not on a general preference.
- If you offer Redis to third parties as a service, or plan to, the source available restrictions raise real exposure and Valkey or a commercial license becomes the practical choice.
- If you want to remove dependency on future commercial terms, Valkey returns the workload to an open license under foundation governance.
- If you run a stable internal version with no live trigger, holding can be reasonable, provided the decision is documented and the security posture is managed.
- If you rely on specific Redis commercial features, weigh a scoped commercial license against the engineering cost of replacing them.
Whichever way the choice leans, size the exposure before you act. A confidential assessment maps where Redis runs, classifies each deployment by use, and sets the cost of exposure against the cost to cure, so the decision rests on numbers rather than urgency. See also the Redis, Elastic and database licensing FAQ and the broader relicensing pillar.
COMMON QUESTIONS
Questions buyers ask.
What is the difference between Redis and Valkey?
Redis is the original project, now under a model that includes source available licenses as of March 2024. Valkey is the community fork created from the last open source version of Redis, governed by a foundation and continuing under an open license. Valkey aims to stay drop in compatible.
Is Valkey open source and Redis not?
Valkey is open source under a permissive license held by a foundation. The Redis source available editions are not open source, though Redis later added an open license option. The license posture is the central difference for risk.
Is Valkey compatible with Redis?
Valkey was forked from the last open source Redis release and aims to remain compatible with the Redis protocol and common client libraries. Compatibility is strong at the fork point, but the projects can diverge over time, so test against your own workload.
Should an enterprise migrate from Redis to Valkey?
It depends on how you deploy. If your use risks crossing the source available restrictions or you want to remove dependency on future commercial terms, Valkey is a strong path. If you run a stable internal version with no live trigger, holding may be reasonable. Size the exposure first.
Is this comparison legal advice?
No. It is commercial and licensing risk analysis, not legal advice. For interpretation of license terms, engage your own counsel.
CONTAINMENT
Decide Redis vs Valkey on numbers, not urgency.
A confidential open source license risk assessment. Independent, buyer side, paid only by you.
Not ready to talk? Read the free open source license risk guides first.