Redis and Valkey Part 2: The Licensing Shift and the Rise of Valkey
February 02, 2026
This is Part 2 of our four-part series on Redis and Valkey. In Part 1, we examined the business value these technologies provide. Now we'll explore the licensing changes that led to Valkey's creation and what they mean for businesses.
The Redis Licensing Shift
The recent upheaval in the Redis ecosystem stems from licensing changes. Redis was originally released under the permissive BSD license, which allowed companies to use, modify, and integrate it freely. However, in 2018, Redis Labs (now Redis Inc.) introduced the Redis Source Available License (RSAL) for certain modules, and in 2021, they switched the core Redis database from BSD to RSAL.
The latest change came in 2023 when Redis Inc. moved from RSAL to the Redis Server License (RSL), which further restricts certain use cases, particularly for cloud providers offering Redis as a service.
Understanding the BSD License (Original)
The original BSD license was permissive:
- Use Redis for any purpose
- Modify the source code
- Distribute modified versions
- Offer Redis as a service
- No licensing fees ever
This openness enabled Redis's massive adoption. Companies could:
- Deploy without vendor approval
- Modify for specific needs
- Bundle with products
- Offer as managed services
The Shift to RSAL (2018-2021)
Redis Labs introduced RSAL for add-on modules:
- Restricted offering Redis modules as a competing service
- Still allowed internal use and modification
- Created uncertainty about open source status
- Aimed at protecting against cloud providers
This change primarily affected cloud providers offering Redis services, not most users.
The Move to RSL (2023)
The Redis Server License brought more significant restrictions:
What RSL Allows:
- Internal use within organizations
- Modification for internal purposes
- Hosting Redis for your own applications
- Most typical business uses
What RSL Restricts:
- Offering Redis as a database service to others
- Certain types of commercial redistribution
- Competing directly with Redis Inc.'s offerings
Why Redis Inc. Made These Changes
Understanding Redis Inc.'s motivations provides context:
Cloud Provider Competition: Major cloud providers (AWS, Google Cloud, Azure) offered managed Redis services without contributing back to Redis development or paying Redis Labs. This "strip mining" of open source projects became unsustainable.
Business Sustainability: Redis Inc. needed revenue to fund development, support, and growth. The permissive license made monetization difficult.
Market Reality: The open-source sustainability crisis affects many projects. Redis Inc. sought a middle ground — accessible to users but protected from cloud providers offering it as a commodity.
Impact on Different Organizations
The licensing changes affect organizations differently:
Minimal Impact:
- Using Redis internally for your own applications
- Deploying Redis to support your product
- Standard business use cases
- Most small to medium businesses
Moderate Impact:
- Large enterprises with complex licensing reviews
- Organizations planning internal "platform" services
- Companies with risk-averse legal departments
- Open-source purists who prefer OSI-approved licenses
Significant Impact:
- Cloud providers offering Redis as a service
- Platform companies reselling Redis capabilities
- Competitors to Redis Inc.'s offerings
- Organizations with strict open-source requirements
The Rise of Valkey
Valkey emerged in early 2024 as a community fork of Redis, maintaining the BSD license. Led by Amazon Web Services, LaunchBadge, and several Redis core contributors, Valkey aims to preserve the open source nature of the project while continuing its development.
The Valkey fork represents a significant moment in the open source world. It is not just about licensing – it is about governance, community involvement, and the long-term stability of critical infrastructure.
Why Valkey Emerged
Several factors drove Valkey's creation:
Licensing Concerns: Organizations uncomfortable with RSL restrictions wanted an alternative with clear open-source licensing.
Governance: The community wanted input into Redis's direction, not just Redis Inc.'s commercial priorities.
Long-term Certainty: Concerns that future license changes could further restrict usage drove demand for a community-controlled alternative.
Cloud Provider Interests: Major cloud providers wanted to continue offering Redis-compatible services without RSL restrictions.
Who's Behind Valkey
The Valkey project has already gained substantial traction, with major cloud providers including AWS, Google Cloud, and Oracle Cloud backing it. This support suggests Valkey will likely have the resources needed for ongoing development and maintenance.
Key Supporters:
- Amazon Web Services: Major contributor and advocate
- Google Cloud: Backing and planning support
- Oracle Cloud: Committed to Valkey
- Former Redis contributors: Core developers who forked
- Linux Foundation: Providing governance structure
This backing provides confidence in Valkey's longevity and development velocity.
Valkey's Governance Model
Valkey uses open governance:
- Community-driven development: Not controlled by a single vendor
- Transparent decision-making: Public discussions and roadmaps
- Meritocratic contributions: Anyone can contribute
- Linux Foundation oversight: Neutral governance structure
This model contrasts with Redis Inc.'s commercial control, appealing to organizations that value community governance.
The Open Source Philosophy
The fork reflects deeper questions about open source:
Business vs. Community: Can open source projects sustain themselves commercially while remaining truly open?
Cloud Provider Responsibility: Should cloud providers contribute more to projects they monetize?
License Changes: Is changing licenses on established projects fair to users who built on original terms?
Sustainability: How do we ensure critical infrastructure remains maintained without exploitative commercial practices?
Valkey represents one answer: community fork with diverse backing.
The Practical Reality for Businesses
For most businesses using Redis, the immediate impact is minimal:
If you're using Redis internally: The RSL likely doesn't affect you. Continue using Redis with confidence.
If you're planning new implementations: Consider both Redis and Valkey. Evaluate based on your specific needs and risk tolerance.
If you have strict open-source requirements: Valkey's BSD license might be preferable for policy compliance.
If you're a cloud provider: Valkey provides a path to continue offering Redis-compatible services.
Coming Up
In Part 3, we'll examine the technical differences between Redis and Valkey, including compatibility considerations and how the projects are diverging. Part 4 will provide a framework for making strategic decisions between them.
The licensing shift and Valkey's emergence create choice where none existed before. Understanding the context helps businesses make informed decisions about their in-memory data infrastructure.