Redis has always been the go-to when you need fast, in-memory data storage. You’ll find it everywhere. Big ecommerce sites. Mobile apps. Maybe your own projects, too.
But if you’re relying on Redis today, you’re facing a new reality: the licensing terms have changed, and that shift could affect the way you use Redis going forward.
The new Redis license isn’t just some boring legal update; it affects how teams deploy, share, and even build with Redis. This especially matters if you run large apps or offer managed services. There’s a lot of noise and confusion out there. Let’s clear it up.
We’ll cover:
- What’s actually different now
- What new risks or headaches you should know about
- What you can do to keep your options open
So, what changed with the Redis license?
If you’ve used Redis for a while, you probably remember the old days. No licensing headaches. Just download and go. That changed with Redis 7.4.
Here’s what’s new:
No more BSD freedom
Redis is no longer what most people consider “open source.” The BSD license made Redis simple to use anywhere, for anything. That’s off the table now. If you care about open source, this is a real change.
A tangle of new licenses
Redis now ships under three different licenses:
- AGPLv3: Open source in name, but much stricter. If you run Redis as a networked service and tweak the code, you’re expected to release those changes.
- RSALv2 (Redis Source Available License): You can use Redis for your own projects and apps, but offering it as a managed service is prohibited.
- SSPLv1: Even stricter. If you provide Redis as a service, you’d have to share your whole service codebase with the world.
Features may have different rules
Not everything in Redis uses the same license now. Some new features or modules might only come under stricter terms. You’ll need to check before you upgrade or add anything new.
Managed and hosted services are the big target
If you’re just running Redis for your own business, you might not notice an immediate difference. But if your company offers Redis as a cloud or SaaS feature, you’re now facing legal and operational roadblocks. Even if you’re running internal platform services, you need to know where you stand before rolling out new versions.
Packaging is already changing
Some Linux distributions and package managers are dropping Redis or moving slowly on updates because it no longer fits their open source policies. That means installing or upgrading Redis could become more complicated over time.
Upgrades come with homework
For most teams, the days of “just update Redis” are probably over. Now, every new release might require a legal review. This adds friction, but it’s necessary to avoid headaches later.
The community is splitting
The licensing change sparked the creation of Valkey, a fully open source fork now led by the Linux Foundation. This may lead to Redis and Valkey going in different directions over time.
The bottom line: The Redis license change affects how you use, update, and build on Redis. If open source, flexibility, or avoiding vendor surprises are important to you, you’ll want to pay close attention.
What does this mean for teams using Redis?
If you’re running Redis today, this license change isn’t something to ignore. The practical effects depend on how you use Redis and where your organization is heading.
For teams using Redis internally: You’ll probably keep humming along for now. But start making a habit of reading the license notes before any upgrade or new feature. Some releases may add new rules.
If your company offers Redis as a managed, hosted, or SaaS solution: This is where the impact is immediate. The new license blocks you from offering Redis as a service unless you want to share your code or make a commercial deal. If Redis is something you sell, you need to review your plans asap.
For those embedding or distributing Redis in a product: Shipping Redis as part of your hardware or software? The new license affects what you can include, support, or even update. Every new release could change your requirements. Loop in your legal and product teams.
Upgrade planning is now a team sport: It’s not just about the latest features anymore. Upgrades may need input from legal, compliance, and support. The risk isn’t only technical; it’s legal and operational, too.
Expect some ecosystem shakeups: With open source distributions and package managers rethinking their relationship with Redis, you may find updates or support less straightforward than before. Plan for extra steps.
Are there open source alternatives to Redis?
Yes. If your team depends on open source software, or you just want to skip future licensing headaches, you’re not out of luck. As mentioned earlier, the community quickly responded to the Redis license change by launching Valkey, a new fork of Redis. Valkey is governed by the Linux Foundation and released under the permissive BSD license, so it remains fully open source and free from vendor lock-in.
Valkey aims to deliver the familiar speed and flexibility teams expect from Redis, while protecting the open source values many organizations rely on. For some, it’s a direct path to keeping their data infrastructure simple and predictable.
Of course, switching technologies raises its own set of questions. That’s where having the right support and guidance becomes critical.
Need help making sense of it all? We’ve got your back.
Licensing changes shouldn’t leave you stuck, scrambling, or second-guessing your next move. Whether you’re planning to stay on Redis, exploring Valkey, or just want to make sure your current environment stays secure and high-performing, having the right support matters more than ever.
That’s exactly why Percona offers 24/7, enterprise-grade support and consulting for both Redis and Valkey. Our team has experience with both technologies, and our only agenda is making sure you have what you need to run reliably.
Thinking about migrating? Need help with compliance, upgrades, or day-to-day operations? We’re here to help you chart the best path forward on your terms.
Learn more about Percona Support for Redis and Valkey
