ADVISORY
Redis license change advisory for the teams running it in production.
Our Redis license change advisory explains what the 2024 move to the Server Side Public License restricts, maps where it touches your estate, and weighs the community fork Valkey against staying current or negotiating commercial terms. Independent, buyer side, paid only by you.
Not ready to talk? Read the free open source license risk guides first.
A Redis license change advisory starts with the facts. As of March 2024 Redis moved from an open source license to a dual model under the Redis Source Available License version 2 and the Server Side Public License, and later added an open license option. The community fork backed by several vendors is Valkey. The practical question for most enterprises is narrow: where does the new license actually bite, and what does it cost to stay clean.
What the Redis license change means
Source available is not open source. The Server Side Public License is not approved by the Open Source Initiative, and it carries a strong service condition aimed at parties who offer the software as a service. For an enterprise that runs Redis internally, the exposure profile differs sharply from a provider that resells a managed Redis offering. The advisory reads your usage against the license triggers rather than applying a blanket warning.
Where the change touches your estate
- Direct deployments of Redis across services and environments.
- Redis embedded inside other tools and platforms you run, which is where exposure hides.
- Any offering where you expose Redis functionality to customers as a service.
- Upgrade paths, since the new terms govern future versions rather than copies already deployed.
Valkey, negotiated terms, or staying current
There are three credible paths and the right one depends on the facts. Migrating to Valkey rather than Redis preserves an open posture but carries migration cost. Negotiating a commercial license can be the cleaner answer when usage is deep and switching is expensive. Staying current under the new terms is viable when your usage never crosses a restricted trigger. The advisory sizes each path so the decision is evidence based.
How the advisory connects to the wider picture
Redis is one instance of a broader pattern. The same dynamics drove the changes at Elastic and HashiCorp. For the full context read the Redis and Elastic database licensing pillar and the relicensing pillar. When the work moves from analysis to action, a relicensing exposure review sizes the cost and a containment plan sequences the fix. See all advisory services for scope.
COMMON QUESTIONS
Questions buyers ask.
What changed with the Redis license?
As of March 2024 Redis moved from an open source license to a dual model under the Redis Source Available License version 2 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. The community fork is Valkey.
Does the Redis license change affect software already in production?
It can. The change does not rewrite versions you already deployed, but it governs upgrades, redistribution, and offering Redis as a managed service. A Redis license change advisory maps where those triggers apply in your estate.
Should we move to Valkey?
Sometimes. Valkey is a community fork that preserves an open license posture, but a migration carries engineering cost and operational risk. The advisory weighs a fork against staying current under the new terms or negotiating a commercial license, on the facts of your deployment.
Is the Redis license change advisory legal advice?
No. It is commercial and licensing risk advisory, not legal advice. For interpretation of the license terms we recommend your own counsel.
CONTAINMENT
Understand the Redis license change before your next upgrade.
A confidential Redis license change advisory. Independent, buyer side, paid only by you.
Independent, confidential, buyer side. See how buyers contained their exposure →