Valkey vs Redis in 2026: When to Pick the Fork
The April 2024 Valkey fork changed the decision from two-way to three-way. Here is when to pick which.
Redis 8.0 vs Valkey 8.1: side-by-side spec table
| Feature | Redis 8.0 | Valkey 8.1 |
|---|---|---|
| License | RSALv2 / SSPLv1 / AGPLv3 (tri) | BSD-3-Clause |
| OSI open source | Yes (under AGPLv3 only) | Yes (BSD is OSI-approved) |
| RESP protocol | Yes | Yes (drop-in compatible) |
| Vector sets (HNSW) | Yes (Redis 8.0, May 2025) | Not yet (early 2026) |
| Hash field TTL | Yes (Redis 8.0) | In development |
| Multi-threaded I/O | Yes (I/O threads) | Yes (redesigned in 8.0, 30-35% gain) |
| Memory efficiency at scale | Baseline | ~28% lower at 50M sorted-set entries (Momento, independent) |
| Backed by | Redis Inc | Linux Foundation (AWS, Google, Oracle, Ericsson) |
| AWS managed | Available (ElastiCache Redis OSS) | Default for new AWS ElastiCache deployments |
| GCP managed | Memorystore for Redis (legacy) | Memorystore for Valkey (default) |
| Aiven managed | Aiven for Redis (legacy) | Aiven for Valkey (primary, ~20% cost savings) |
| Current version | 8.0.x | 8.1.x |
Sources: Redis 8.0 GA blog, valkey.io, Momento benchmark
Pick Valkey if...
SSPL or AGPLv3 blocks your licensing approval
If your legal or procurement team has flagged Redis 7.4+ as non-compliant (SSPL or RSALv2 concerns), Valkey's BSD-3 license is the clean path. No copyleft, no managed-service restrictions, no OSI grey area.
You are on AWS ElastiCache or Google Memorystore already
Both clouds default to Valkey for new deployments since 2024-2025. If you created a new cluster recently, you may already be on Valkey. Check your cluster engine version in the console.
Memory efficiency at scale matters
Valkey 8.1 shows ~28% lower memory at 50M sorted-set entries vs Redis 8.0 in the Momento independent benchmark. At hyperscale, that is a real cost difference. Source: Momento (independent, AWS c8g.2xlarge Graviton4).
You want OSI-approved permissive open source with no commercial entity gatekeeping
Valkey is governed by the Linux Foundation, not a single commercial entity. The BSD license has no strings. Redis Inc's RSALv2 and SSPL explicitly restrict how you can use Redis commercially.
You do not need Redis 8.0-specific features yet
If you do not need vector sets (HNSW-based similarity search), hash field TTL, or vendor-supported Redis Cloud SLAs, Valkey covers your workload. Valkey 8.1 is compatible with the Redis 7.2 command set in full.
Pick Redis 8.0 if...
You need vector sets for AI / RAG workloads
Vector sets (VADD, VSIM, VDIM commands, HNSW algorithm) shipped in Redis 8.0 (May 2025). As of early 2026, Valkey has not shipped an equivalent. If your pipeline needs on-Redis vector similarity search, stay on Redis 8.0.
You need hash field TTL
HEXPIRE (per-field TTL on hashes) is a Redis 8.0 feature. Valkey's roadmap includes it but it was not in 8.1 as of early 2026. If your session or metadata patterns rely on per-field expiry, Redis 8.0 is required.
You rely on Redis Stack modules (RedisJSON, RediSearch, RedisGraph)
Redis Stack modules are Redis Inc proprietary. They do not run on Valkey. Valkey ecosystem alternatives are emerging but immature in early 2026. If your workload depends on RedisJSON or RediSearch, migrating to Valkey requires finding alternatives first.
You have commercial Redis Cloud SLAs
Redis Inc provides enterprise support contracts and Redis Cloud SLAs. If you have a commercial Redis Inc agreement, staying on Redis 8.0 preserves that relationship. Valkey has managed providers (Aiven, AWS, GCP) but no Redis Inc SLA.
Migration playbook: Redis to Valkey
Aiven migrated 15,000 servers from Redis to Valkey in 3 months (May-August 2024). Here is the general playbook.
Verify command compatibility
Valkey is drop-in for Redis 7.2.4 baseline. Most Redis 7.4-compatible commands work too. Scan your codebase for Redis 8.0-specific commands (vector sets, hash field TTL) before migrating. Source: valkey.io compatibility docs.
Identify Redis Stack module dependencies
RedisJSON, RediSearch, RedisGraph do not run on Valkey. If your app uses these, migration requires replacing them first. Valkey ecosystem alternatives are emerging but check readiness for your use case.
Stand up Valkey alongside Redis
Run both in parallel. Configure your application to dual-write to both stores for one to two weeks. This validates data compatibility and gives you a rollback path without downtime.
Cutover and monitor
Flip reads to Valkey. Monitor hit rates, latency, and error rates. Valkey's RESP protocol compatibility means most clients (ioredis, redis-py, Jedis) work without code changes. Keep Redis warm for one week post-cutover before decommissioning.
Aiven migration reference: Valkey blog: 2024 year of Valkey
Expect one quarter of CI/staging/prod cutover work for a non-trivial migration. The CI cost compounds. CI/CD Cost Calculator →
Verdict: 2026
For most 2026 commercial shops with license sensitivity, Valkey is the lower-risk pick. Redis 8.0 is the higher-feature pick. If you are on AWS ElastiCache or Google Memorystore and created a new cluster recently, you may already be on Valkey. Check before migrating. Cache stack cost is one node in the broader tech stack decision. Tech Stack Cost →