Yes, Redis is open source again, but with a specific and important caveat: the core data store is now licensed under the AGPLv3, while certain optional modules remain under the source-available RSALv2 or SSPLv1. This change, announced in March 2025, reverses the controversial 2024 switch to a source-available license and returns the core to a true OSI-approved open source license, though the full ecosystem is not entirely open source.
Background: The 2024 License Change
In March 2024, Redis Ltd. (then Redis Inc.) changed the license of the Redis core from the permissive BSD-3-Clause to a dual license: RSALv2 (Redis Source Available License) and SSPLv1 (Server Side Public License). The stated reason was to prevent cloud providers, particularly AWS, Google Cloud, and Azure, from offering Redis as a managed service without paying for it. This move effectively made Redis “source-available” rather than “open source” under the OSI definition, because the licenses restricted how the software could be used (e.g., you couldn’t offer it as a managed service).
This triggered a fork: the Linux Foundation launched Valkey in March 2024, based on the last BSD-licensed Redis code, and quickly gained backing from major cloud providers and companies like Amazon, Google, Oracle, and Ericsson. Redis Ltd. continued developing Redis under the new license, but the community and many enterprises saw the fork as a safer bet for long-term open source stability.
The 2025 Reversal: What Changed
In March 2025, Redis Ltd. announced it was moving the Redis core back to an open source license: AGPLv3 (GNU Affero General Public License v3). This is a strong copyleft license that requires anyone who modifies the code and offers it as a network service to release their modifications under the same license. It is OSI-approved, so the core Redis is again “open source” in the official sense.
However, the company kept some modules under the source-available RSALv2 and SSPLv1 licenses. These include Redis Stack modules like RediSearch, RedisJSON, RedisTimeSeries, and RedisBloom. The core data structures (strings, hashes, lists, sets, sorted sets, streams, etc.) are AGPLv3, but the extended functionality is not.
Why AGPLv3 and Not BSD or MIT?
Redis originally used the permissive BSD license, which allows anyone to use, modify, and distribute the code with minimal restrictions, including in proprietary software. The company chose AGPLv3 for the core because it provides a middle ground: it allows broad use, but if you modify Redis and offer it as a network service (e.g., a hosted Redis), you must share your modifications with users. This is designed to prevent cloud providers from taking the code, adding improvements, and offering it as a service without contributing back.
This is a different approach from the 2024 licenses, which outright prohibited offering it as a managed service without a commercial agreement. AGPLv3 is more permissive, but still copyleft. It’s a strategic choice to satisfy the open source community while still protecting against free-riding cloud providers.
What This Means for Users and Companies
For most users, the practical impact is minimal if you use Redis as a database or cache in your own applications. The AGPLv3 license allows you to use it internally without any obligation to open-source your own code, as long as you don’t modify Redis itself and offer it as a network service. If you do modify Redis and offer it as a service (like a managed Redis provider), you must release your modifications under AGPLv3.
For cloud providers and managed service vendors, the situation is nuanced. They can now offer Redis as a service, but if they modify the core, they must open-source those modifications. They can still use the source-available modules under RSALv2/SSPLv1, but those have separate restrictions (e.g., RSALv2 prohibits offering the module itself as a managed service).
For developers, the main consideration is whether you need the Redis Stack modules. If you only use core Redis, you’re fine with AGPLv3. If you need RediSearch or other modules, check their specific licenses and whether that affects your use case.
Comparison: Redis vs. Valkey vs. KeyDB
- Redis (AGPLv3): The original, now open source core. Most features, largest ecosystem, but some modules are not open source.
- Valkey (BSD-3-Clause): Fork from the last BSD Redis (7.2.4). Fully open source, permissive. Backed by Linux Foundation and major cloud providers. Lacks some newer Redis features but is API-compatible with Redis 7.2.
- KeyDB (BSD-3-Clause): A long-standing fork of Redis, focused on multi-threading and higher performance. Also fully open source, but less active than Valkey.
If you need the latest Redis features (like vector sets or new data types), Redis is the choice. If you want a stable, permissively licensed drop-in replacement, Valkey is strong. KeyDB is an option if you need multi-threaded performance.
Common Misconceptions
“Redis is now fully open source again” – Not entirely. The core is AGPLv3, but the Redis Stack modules are not. Check the license of every module you use.
“AGPLv3 means I have to open-source my entire application” – False. You only need to release modifications to the Redis code itself, not your own application that uses Redis. If you don’t modify Redis, you have no obligation.
“Valkey is a drop-in replacement” – Mostly yes, but there are subtle differences in configuration options and some commands. Test thoroughly before migrating.
How to Choose: Redis or Valkey?
Consider the following:
- Licensing comfort: If you want a permissive license (no copyleft), Valkey or KeyDB. If you’re okay with AGPLv3 for the core, Redis.
- Feature needs: If you need Redis Stack modules (search, JSON, time series), Redis is the only real option. Valkey has some modules but not all.
- Support and ecosystem: Redis has the largest ecosystem, but Valkey is backed by the Linux Foundation and major cloud providers, so it’s growing fast.
- Migration effort: If you’re already on Redis 7.x, switching to Valkey is almost seamless. If you’re on Redis 8.x, you might need to wait for Valkey to catch up.
Frequently Asked Questions
Is Redis free to use now?
Yes, the core Redis is free under AGPLv3, which is an open source license. You can use it in commercial products without paying, as long as you comply with the copyleft terms (release modifications if you offer it as a network service).
Can I use Redis in my commercial SaaS product?
Yes, you can use the core Redis in your SaaS product without open-sourcing your own code, as long as you don’t modify Redis and offer it as a service. If you do modify Redis and offer it as a service, you must release your modifications.
What happened to the Redis fork Valkey?
Valkey continues to be developed independently under the BSD license. It remains a popular choice for those who prefer a permissive license. The Redis license change doesn’t affect Valkey’s status.
Are the Redis Stack modules open source?
No, the Redis Stack modules (RediSearch, RedisJSON, etc.) are under the source-available RSALv2 or SSPLv1 licenses. They are not OSI-approved open source, but you can still use them for free in most cases, subject to restrictions on offering them as managed services.
Do I need to worry about AGPLv3 if I just use Redis as a cache?
No. Using Redis as a cache in your application does not trigger any AGPL obligations, because you are not modifying Redis or offering it as a service. You’re just using it as a tool.
Will Redis change its license again?
There’s no indication of that, but the history shows it’s possible. To hedge, some companies are standardizing on Valkey to avoid future license surprises. It’s a risk assessment decision.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Fisch Sea 2 Animals Bestiary Guide
- Git Push Origin: What It Does and How to Use It
- AI Agents vs Chatbots: What Each Can Do
- OnePlus Nord 6 vs Vivo V70 Elite: Key Specs, Prices, Buying Trade-offs
- Galaxy M36 vs Redmi Note 15 SE 5G: What to Know Before Choosing
- Does IFTTT Need to Stay Open for Applets to Run?