Redis, the popular in-memory data store, switches from the open source 3-clause BSD license to a controversial dual-license model
Redis, the popular in-memory data store, is switching away from the open-source three-clause BSD license. Instead, in a move that is clearly aimed to prevent …
TechCrunchFrederic Lardinois
Context & Ripple Effects
Redis had built commercial momentum around an in-memory database while retaining an open-source identity, including earlier funding for its commercial services and a later growth round. The licensing shift therefore changes the terms around a widely used component, not just a new product offering.
The move also sits in a familiar community-pressure cycle: related coverage records Redis returning its main system to an AGPL license after criticism of the 2024 dual-license change. That later reversal makes this an important test of how licensing choices affect adoption and trust.
First-order effects
Redis users, redistributors, and commercial implementers must review whether their existing and planned uses fit the new dual-license terms rather than the former BSD baseline.
Redis gains a licensing mechanism to distinguish uses it permits under open terms from uses that may require a commercial arrangement.
Second-order effects
Organizations that chose Redis partly for BSD-style simplicity may evaluate migration paths, forks, or substitute databases, raising switching and support costs even where they remain on Redis.
The change puts more weight on vendors' license clarity: permissive licensing had been dominant across the package ecosystem in a study of open-source package licenses, so departures can become a procurement and governance issue.
Third-order effects
If similar changes proliferate, open-source infrastructure vendors may increasingly use licensing as a boundary between broad developer adoption and monetizable deployment—while users price in the risk of later term changes.
Redis's subsequent license reversal suggests community acceptance can constrain that strategy; durable licensing models will need to balance vendor control with contributor and user confidence.
The trend: This is one instance of infrastructure software vendors using license design to reconcile open distribution with commercial control, while communities retain leverage through adoption choices.
I've gotten together with various former Redis contributors and we've started working on a fork: https://github.com/.... We are all unhappy with the license change, and are looking to build a new truly open community to fill the void left by Redis. Come join us!
Redis going the proprietary way is yet another sign that we need infrastructure to fund truly Open Source projects. Be it for maintainers struggling to keep things afloat or for users.
With Open Source Redis dead, the good thing is there are many implementation of Redis Protocol. Some Open Source. Which one do you think is leading contender to take over ? #redis #opensource
2,038 days. That's how long it took from @antirez to say Redis will remain BSD license, to when Redis changes from BSD license. https://antirez.com/...
Redis is cracking down on cloud providers who offer hosted Redis by introducing new licenses: https://redis.com/... I'm critical of bait-and-switch, but providers who pay for OSS can benefit from protecting themselves from free-loading providers. But will Redis stop there?
redis was a bit of magic; that a single person could lead a free, extremely reliable + performant, and simple database; but I guess yesterday shows infrastructure tends to fall towards private corporations with the structures and funding to manage it
honestly disappointed in Redis... I am disappointed in companies taking advantage open source communities that have helped build their success... please support open source foundations and other efforts that try to enable fair playing fields
Today, we announced that all future versions of Redis will be released with source-available licenses. Starting with the release of Redis 7.4, Redis will be dual licensed under SSPLv1 and RSALv2. The Redis source code will remain freely available to developers, customers, and...
A note to Founders: If you want to step back and ensure Open Source future of your software, transfer it to hands of a Foundation. Apache Redis would not have a license change! and still allow commercial companies to build their solutions on it #redis #opensource
redis going closed ("available") source and trying to charge everyone to use it in the cloud or production sucks so much :< i hate companies. bought and merged with an israeli firm and immediately started destroying their product/community for money. At least there r alternatives
> Hi, this is Yiftach, CTO and Co-founder of Redis Labs. First, let me assure you that Redis remains and always will remain, open source, BSD license. @Yiftachsh Shoolman, 2018 https://news.ycombinator.com/ ... “Always” until March 20, 2024, I guess.
unpopular opinion: with the relicense of #redis, nothing changes for the vast amount of users even if everyone loves drama and “parties with special interests” love to spread FUD. as a reminder, mongodb changed license in 2018 ( https://www.mongodb.com/...) — their users are fine
I am excited about the actions @reconditerose and other core #redis maintainers are taking. BTW, this is Madelyn taking action, not an official #AWS announcement. She should get serious credit for her bias for action. Expect more news soon.
If you miss the news, Garnet is like Redis (drop-in compatible), but much faster, written in C#, and has cluster mode. It's created by Microsoft Research and has MIT license.
RIP Redis: How Garantia Data pulled off the biggest heist in open source history. Detailed blog linked - but checkout the thrilling story of this heist in 🧵first 👇 https://www.gomomento.com/... [image]
📣 Azure Cache for Redis customers: you will not be affected by the upcoming @Redis licensing changes. Our ongoing collaboration ensures that Azure customers can seamlessly utilize all tiers. Read more: https://azure.microsoft.com/ ...
Hi everyone, I'm excited to announce that the Garnet research project is now open source! Garnet is our new cache-store that offers very high performance and adopts the popular RESP wire protocol of Redis. Check it out at https://github.com/... and see our blog post quoted here.