License change for Redis: a choice that divides open source
On March 20, 2024, Redis Ltd. announced its future versions would no longer be under an open-source license, restricting use by cloud providers.
How do you manage a community's reaction when restricting access to a product once free?
Anticipate the disagreement on principle and build a new narrative for partners affected by the restriction. When 49 simulated voices reacted to the Redis decision, about half declared against it, with doubts about the legitimacy of such a change after years of openness.
The context, in plain terms
Redis Ltd. announced on March 20, 2024, that all future versions of Redis, starting with version 7.4, would be released under source-available licenses. This broke with the previous BSD 3-Clause license. The company explicitly indicated a transition to a dual-licensing model using RSALv2 and SSPLv1.
This change meant cloud service providers hosting Redis offerings would no longer be allowed to use Redis source code for free. On March 21, 2024, TechCrunch reported this decision aimed to prevent large cloud providers from offering free alternatives to Redis's hosted services.
Publicly, the long-term practical impact of this decision is not established. Nothing public indicates if the company presented this policy as permanent beyond the versions already mentioned.
Code: A Promise or a Product?
Redis Ltd.'s announcement on March 20, 2024, lends itself to two readings. In one, it is a strategic adjustment necessary for the company's sustainability. In the other, it redraws the lines of commitment and collaboration.
The shift from a permissive open-source license to source-available terms has a direct consequence. For those who built on Redis, this implied that the code, once considered a freely usable common good, now became a product subject to specific usage conditions.
Before a panel of simulated voices, the response was divided. About half of the voices declared against the decision. About one voice in seven doubted its relevance, and about one voice in three supported it. The external contributors group counts for more in this response. The decision directly impacts the philosophy of collaboration and sharing they protect. A license is more than text; it is a trust agreement.
The Price of Retrospective Openness
What holds it back first is a deep disagreement on principle. The issue is not so much Redis Ltd.'s need to generate revenue. It is about how a past commitment is revised for the project's future. Objections focus on a company's legitimacy to restrict access to a project that thrived on its community's collective contribution. It is as if the rules of the game were changed after several rounds played.
On this point, what is missing is the Contribution Debt. This is an explicit acknowledgment and compensation for years of open-source community investment that built the value of the Redis product. The license change alters the perception of collectively created value. This happens without fully accounting for historical contributions. You do not change the rules of the game without acknowledging the past.
The Community Seeks a New Home
Among the opposing voices, a simulated contributor supporting Valkey, from the Project Maintainers group, illustrates a deep split. Though tied to the project, this contributor declared against the decision, stating: "Redis just proved that open-source principles matter, Valkey is the real home for the community now."
This position is shared by a simulated open-source purist contributor, a member of the Outside Contributors, who sees it as "a betrayal of the gift economy that makes open source work at all." Even if a simulated venture capitalist, from the Venture Investors group, supports that "This was the right call, protecting Redis’s revenue from cloud providers is critical for our exit strategy," the disagreement on principle remains the dominant friction point.
We ran the exercise three times: same answer. The strength of this opposition does not come from a simple economic disagreement. It comes from a questioning of the Redis project's ethical foundations. Community loyalty is earned over time, not by a change of terms.
Building a New Social Contract for Code
Now that Redis Ltd.'s decision is public, the first follow-up step is to redefine the social contract with the community and partners. This means addressing those who contributed the most. The goal is not to justify the decision. It is to present the new value proposition and possible collaboration paths.
One must acknowledge the community's past contributions. Clearly articulate the benefits of the new licenses for the product's future. Also, address the concerns of cloud providers. This approach transforms the Contribution Debt into an opportunity for dialogue and re-engagement.
The timeline of this decision, from March 20, 2024, shows it is already in effect. The long-term practical impact on market dynamics is not publicly established. However, the emergence of alternatives is a logical next step. Facing a community seeking a new home, the question is no longer about going back. It is about building new legitimacy. After the license change, the story of shared value must be rewritten.
What you just read comes from a rehearsal, not a report. Before a panel of 49 simulated voices, the Kapari test bench highlighted a deep disagreement on principle. This was illustrated by contributors who see this change as a betrayal. It also showed how a venture capitalist perceives this decision as essential for an exit strategy. The same exercise can be conducted on a decision not yet announced, to anticipate friction points and unexpected allies.
The questions readers ask
How do you explain the economic necessity of such a license change?
For the panel's simulated venture capitalist, the license restriction protects revenue from cloud providers. This voice deems it critical for its exit strategy. In this reading, the goal is to ensure the company's financial viability by monetizing the use of its code by major commercial players. These players would otherwise benefit from collective work for free.
What do contributors expect from such a decision?
Contributors, especially open-source purists, expect respect for the principles of the gift economy and collaboration. Their hostility stems from a feeling of betrayal of these values. They perceive these values as the very foundation of the project's success. They seek an environment where these principles are preserved.
Is this a poll or a prediction?
The voices cited in this article are from a panel of 49 simulated voices. They are not an opinion poll, nor a prediction of reality, nor a representative measure of public opinion. Facts come from verified and dated sources. Kapari sheds light on the decision; it does not make it.
How Kapari computes and reads its signals: the method
Related cases
Your next decision deserves the same scrutiny.
Run it through the test bench before you announce it: a panel of voices reacts, you read the range and you see the frictions coming.
Start free