Redis vs Valkey: The Open-Source Fork War Explained
Redis vs Valkey 2026 — explaining the BSL license fork, Valkey 8.0 performance benchmarks, cloud provider migration, and which to choose for new projects.
Quick Answer
Valkey 8.0 is the pragmatic open-source choice in 2026 — it is a drop-in Redis replacement under GPL license, backed by major cloud providers, and already replacing Redis in AWS ElastiCache and GCP Memorystore. Redis 7.4+ is the better choice only if you use Redis-proprietary modules (RedisJSON, RediSearch) or Redis Cloud specifically.
Redis vs Valkey: Overview
Redis Cloud users, RedisJSON/RediSearch module users, legacy Redis stacks
Redis Cloud free: 30MB; open-source BSL self-host free for non-competing use
Redis Cloud Essentials from $7/mo; Pro from $35/mo; Enterprise custom
New projects, cloud-agnostic deployments, teams avoiding BSL license risk
Fully open-source GPL v2; ElastiCache Valkey free tier (AWS); self-host free
AWS ElastiCache Valkey from $0.017/hr; Aiven Valkey from $19/mo; self-host free
Redis vs Valkey: Feature Comparison
| Feature | Redis | Valkey |
|---|---|---|
| License | BSL 1.1 (non-compete clause) | GPL v2 (Linux Foundation)Winner |
| AWS ElastiCache / GCP Memorystore | Removed — providers migrated to Valkey | Default engine on ElastiCache, MemorystoreWinner |
| Module ecosystem (JSON, Search) | RedisJSON, RediSearch, RedisTimeSeriesWinner | No equivalent modules |
| Single-threaded throughput | ~100K ops/sec (Redis 7.2) | ~100K ops/sec + MT I/O (Valkey 8.0) |
| Drop-in compatibility | N/A — original | RESP3 protocol, same commands, same clientsWinner |
| Multi-region active-active | Redis Cloud CRDTs (proprietary)Winner | Not available yet |
Pros & Cons
Redis
Pros
- Redis 7.2 is production-proven with 10+ years of battle testing at Twitter, GitHub, and Airbnb scale
- RedisJSON module provides native JSON storage with JSONPath queries — no JSONB translation needed
- RediSearch adds full-text search and vector similarity (Redis Vector Library) in a single deployment
- Redis Cloud provides active-active geo-replication with CRDTs for conflict-free multi-region writes
- Redis Insight GUI tool provides real-time monitoring, slow log analysis, and memory profiler
Cons
- BSL license (since Redis 7.4, March 2024) prohibits cloud providers from offering Redis as a service
- AWS, GCP, Azure, and major cloud providers have migrated managed services away from Redis to Valkey
- BSL license creates uncertainty for internal deployments at companies competing with Redis Inc.
- RedisJSON and RediSearch modules are proprietary to Redis Inc. — not available in Valkey
Valkey
Pros
- Valkey 8.0 (November 2024) introduces multi-threaded I/O matching Redis 7.2 benchmarks within 5%
- GPL v2 license under Linux Foundation — no commercial use restrictions, no BSL ambiguity
- Drop-in Redis replacement: same RESP3 protocol, same commands, same client libraries work unchanged
- AWS ElastiCache, GCP Memorystore, Aiven, and Upstash have officially migrated to Valkey
- Valkey 8.0 adds dual-channel replication that reduces replication lag by 60% during heavy writes
Cons
- No equivalent to RedisJSON, RediSearch, or RedisTimeSeries modules — core only
- Smaller commercial support ecosystem vs Redis Inc.'s enterprise support contracts
- Valkey 8.x is <2 years old — less production history than Redis 7.x for edge cases
- Redis Cloud active-active geo-replication (CRDT-based) has no Valkey equivalent yet
Our Verdict: Redis vs Valkey
Use Valkey 8.0 for all new projects in 2026 — it is already the default in AWS ElastiCache, GCP Memorystore, and Aiven, and the GPL license removes all BSL ambiguity. Your existing ioredis, redis-py, and Jedis clients work without changes. Use Redis only if you specifically need RedisJSON for native JSON storage, RediSearch for full-text/vector search, or Redis Cloud active-active CRDT replication — these modules have no Valkey equivalent. For the 90% of use cases that need caching, pub/sub, and sorted sets, Valkey 8.0 is the better choice today.
Redis vs Valkey — FAQs
Why did Valkey fork from Redis in 2024?
Redis Inc. changed its license from BSD (open source) to BSL 1.1 (Business Source License) in March 2024 with Redis 7.4. BSL prevents companies from offering Redis as a managed cloud service — effectively blocking AWS, GCP, and Azure from their ElastiCache/Memorystore Redis products. In response, major contributors from AWS, Google, Oracle, and Ericsson forked Redis at the last BSD-licensed commit (7.2.4) and donated the fork to the Linux Foundation as Valkey. The fork process took three weeks, and Valkey 7.2.5 shipped in April 2024 as a drop-in replacement.
Is Valkey 8.0 faster than Redis 7.2?
Valkey 8.0 is roughly equivalent to Redis 7.2 on single-threaded benchmarks — within 2-5% on standard GET/SET workloads. The significant improvement is dual-channel replication in Valkey 8.0, which reduces replication lag by 60% during write-heavy periods by separating the replication data stream from control messages. Valkey 8.0 also adds I/O threading improvements that reduce p99 latency at high connection counts (1,000+ concurrent clients). For most production workloads, performance is functionally identical; the licensing difference is the primary decision factor.
Can I migrate from Redis to Valkey without changing my application code?
Yes. Valkey speaks the identical RESP2/RESP3 protocol as Redis, so all Redis client libraries — ioredis, redis-py, Jedis, StackExchange.Redis — connect to Valkey without any code changes. Redis commands, data types (strings, hashes, lists, sorted sets, streams, HyperLogLog, geo), and replication/cluster semantics are identical. The only migration steps are: update your connection string to point to Valkey, and verify you do not use Redis-proprietary modules (RedisJSON, RediSearch). If you use those modules, migration requires replacing them with application-layer logic or alternative tools like Typesense for search.
Try the Best AI Platform — Free
Assisters brings the best of AI together in one platform. No credit card required to start.