Posts

Redis or Valkey? And Now What?

·
6 min read

When Redis changed its license and the community forked it into Valkey, every team running Redis had to ask: and now what? What I found digging into it, and the question I now ask of every piece of our stack.

How I Think
Redis
Valkey
Open Source
Thoughts
A single tree trunk splitting into two branches, one with red leaves labelled Redis and one with blue leaves labelled Valkey

“And now what?” That was the question on the table in March 2024, when Redis changed its license. We’ve been using Redis for years. It’s one of those pieces that sits at the heart of the system and that you rarely think about. Suddenly we had to think about it: do we stay with Redis, or do we move to Valkey, the fork the community had just created?

I spent a good while reading about it, trying to understand what had really happened and what it meant for us. This is what I found. The facts are linked at the end. The opinions are my own, not my employer’s.

What happened

To understand the fork, you have to remember that behind Redis there is a company. And a company needs to make money.

The problem was the cloud providers. They were offering Redis as a managed service and charging their customers for it, without paying Redis. They were allowed to: Redis was open source, under the BSD license. The CEO, Rowan Trollope, put it this way: the cloud providers “commoditize Redis’ investments and its open source community.”

So on March 20, 2024, Redis closed the door. Starting with Redis 7.4, it moved to a source-available license, and offering Redis as a service required a commercial agreement with the company. Everything up to Redis 7.2.4 stayed under the BSD license.

That’s the part of open source people tend to forget. Whoever controls a project decides what happens to it, even whether it stays open at all. That’s the big freedom open source gives you. And Redis used it.

The response came fast. Eight days later, on March 28, Valkey was born: a fork of Redis 7.2.4 under the Linux Foundation, keeping the BSD license. It was started by Madelyn Olson, one of the Redis maintainers, who worked at AWS, together with engineers from Alibaba, Tencent, Ericsson, Huawei and Oracle.

Was it fair?

Redis was within its rights. The question is whether it was fair.

Redis wasn’t built by one company. For years, many people who didn’t work at Redis contributed to it. Some were paid by their employers to do it. Many gave their own time, for free. They were building something meant for everyone to use. Changing the rules on top of all that work may be legal, but I don’t think it’s fair.

I also think it was a mistake. There are other ways to make money from a project you lead. You’re in the best position to help companies adopt it, to advise them on how to use it and how to use it well. That’s a business too. Redis chose the direct route instead: make the cloud providers pay. And on the way, it broke the trust of the people who had helped build it.

To me, Valkey is the community saying: this can’t happen again. A piece as important as Redis, running all over the world, can’t depend on the decisions of a single company.

It’s the same reason I value projects like the Linux kernel and Python, and the foundations that protect them. They let us keep moving forward without a company showing up one day, taking control of something we all depend on, and closing it. That control belongs to humanity.

And now what?

The story still had a twist. At the end of 2024, antirez, the creator of Redis, announced he was going back to the company. In May 2025, Redis 8 added the AGPLv3 license, and Redis was open source again.

The official version is that antirez pushed for it, and I believe he did. But I don’t think that’s the whole story. This wasn’t the plan in March 2024. By one count, a year after the license change, Redis had lost most of its external contributors, while Valkey kept growing. It looks a lot like a response.

And there’s a detail worth noticing: the same CEO announced both changes. The company that closed Redis is the company that reopened it. Which means it could change the license again.

So the question didn’t go away. And it isn’t free to answer. Moving means preparing for the change: the infrastructure, deciding which branch to follow, the client libraries, the connections, making sure everything stays compatible. You’ll test it in staging, of course. You won’t just cross your fingers. But it’s slow, careful work, and none of it would be needed if the project hadn’t split.

The first thing I looked at was where each project is heading, because since the split they have diverged. Both are getting faster, to be fair. Redis 8 shipped a long list of performance improvements. But for me, its headline was AI: vector sets and a query engine. Valkey has been obsessed with throughput. Valkey 8.0 roughly tripled it with a new I/O threading model, and each release since has pushed further. Even the client libraries split: in Python, valkey-py is a fork of redis-py.

For us, that difference matters. As I showed in my talk at EuroPython 2026 in Kraków, performance is critical in our system. Calls like HGETALL and HSET take milliseconds, and that’s where a big part of our time goes. Any improvement there benefits us directly. We don’t need vector sets or a query engine. We need those calls to be faster. That’s why I lean towards Valkey.

Who controls it?

The second thing I looked at matters more to me than performance, and it’s the lesson I’m taking from all this. When you choose a technology, don’t only ask whether it’s good. Ask how much control you have over it.

Today, Redis is open source again. But one company decides its future. Valkey is governed by a foundation, with many companies behind it, and no single one of them can close it.

That doesn’t make Redis the wrong choice for everyone. If you need what only Redis offers, like vector sets, or you want support from the company that leads it, Redis makes sense. And a foundation isn’t a guarantee either: it only works as long as the companies behind it stay involved. But at least you know what you’re betting on.

We used Redis for years without ever asking who controlled it. Now, for me, it’s the key question when choosing a technology. So, look at your own stack. Who controls it?

References