Redict: When Open Source Turns Paywall: The Redis Rebellion That Shook Tech

In March 2024, Redis Inc. announced a pivotal shift, moving future versions of its widely used in-memory database from the permissive BSD-3-Clause open-source license to a dual-licensing model featuring the Redis Source Available License (RSAL) and the Server Side Public License (SSPL). This change effectively restricted commercial cloud providers from offering Redis as a service without either paying licensing fees or publicly disclosing their proprietary infrastructure under SSPL—a condition most deemed unacceptable. The decision ignited widespread backlash across the developer community, who viewed it as a betrayal of open-source principles. Many had built businesses, platforms, and careers on the assumption that Redis would remain freely available, and the sudden license change threatened their operational and financial stability. In response, developers and organizations rallied to preserve the original open-source ethos by forking the last BSD-licensed version of Redis, giving rise to Redict. Hosted under the Linux Foundation, Redict emerged as a community-driven, truly open-source alternative committed to the BSD-3 license, ensuring long-term freedom from restrictive commercial terms. The move highlighted a growing tension in the open-source ecosystem: how to sustainably fund critical software development without compromising the freedoms that fuel innovation and broad adoption. Major cloud providers like Amazon, Google, and Microsoft, who had profited from offering managed Redis services, now faced a strategic crossroads—pay licensing fees, risk security by sticking to outdated versions, or support open forks like Redict. This shift has broader implications, as it sets a precedent that could encourage other open-source projects to adopt source-available licenses, potentially fragmenting the ecosystem and creating parallel development paths. The Redis-Redict split exemplifies a larger debate about the sustainability of open source, the ethics of cloud provider exploitation, and the balance between creator compensation and community access. While Redis Inc. argues the change was necessary for survival and continued innovation, critics warn it undermines trust in open-source projects and may deter future contributions. Conversely, Redict represents a counter-movement, proving that community-led initiatives can respond swiftly to protect shared digital infrastructure. The outcome will influence how future open-source projects are funded, governed, and maintained. For end users, the impact may be indirect but real—potentially affecting service costs, app performance, and data security depending on which database stack companies choose. Ultimately, the Redis saga underscores that open source is not just about code, but about values: collaboration, transparency, and equitable access. As the tech world watches this unfolding drama, the choices made by developers, companies, and communities today will shape the architecture of tomorrow’s digital landscape, reinforcing the idea that the soul of the internet depends on the principles we choose to defend.

There are no comments yet.

Please log in to write the first comment.