Redis's 15-Year Governance Cycle: From Closed Source in Sicily to the AGPL Revival
In March 2024, when Redis announced it was transitioning its core license from BSD-3-Clause to the non-open-source RSALv2 and SSPLv1, shockwaves rippled across the open-source community. Shortly after, the Linux Foundation launched the Valkey fork, with cloud hyperscalers like AWS and Google Cloud quickly rallying behind it.
Yet just one year later, Redis’s founder returned. With the release of Redis 8 in May 2025, AGPLv3 was officially reintroduced as an optional core license, restoring its OSI-approved open-source status.
Over fifteen years, Redis traversed a complete governance cycle: from an internal closed-source utility to permissive licensing, corporate self-defense, a community fork, and ultimately back to copyleft reciprocity.
Origins: A Sicilian Startup’s Proprietary Workaround
In early 2009, Salvatore Sanfilippo (known online as antirez), based in Sicily, was running a real-time web analytics service called LLOOGG alongside his co-founder. Paying customers needed real-time visibility into their site’s “last N pageviews.” It was an unforgiving workload: every single page event required maintaining a bounded list under high-frequency writes, while older entries rapidly lost value.
Relational databases struggled under the relentless churn of concurrent inserts and deletes, while the prevailing in-memory cache, Memcached, supported only flat strings—incapable of trimming lists server-side without massive overhead.
antirez decided to build his own tool from scratch. In doing so, he laid down three architectural pillars that would endure for fifteen years: in-memory data storage, a single-threaded event loop (granting commands inherent atomicity), and the explicit identity of a data structure server.
Yet that codebase began its life behind closed doors. As antirez reflected years later:
When I started to develop Redis in the context of a company where I was one of the two founders and where we kept the software code closed (Redis was opened as it was considered not part of the core product). We didn’t want our services to be copied by others, as simple as that.
The team kept the code under wraps until concluding that the tool was incidental rather than central to their core business. Redis went public in February 2009 under the ultra-permissive BSD license.
The Robin Hood Era: A Golden Decade Under Corporate Sponsorship
When GitHub built its Resque job queue on Redis in 2009, and Instagram published a 2011 post detailing how it stored hundreds of millions of simple key-value pairs in Redis, the project exploded in popularity. Maintenance was quickly outgrowing what a solo developer could handle.
To make development sustainable, antirez explored various avenues to earn a living. He considered keeping peripheral tooling proprietary, and even toyed with an open-core-like model that delayed BSD licensing for new code by six months.
The ultimate breakthrough came through corporate patronage. Starting in 2010, VMware sponsored antirez to work on Redis full-time. That sponsorship transferred to Pivotal in 2013, and in June 2015 moved to Redis Labs (formerly Garantia Data). Over this period, Redis Labs gradually acquired the project’s trademark and organizational assets, cementing itself as the official commercial entity.
- Corporate SponsorVMware / Redis Labs
- Sponsorship SalaryantirezLead Maintainer
- Full-time BSD CodeOpen Source UsersGlobal Community
antirez once colorfully described this arrangement as the Robin Hood of open source: corporations paid him a regular salary, but he dedicated himself entirely to writing BSD-licensed core code for the broader community. Throughout this golden decade, Redis matured from a personal side project into enterprise-grade distributed infrastructure.
From Lua scripting integration and high-availability Sentinel to horizontally scalable Redis Cluster, the project steadily secured its place in the mainstream. Yet the complexity of distributed systems and cluster fault tolerance vastly inflated maintenance overhead, exposing the structural vulnerability of permissive licensing: cloud providers packaged operationally complex clusters into turnkey managed services (such as AWS ElastiCache), reaping massive margins without sharing any revenue with the project’s creators. With the corporate sponsor footing the entire bill for core engineering, the economic scales tilted dangerously.
The First Cracks: From Perimeter Defense to Maintainer Departure
Seeking commercial viability outside the BSD core, Redis Labs attempted to move its line of defense to the perimeter. The Modules API introduced in 2017 was originally meant to keep the core lean by letting developers dynamically plug in custom data types. Soon, however, the company began implementing high-value innovations—such as full-text search and graph querying—as proprietary add-on modules, experimenting with restrictive licenses to monetize them.
In August 2018, Redis Labs shifted advanced modules like RediSearch and RedisGraph from AGPL to Apache 2.0 with the Commons Clause (forbidding commercial resale), before adopting its proprietary Redis Source Available License (RSAL) in 2019.
Backlash from the open-source community was immediate. To quell unease, antirez repeatedly assured users that the core engine would remain strictly BSD, insisting it was not an open-core bait-and-switch. But this architectural decoupling between core and extensions created a perverse governance incentive: the commercial entity had every reason to lock high-value innovations inside source-available modules, while the open-source core risked stagnation as an under-resourced maintenance burden.
A bigger turning point came on June 30, 2020. antirez published his farewell announcement, handing stewardship over to core maintainers Yossi Gottlieb and Oran Agra. His departure stemmed not from licensing disputes, but from creative burnout:
However I never wanted to be a software maintainer. […] I write code in order to express myself, and I consider what I code an artifact. […] I’d rather be remembered as a bad artist than a good programmer.
He admitted that when daily work shifted from building novel creations to safeguarding system reliability and reviewing sprawling pull requests, his drive for self-expression withered. The founder’s exit—combined with the commercial company’s consolidated control over the trademark and governance—stripped the open-source core of its most formidable defense against full commercialization.
The License Storm and the Valkey Fork: Clashing with Cloud Titans
Four years later, on March 20, 2024, past assurances buckled under commercial reality. Redis CEO Rowan Trollope officially announced that starting with Redis 7.4, the core engine was ditching BSD-3 in favor of a dual-license model: RSALv2 and SSPLv1.
| License Model | OSI-Approved Open Source | Competitive Cloud Hosting | Internal Enterprise Use |
|---|---|---|---|
| BSD-3 | Yes | Fully permitted (unrestricted) | Fully permitted and free |
| RSALv2 | No | Explicitly bans reselling as a database service | Fully permitted and free |
| SSPLv1 | No | Requires open-sourcing the entire hosting management stack | Fully permitted and free |
| AGPLv3 | Yes | Modified network services must disclose source code | Fully permitted and free |
The new licenses were fundamentally “source-available” rather than open source. RSALv2 explicitly barred offering Redis as a competitive commercial database service, while SSPLv1—borrowed from MongoDB—stipulated that offering the software as a service required open-sourcing the provider’s entire infrastructure and management control plane. The target was unmistakable: cloud hyperscalers repackaging open-source software for profit without giving back.
In subsequent reflections, antirez noted bluntly that hyperscalers had broken the economics of foundational infrastructure; Redis was merely the latest casualty in an industry-wide licensing shift. Drawing a defensive perimeter to prevent cloud giants from reselling the entire software package without contributing a dime was a rational bid for corporate survival.
Yet the counterstrike from the community and cloud giants was swift and decisive. Just eight days later, on March 28, the Linux Foundation announced the launch of an open-source fork: Valkey.
Branched from Redis 7.2.4—the final BSD-licensed release—Valkey marshaled immediate backing from AWS, Google Cloud, Oracle, and others. In the fall of 2024, the Valkey team rewrote the asynchronous I/O threading engine for version 8.0, turning substantial performance gains into its calling card. AWS soon rolled out Valkey support on ElastiCache, advertising pricing roughly 20% lower than comparable Redis instances.
NOTE
Further reading: From BSL Shockwaves to State Encryption: OpenTofu’s Open-Source Stand and Technical Breakthrough
The Pragmatic Detour: The Founder’s Return and the AGPL Compromise
In December 2024, after a four-year absence, antirez announced his return to Redis. He reached out to the CEO himself. In his essay, he explained that years devoted to writing had left him craving a renewed sense of purpose, and that watching the Redis community splinter had become unbearable.
Back at the company, he spearheaded the implementation of native vector retrieval (vector sets), giving developers an intuitive, sorted-set-like syntax for high-dimensional vector similarity searches. This time, however, he wanted the new capabilities to live under a recognized open-source license.
- 2009 Closed Source (LLOOGG internal tool)
- Open-sourced as non-core2009-2020 BSD-3 Era (VMware / Redis Labs)
- Maintainer exit & Cloud friction2024-03 RSALv2 / SSPLv1 (Commercial defense)
-
- antirez returns with vector sets2025-05 Redis 8 with AGPLv3 (Back to OSI)
- 2024-03 Linux Foundation forks Valkey
On May 1, 2025, Redis 8.0 officially landed. Alongside existing source-available licenses (RSALv2 and SSPLv1), the project added AGPLv3 to the core distribution, formally returning to the OSI-approved open-source fold. At the same time, the previously separated Redis Stack modules—including vector search, JSON support, and Bloom filters—were consolidated into a single unified distribution at no cost.
antirez offered a piercing verdict on this licensing choice:
the AGPL vs SSPL main difference is that AGPL is ‘understood’
While SSPL was draconian and invited persistent legal ambiguity alongside accusations of open-source apostasy, AGPLv3 was a battle-tested reciprocal (copyleft) license with nearly two decades of scrutiny and clearly delineated boundaries.
For typical developers, applications call Redis as an independent process over a network protocol. This network separation triggers no copyleft contagion for proprietary codebases, keeping SaaS business logic entirely safe. For cloud providers, however, AGPL mandates that any modified version used to deliver network services must make its source code public. That requirement sharply raised the penalty for cloud vendors running proprietary patches and bespoke extensions without upstreaming improvements.
Equilibrium After the Fork: Pragmatic Order Through Reciprocal Boundaries
Although Redis reclaimed its open-source credentials, the fork was already a fait accompli, steering the broader ecosystem toward a pragmatic equilibrium.
Cloud strategies diverged accordingly. While AWS and Google Cloud decisively backed Valkey, Microsoft Azure took the opposite tack: partnering directly with Redis Inc. to launch Azure Managed Redis, built on Redis Enterprise software and supporting Redis 7.4.x as of this writing.
On one end of the architectural spectrum, organizations with corporate copyleft restrictions or deep investments in AWS/GCP native managed services gravitated toward Linux Foundation–backed Valkey. On the other end, teams prioritizing rich native capabilities (such as unified vector retrieval and JSON) and those invested in Azure’s managed environment opted for the all-in-one delivery of Redis 8.
NOTE
Licensing Boundaries for Existing Production Environments: Any existing production deployments running Redis 7.2 or earlier retain their BSD-3 rights indefinitely; subsequent licensing changes are non-retroactive. Only infrastructure teams planning upgrades to version 7.4 and beyond need to evaluate licensing compliance boundaries.
From an internal utility in a Sicilian startup and viral growth under permissive licensing to drawing a line in the sand with AGPLv3, Redis exemplifies the raw economic reality of modern open-source infrastructure: in an age dominated by cloud hyperscalers, the romantic “Robin Hood model” of permissive licensing fueled by solo goodwill can no longer sustain the critical foundations of the internet.