Redis has returned to true open-source licensing with the release of Redis 8, which is available under the AGPLv3 (Affero General Public License version 3) license alongside its existing RSALv2 and SSPLv1 licenses. This marks a shift just over a year after the controversial move away from open source.
The Background: What Happened in March 2024
In March 2024, Redis Labs (now Redis Ltd.) made the controversial decision to switch from the BSD license to a dual-license model using RSALv2 (Redis Source Available License v2) and SSPLv1 (Server Side Public License v1). This change was primarily aimed at preventing major cloud providers like AWS and Google from offering Redis as a managed service without contributing back.
The community reaction was swift and negative:
- The Linux Foundation created the ValKey fork
- Multiple Linux distributions switched to ValKey
- The Open Source Initiative (OSI) continued to reject SSPL as a proper open-source license
How Hyperscalers Responded to the License Change
When Redis switched to SSPL, the major cloud hyperscalers made clear strategic decisions:
- Amazon Web Services (AWS), Google Cloud Platform (GCP), and Oracle immediately backed ValKey, the Redis fork created by the Linux Foundation
- AWS and Google began maintaining their forked versions of Redis rather than complying with the SSPL terms
- Microsoft took a different approach, reaching a commercial agreement with Redis instead of backing ValKey
- The hyperscalers' support gave Valkey immediate credibility and resources, helping it gain 20.7k stars on GitHub and over 700 contributors within a year
The Return to Open Source: AGPLv3
The return to open source has multiple factors behind it:
Key Drivers
- Community Pressure: The SSPL wasn't accepted as a true open source, creating fragmentation
- Salvatore Sanfilippo's Influence: Redis creator "antirez" rejoined the company in November 2024 and advocated for AGPLv3
- Competition from Valkey: The Linux Foundation-backed fork gained significant momentum with hyperscaler support
- Practical Considerations: Customers found it easier to operate under an OSI-approved license
What Changed with Redis 8
- Tri-licensing model: Redis 8 is available under AGPLv3, RSALv2, and SSPLv1, see the explanations here
- Vector Sets: New data type created by antirez for AI workloads
- Performance improvements: Over 30 enhancements, with up to 87% faster commands
- Integrated features: Redis Stack components (JSON, TimeSeries, etc.) are now part of the core Redis
Technical Implications
- AGPLv3 Benefits: OSI-approved, network-copyleft protection from cloud providers
- Developer Experience: No more split between Redis Community Edition and Redis Stack
- Backward Compatibility: Redis 7.2.x and earlier remain under BSD3
Community Response
The move has been generally welcomed, though many remain skeptical about the tri-licensing approach and Redis's history of licensing changes. Industry experts point out several concerns:
- Trust Issues: "Trust is hard to build and easy to lose. Redis' actions have caused a lot of disruption," says Amanda Brock, CEO at OpenUK
- Valkey's Future: Major cloud providers are likely to continue supporting ValKey rather than return to Redis, especially given AGPL's restrictions
- Enterprise Impact: Each license change forces organizations to reevaluate their technology stack and compliance risks
Looking Forward
Redis's decision demonstrates the complex balance companies must strike between protecting their business interests and maintaining community trust. The AGPLv3 license appears to offer the protection Redis sought while satisfying open-source purists and the broader community.
However, Valkey's established ecosystem with hyperscaler backing presents a formidable alternative. The market may now permanently have two competing Redis-compatible projects, with enterprises choosing based on their compliance needs and vendor relationships.
Explanation Of The Licensing Models Mentioned
Here's the revised section with full license naming:
Understanding the Licensing Models
Redis's journey through various licensing models reflects a broader industry struggle to balance open-source principles with business sustainability. Now operating under a tri-license system, Redis 8 offers unprecedented flexibility – though with important distinctions:
The Three Licenses Explained
1. BSD 3-Clause License (Historical)
- Used for Redis 7.2.x and earlier versions
- Completely permissive: allows unlimited commercial use
- No restrictions on cloud providers
- The license that made Redis ubiquitous
2. GNU Affero General Public License v3 (AGPLv3) (Current Option)
- True open source: approved by the Open Source Initiative
- Network copyleft: requires sharing modifications when running as a service
- Designed to prevent "SaaS loophole" in traditional GPL
- Acceptable to most enterprises with proper compliance procedures
3. Server Side Public License v1 (SSPLv1) (Current Option)
- Not recognized as open source by Free Software Foundation or Open Source Initiative
- Specifically targets cloud providers offering Redis as a service
- Requires sharing all "service provider" code if offering as a managed service
- The license that triggered the community exodus and ValKey fork
4. Redis Source Available License v2 (RSALv2) (Current Option)
- Proprietary license created by Redis Ltd.
- Prevents commercial use without permission
- Allows studying, modifying, and personal use
- Stricter than SSPL for commercial enterprises
Conclusion
Redis's return to open source under AGPLv3 is a significant development, but the landscape has fundamentally changed. With hyperscalers firmly behind Valkey and the community wary of future license changes, Redis must now compete not just on features but also on trust and stability. Time will tell if this approach successfully resolves the tension between open source ideals and commercial sustainability, or if Valkey has already won the hearts and infrastructure of the cloud computing giants.