Valkey: the open source successor to Redis you need to know | by Mr. Ali Khan | October 2025

When Redis Labs changed the Redis licensing model in 2024, it sent shockwaves through the open source and cloud ecosystems. Suddenly, what had long been the cornerstone of in-memory caching, session storage, and message brokering was no longer fully open source.

Enter walkie – the community fork of Redis which is determined to keep the original spirit of the project alive. Built and maintained under the Linux FoundationValkey is not just another clone, it is a modern and open alternative that is already gaining ground as a true successor to Redis.

Why Valkey exists

In March 2024, Redis Labs renewed the Redis license of BSD has RSAL (Redis Source license available) – a decision that limited how businesses could use Redis in commercial cloud environments.

The move left developers, businesses, and open source contributors searching for a new, transparent alternative. In a few weeks, the main players, notably AWS, Google and Alibaba Cloud — collaborated with the Linux Foundation to create walkieensuring that the Redis ecosystem remains open and governed by the community.

In short:
Valkey = Open-Source Redis + Long-term community governance.

What is Valkey?

walkie is a high-performance in-memory key-value data storefully compatible with Redis 7.x, designed to serve as a drop-in replacement for most use cases.

He maintains:

• THE same protocol And data structures (Strings, lists, sets, sorted sets, hashes).
• THE same commands (GET, SET, HGETALL, ZADDetc.).
• Cluster mode, replicationAnd persistence features (RDB and AOF).

This means that most applications that use Redis today can move to Valkey. with zero code changes.

Installation and compatibility

You can install Valkey from source or through package managers.
For example, on Ubuntu:

sudo apt update
sudo apt install valkey-server valkey-cli

Or using Docker:

docker run -d --name valkey -p 6379:6379 valkey/valkey:latest

To log in:

valkey-cli ping
# PONG

If you know redis-cliyou’ll feel right at home — Valkey intentionally reflects the Redis development experience.

Performance and references

The first community benchmarks show that Valkey is efficient on par or slightly better than Redis 7.x in most scenarios.
The architecture is optimized for modern processors and multi-core scaling, with a continued focus on:

• Efficiency of event-driven I/O
• Support for threaded networks
• Optimized memory footprint
• Faster snapshot persistence (RDB)

It is also fully backwards compatibleso that libraries and SDKs written for Redis in Python, Go, Node.js or Java work seamlessly.

Who supports Valkey?

Valkey is managed under Linux Foundation and supported by major organizations like:

• Amazon Web Services (AWS)
• Google Cloud
• Alibaba Cloud
• Oracle
• Microsoft Azure engineers (individual contributors)

This support ensures that Valkey is not dependent on the interests of a single company: it is owned by the community, just as Redis was intended to be.

Main features of Valkey

1. Full Redis protocol compatibility
   Works out of the box with all Redis clients, commands, and extensions.
2. High performance in-memory engine
   Designed for sub-millisecond latency with high concurrency.
3. Open governance model
   Decisions made by community managers under the Linux Foundation.
4. Persistence and durability
   RDB snapshots and AOF logs are supported just like Redis.
5. Cluster and Sentinel mode
   Provides horizontal scalability and automatic failover.
6. Evolve beyond Redis
   Valkey aims to innovate faster, without licensing constraints, meaning new features, data structures and integrations are on the roadmap.

Migrating from Redis to Valkey

One of the best aspects of Valkey is the simplicity of migration.
If you’re using Redis 7.x or earlier, the change can be as simple as:

Export your Redis dump:

redis-cli save

(Generates dump.rdb)

Install Valkey and move the dump file:

cp /var/lib/redis/dump.rdb /var/lib/valkey/

Start Valkey:

sudo systemctl start valkey

Valkey will load your Redis dataset without problem: same port (6379), same commands, same data.

Future roadmap

Valkey maintainers focus on:

• Improved multithreaded performance
• Improved cluster resilience
• Better observability (Prometheus metrics, tracing)
• New data types And modular extensions
• Following protocol compatibility with Redis clients

The ultimate goal: to make Valkey open memory by default for cloud-native and distributed applications.

Why developers are excited

The developers see Valkey as more than just a fork: it’s a symbol of open collaboration.

Redis’ license renewal left a trust void; Valkey filled it with transparency and community governance. This is a collective decision by the developer ecosystem to protect open data infrastructure.

As one contributor said:

“Valkey is Redis – without the corporate handcuffs.”

Conclusion

If you are using Redis for caching, pub/sub, or as a primary data store, Valkey is the natural evolution. It retains everything that made Redis great: speed, simplicity, and reliability, but restores what made it truly revolutionary: freedom.

Whether you’re a startup developer or managing large-scale distributed systems, Valkey ensures your in-memory layer remains open, fast, and scalable.