Redis, which makes the Redis value-key database, returns its main system to open-source license AGPL, after criticism in 2024 for moving to a dual-license model
https://antirez.com/... Though the more interesting question I think is whether Redis Inc can recover the lost trust from the community (and from customers). … Forums: r/programming : Redis is open source again -antirez r/programmingcirclejerk : Redis is open source again r/linux : Redis is Open Source again r/theprimeagen : Redis is open source again r/opensource : Redis is now available under the the OSI-approved AGPLv3 open source license
Context & Ripple Effects
Redis’s 2024 move away from its 3-clause BSD terms to a controversial dual-license model put the company’s commercial strategy at odds with expectations built around the database’s open-source distribution.
The return to an OSI-approved copyleft license is therefore chiefly a trust-repair move: it restores a recognized open-source framework, but does not by itself resolve the community and customer confidence questions raised by the earlier change.
First-order effects
- Redis users, contributors, and downstream distributors can again evaluate the main system under AGPLv3 rather than the intervening dual-license arrangement.
- Redis Inc gains a clearer basis to re-engage open-source stakeholders, while facing immediate scrutiny over whether the reversal is durable enough to rebuild trust.
Second-order effects
- Organizations that delayed upgrades, contributions, or Redis-based product decisions because of licensing uncertainty now have a defined license baseline for reassessing those choices.
- The episode raises the reputational cost for other infrastructure vendors considering restrictive licensing shifts, especially where their adoption depends on broad developer participation.
Third-order effects
- The reversal underscores that licensing is a governance decision as much as a monetization tool: changes that disrupt community expectations can be difficult to unwind even after a company restores an OSI-approved model.
- It also keeps the industry’s permissive-versus-copyleft trade-off in focus, following evidence that permissive licenses dominated open-source packages; vendors may increasingly weigh commercial control against ecosystem legitimacy.
The trend: Commercial open-source companies are being pushed to align revenue protection with license choices that preserve long-term developer and customer trust.