Redis Goes Source-Available, Sparks Fork Discussions
Redis Labs relicenses Redis under SSPL + RSAL. Linux Foundation announces Valkey as an open-source fork backed by AWS, Google, and Oracle.
Full summary
Redis Labs has announced that Redis will be relicensed from the permissive BSD-3-Clause license to a dual SSPL / RSAL ("source-available") arrangement, mirroring the path MongoDB and Elastic took in earlier years. Within hours, the Linux Foundation announced Valkey, a Redis fork seeded from the last BSD-licensed commit. The fork has corporate backing from AWS, Google Cloud, and Oracle, all of whom maintain Redis-compatible services. For end-user developers, the immediate impact is small: protocol compatibility will be maintained on both sides for the foreseeable future. The long-term divergence question is more interesting.
Why it matters
License changes in widely-deployed open source projects create downstream effects across cloud providers, packaged distributions, and enterprise procurement. Even if no code changes, legal review is now required for many teams.
Technical explanation
Both Redis 7.4 (SSPL) and Valkey 8.0 (BSD) maintain protocol compatibility. Client libraries should work against either. Where they'll diverge is in modules (RedisJSON, RediSearch — those remain Redis-only) and in cluster behavior over the next 18 months.
Business impact
Procurement and legal teams will be asked to re-review Redis usage. Managed-Redis vendors that depended on the upstream open-source license now have a clearer commercial narrative.
⚡ Action needed
If you self-host Redis, decide which fork to track. If you use a managed service (Elasticache, MemoryStore, Redis Enterprise Cloud), confirm with your provider which fork they're following.