The fight between Valkey vs Redis is the most consequential database fork of the decade. After Redis Inc. abandoned its open-source BSD license in March 2024 for the dual SSPL/RSALv2 model, the Linux Foundation rallied AWS, Google Cloud, Oracle, and Ericsson behind a new project named Valkey, a clean BSD-3-Clause fork led by senior Redis maintainer Madelyn Olson. Two years later, the data is in. Valkey 8.1, released March 31, 2025, runs roughly 8 percent more operations per second than Redis OSS, a throughput edge Percona’s own benchmark data confirms, cuts P99 latency by 22 percent, uses 20 percent less memory – a reduction Redisson’s feature comparison corroborates – and ships on AWS ElastiCache at a 20 percent lower hourly rate, per AWS pricing data still current as of June 2026. Redis Inc. countered by reverting to AGPL in May 2025 and launched Redis 8.0 with vector sets, hash field TTL, and Redis Functions 2.0. Adoption has followed the momentum: Upstash confirms Valkey’s Docker Hub pull count surpassed 100 million in May 2026, a 17-fold year-over-year jump that makes it one of the fastest-growing base images in the caching category. This Valkey vs Redis comparison cuts through the licensing fog with hard 2026 benchmarks, Linux Foundation governance facts, AWS ElastiCache pricing, third-party Percona and ScyllaDB tests, real production case studies from Snap Inc. and Pinterest, and a verdict on which engine your stack should ship in production today.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Valkey vs Redis 2026: Executive Summary and Verdict
The headline numbers are decisive. Valkey 8.1 hits 1.2 million operations per second on r6g.large nodes versus 1.11 million for Redis OSS, an 8 percent throughput edge per Percona Toolkit benchmarks published in 2025. P99 tail latency lands at 1.8 ms for Valkey against 2.3 ms for Redis OSS on cache.m7g.large with mixed read/write traffic, a 22 percent improvement that compounds at high QPS. Memory efficiency is the bigger story: Valkey 8.1’s redesigned hash table drops memory footprint by 20 percent for typical key-value workloads, and AWS measures cumulative savings of 36 percent against Redis OSS 7.2 once the per-node price cut is layered in. Redis 8.0, shipped May 1, 2025, narrows the feature gap with native vector sets backed by HNSW indexing, per-field hash TTL, JSON path queries, and Redis Functions 2.0 with Lua plus WebAssembly support, while Redis’s own May 2025 announcement confirms AGPLv3 arrived as a third license option alongside the existing RSALv2 and SSPLv1 terms. Redis 8.2, GA February 17, 2026, adds client-side caching protocol upgrades and dual cosine-plus-dot-product similarity metrics. By September 2026, Valkey had moved two full versions past 8.1: version 9.0 reached general availability on October 21, 2025 per Cloud Magazin, adding cluster multi-database support, with Tencent Cloud separately confirming it had adopted Valkey 9.0 as the officially released engine behind its Redis-compatible cache service, and the 9.x line kept shipping on a monthly cadence – Valkey 9.1 arrived May 19, 2026 with database-level ACLs and the new CLUSTERSCAN command per ByteIota, 9.1.1 followed in July 2026, and 9.1.2 is the newest GitHub release as of September 2026 – cementing its status as a direct open-source competitor to the entire Redis 8.x line, according to DevOps Daily’s June 2026 ecosystem review. Redis Inc.’s own version counter has kept climbing in parallel: a Redisson feature-comparison update published in May 2026 lists Valkey 9.1.1 against Redis 8.8.0 as the two current stable releases, confirming that Redis has pushed well past the 8.2 baseline this comparison was originally built on. License posture remains the dividing line: Valkey ships under BSD-3, Redis 8 ships under dual BSLLv1 plus AGPL, and that single fact is why Fedora 42, Ubuntu 26.04 LTS, Debian 13 backports, and Arch Linux community now default to Valkey.
For greenfield infrastructure that needs caching, session stores, leaderboards, rate limiting, or pub/sub at scale, Valkey is the safer 2026 default. The license is unambiguous, the AWS bill is lower, throughput is higher, and the Linux Foundation governance protects against another Redis Inc.-style relicense. For workloads that depend on RediSearch, RedisJSON, RedisGraph, RedisTimeSeries, or Redis Vector Sets with HNSW, Redis 8 remains compelling because Valkey’s compatible modules ship slower and Redis Enterprise still leads on active-active CRDB replication. Snap Inc. cut caching infrastructure costs 60 percent by migrating 70 percent of Redis clusters to ElastiCache Valkey in the first half of 2026, dropping from $2.1 million per year to $840,000 per year while serving 5 billion daily requests. That single data point is the clearest economic argument in this Valkey vs Redis showdown.
The Redis Fork Story: License Drama and the Linux Foundation Pivot
The Redis fork did not happen overnight. It started March 20, 2024, when Redis Inc. announced that all future Redis OSS releases would ship under the dual Server Side Public License (SSPL) and Redis Source Available License v2 (RSALv2). The change blocked AWS, Google Cloud, Oracle, and other hyperscalers from offering managed Redis services without a commercial agreement, because both SSPL and RSALv2 require source disclosure for any commercial network deployment. Within seven days, the Linux Foundation announced Valkey on March 28, 2024, with founding contributors AWS, Google Cloud, Oracle, Ericsson, and Snap Inc. Madelyn Olson, a senior Amazon Web Services principal engineer who served as a Redis core maintainer for years, became the project lead. Salvatore Sanfilippo, the original Redis creator known online as antirez, returned to Redis Inc. as a developer in late 2024, signaling that Redis would not abandon community development entirely.
Redis Inc. course-corrected on May 1, 2025, when CEO Rowan Trollope announced that Redis 8.0 would ship under the more permissive Affero General Public License v3 (AGPLv3) alongside the existing Redis Source Available License. AGPL is OSI-approved, but it still imposes copyleft network distribution requirements that hyperscalers consider commercially incompatible. The damage was already done. Valkey had absorbed enterprise mindshare, Linux distributions had switched defaults, and AWS ElastiCache had migrated millions of nodes onto Valkey 7.2. The lesson for infrastructure architects in 2026 is simple: Redis Inc. controls the brand and the commercial roadmap, but Valkey controls the upstream that ships in your operating system, your container base image, and your cloud provider’s managed cache. The Linux Foundation Valkey announcement remains the single most important document explaining how this split happened.
Valkey vs Redis: Complete Specs Comparison Table
| Specification | Valkey 8.1 | Redis 8.2 |
|---|---|---|
| License | BSD-3-Clause | Dual BSLLv1 + AGPLv3 |
| Latest stable release | 8.1.7 (May 6, 2026) | 8.2 (February 17, 2026) |
| Major release date | March 31, 2025 | May 1, 2025 |
| Governance | Linux Foundation, vendor-neutral | Redis Inc., commercial |
| Lead maintainer | Madelyn Olson (AWS) | Yossi Gottlieb / Salvatore Sanfilippo |
| GitHub stars (May 2026) | 18,400 | 65,200 |
| Unique contributors | 320 | 1,850+ |
| Core maintainers | 15 | 25 |
| Throughput (1KB SET, r6g.large) | 1.20M ops/sec | 1.11M ops/sec |
| P99 latency (mixed workload) | 1.8 ms | 2.3 ms |
| Memory overhead | -20% vs Redis 7.2 | Baseline |
| I/O threading | Multi-threaded I/O + TLS offload | Single-thread main + I/O threads |
| RESP protocol | RESP2 + RESP3 | RESP2 + RESP3 |
| Vector search | Module (Valkey-Search) | Native Vector Sets (HNSW) |
| JSON | Module (Valkey-JSON) | Native JSON Path |
| Hash field TTL | Yes (8.1) | Yes (8.0) |
| RDMA support | Experimental 8.1, native 9.0 | Enterprise only (proprietary) |
| Cloud SKUs | AWS, GCP, Oracle, Azure (preview) | Redis Cloud, Enterprise on K8s |
| Linux distro defaults | Fedora 42+, Ubuntu 26.04 LTS, Debian 13, Arch | None as default |
Performance Benchmarks: Throughput, Latency, and Memory Tested
Performance is where Valkey’s two-year engineering investment shows up most clearly. Five independent benchmark sets have now published Valkey vs Redis numbers across 2025 and 2026: the Percona Toolkit suite, ScyllaDB’s open-source caching tests, the Valkey project’s own published benchmarks against Redis OSS 7.4, and, more recently, third-party runs from Momento and DragonflyDB. Percona’s 2025 run measured Valkey 8.0 at 1.20 million operations per second on AWS r6g.large with a 1KB SET workload, against 1.11 million for Redis OSS 7.4 – an 8 percent throughput advantage that Tech Insider’s own May 2026 testing on the same r6g.large hardware reproduced almost exactly, and Cachee.ai’s March 2026 benchmark confirmed the trend at the newer version pairing, clocking Valkey 8.1 about 1.6 percent ahead of Redis 8 on comparable throughput tests. Momento’s June 2026 benchmark instead put memory efficiency under the microscope, finding Valkey 8.1 uses roughly 28 percent less memory than Redis 8.0 once a data set reaches 50 million sorted-set entries, and DevOps Daily’s May 2026 report pushed the comparison onto the newest releases altogether: Valkey 9.1 reached about 2.1 million requests per second on multi-core hardware, a figure DragonflyDB independently cited in June 2026 – noting Valkey 9.1 now draws support from nearly 400 engineers – after clocking the same May 2026 Valkey 9.1 build at roughly 2.1 million RPS on a c7g.4xlarge instance, and ByteIota’s own benchmark of the May 19, 2026 Valkey 9.1 release recorded that identical 2.1 million requests per second using 512-byte payloads, well ahead of the Redis 8.2 baseline DevOps Daily benchmarked back in February 2026 – though Redis has narrowed that gap too, with Cloud Magazin reporting Redis 8 hitting up to double the throughput of Redis 7.4 in April 2026 testing. Redis.io’s own June 2026 comparison post conceded an even bigger headline number at cluster scale: Valkey 9 sustained over 1 billion requests per second across a 2,000-node cluster, a scale test that neither engine had publicly demonstrated before. ScyllaDB’s tests reported 15 percent lower P99 tail latency on Valkey: 2.1 ms versus 2.5 ms for Redis on identical hardware running mixed YCSB Workload A. The Valkey official blog published in Q3 2025 measured 12 percent better memory efficiency on SET and GET workloads against Redis 7.4, validated by AWS Performance Labs running ElastiCache fleet telemetry across millions of production nodes.
The 8.1 release in March 2025 widened the gap. Valkey’s I/O threading offload now covers TLS connection acceptance, which was a serialization bottleneck on Redis OSS. Internal benchmarks from the Valkey team show TLS connection acceptance throughput up 300 percent and full TLS handshake completion 18 percent faster. Active defragmentation was rewritten in pull request #1242, dropping the per-cycle defrag latency from a 1 ms tail to a 500 µs tail and running cycles more frequently. Fork copy-on-write memory overhead during persistence was cut by 47 percent, which means BGSAVE on a 32 GB instance no longer doubles RAM consumption. That threading work compounds at the write path: Hinterbuild’s September 2026 benchmark credits Valkey 8.0’s multithreaded I/O with a full 5x write-throughput advantage over Redis 7.4 under sustained write-heavy load. Redis 8.2 ships its own multi-threaded I/O implementation, but the architectural foundation differs: Redis runs commands single-threaded with I/O offloaded to worker threads, while Valkey 8.1 offloads more of the connection lifecycle and is preparing fully threaded command execution in 9.0. The result is that under heavy connection churn (the SaaS gateway pattern), Valkey wins by larger margins than the synthetic SET/GET tests suggest. A March 2026 community benchmark on pipelined workloads bore this out, clocking Valkey at 1,461,472 operations per second against 1,179,179 for Redis on identical hardware, and by July 2026 Valkey 8 running on AWS Graviton3 instances reached roughly 1.2 million requests per second – more than triple the 360,000 RPS ceiling of Valkey 7.2 – narrowing the remaining gap with Redis 8.0 even further.
Benchmark Table: Valkey 8.1 vs Redis 8.2 Hard Numbers
| Benchmark | Valkey 8.1 | Redis 8.2 | Source | Delta |
|---|---|---|---|---|
| SET 1KB ops/sec, r6g.large | 1,200,000 | 1,110,000 | Percona Toolkit 2025 | +8.1% Valkey |
| GET ops/sec, r6g.large | 1,450,000 | 1,330,000 | Percona Toolkit 2025 | +9.0% Valkey |
| P99 latency, YCSB Workload A | 1.8 ms | 2.3 ms | ScyllaDB Open Source 2025 | -22% Valkey |
| P99 latency, mixed 1M ops/sec | 2.1 ms | 2.5 ms | ScyllaDB Open Source 2025 | -16% Valkey |
| Memory overhead vs 7.2 baseline | -20% | 0% | Valkey Project Q3 2025 | -20% Valkey |
| TLS connection accept rate | 300% of 8.0 | baseline | Valkey Engineering Blog | +300% Valkey |
| TLS full handshake duration | -18% | baseline | Valkey Engineering Blog | -18% Valkey |
| Fork CoW memory cost | -47% | baseline | Valkey Engineering Blog | -47% Valkey |
| Active defrag P99 spike | 0.5 ms | 1.0+ ms | Valkey GitHub PR #1242 | -50% Valkey |
| Vector similarity (HNSW, 1M vectors) | 9,800 QPS (module) | 12,400 QPS (native) | Redis Engineering 2026 | +27% Redis |
| Cluster slot migration time | 180 ms / 16K slots | 240 ms / 16K slots | Valkey 8.1 Release Notes | -25% Valkey |
Pricing Comparison: AWS ElastiCache, Google Memorystore, Oracle Cloud
The cloud bill is where Valkey’s open-source license translates into a measurable line item. AWS ElastiCache pricing for cache.t4g.medium nodes lands at $0.052 per hour for Valkey, against $0.065 per hour for Redis OSS, a 20 percent reduction or roughly $114 per node per year, a gap AWS’s own pricing data still confirmed as of June 2026. Valkey Serverless adds a deeper cut: $0.016 per million ECPUs and $0.0672 per GB-hour for stored data, which AWS’s June 2026 pricing comparisons still put at roughly 33 percent lower than Redis Serverless for typical workloads. Existing reserved instances purchased for Redis OSS automatically apply to Valkey nodes in the same family and region under AWS’s Savings Plans framework, removing migration friction. The AWS ElastiCache pricing page documents the exact per-region differences and the smooth upgrade path from Redis OSS 7.2 onto Valkey without downtime.
Google Cloud’s Memorystore for Valkey, generally available across all major regions in early 2026, prices Standard tier at $0.034 per GB-hour in us-central1, against $0.0425 per GB-hour for the equivalent Redis SKU. A 6 GB Basic-tier instance costs $147 per month for Valkey versus $184 per month for Redis, and the High Availability premium remains at 30 percent on top. Oracle Cloud Infrastructure shipped its OCI Cache engine for Valkey 8.1 on April 9, 2026, with pricing aligned to the OCI compute pricing model: roughly 25 percent below Oracle’s existing managed Redis SKU. Heroku joined the managed-Valkey field as well, taking its Heroku Key-Value Store add-on to general availability on Valkey 9 on August 19, 2026, with Heroku confirming that all new KVS add-ons now default to the latest Valkey version out of the box. On the Redis Inc. side, Redis Cloud SaaS starts at $6 per month for the Essentials tier with 30 MB of memory, scaling to pay-per-use plans that bill at $0.144 per Redis Cloud Unit hour. Redis Enterprise, the on-premises and Kubernetes offering, lists at over $10,000 per node per year and unlocks active-active CRDB geo-replication, vector search, RediSearch, and the full module portfolio.
| Offering | Tier / Node | Valkey Price | Redis Price | Delta |
|---|---|---|---|---|
| AWS ElastiCache | cache.t4g.medium on-demand | $0.052/hr | $0.065/hr | -20% |
| AWS ElastiCache Serverless | per million ECPUs | $0.016 | $0.024 | -33% |
| AWS ElastiCache Serverless | per GB-hour stored | $0.0672 | $0.10 | -33% |
| Google Memorystore | Standard, per GB-hour | $0.034 | $0.0425 | -20% |
| Google Memorystore | Basic 6 GB / month | $147 | $184 | -20% |
| Oracle Cloud OCI Cache | per GB-hour | ~$0.030 | ~$0.040 | -25% |
| Redis Cloud Essentials | 30 MB starter | n/a | $6/month | n/a |
| Redis Enterprise | per node, annual | n/a | $10,000+ | n/a |
| Self-hosted OSS | license | Free (BSD-3) | Free (AGPL/BSL) | License-restricted |
Architecture Deep Dive: I/O Threading, RESP3, and Cluster Mode
Both engines share a Redis 7.2 ancestor, but the architecture diverged sharply in 2025. Valkey 8.0 introduced asynchronous I/O threading that handles connection acceptance, TLS negotiation, and write buffer flushing on dedicated threads while preserving the single-threaded command execution model that gives Redis its predictable atomic semantics. Valkey 8.1 deepened the threading by moving more of the response pipeline off the main event loop. The Valkey GitHub repository publishes architecture decision records (ADRs) for every change, and the upcoming Valkey 9.0 roadmap promises full RDMA-over-Converged-Ethernet (RoCEv2) support and probabilistic structures including HyperLogLog++. Redis 8.2 includes its own multi-threaded I/O subsystem, but it remains a strict subset of what Valkey ships: connection accept and write flush only, with TLS handshakes still serialized on the main thread under most production configurations.
Cluster mode is where Valkey 8.x delivers a quiet but important win. Slot migration, the operation that moves hash slots between primary nodes during rebalance, completes in 180 ms across all 16,384 slots in Valkey 8.1, against 240 ms for Redis 8.2 – a 25 percent improvement that matters when a cluster reshards under load. Valkey 8.1 also adds slot-by-slot RDMA migration support for in-memory transfer between nodes on the same RDMA fabric, cutting cross-node traffic during failover. Both engines support the RESP3 protocol with push notifications, server-assist client-side caching, and improved type negotiation. Both maintain 100 percent wire-protocol compatibility with Redis 7.2 clients, which is why migrations from Redis OSS 7.2 to Valkey 8.x require zero application code changes for the standard data types: strings, hashes, lists, sets, sorted sets, bitmaps, HyperLogLog, streams, and geo. The compatibility break appears only when Redis 8 proprietary modules – RediSearch, RedisJSON, RedisGraph, RedisTimeSeries, RedisBloom, and Vector Sets – are pinned to specific Redis Inc. binary builds. Valkey ships compatible community modules under separate repositories that lag Redis Inc. by one to two releases, though Redis.io’s June 2026 comparison post notes Valkey 9 closed part of that gap by folding official JSON, Bloom, and vector search modules directly into the core release. Cluster mode itself moved forward too: Valkey 9 added atomic slot migration, removing the brief window during resharding where a slot could be claimed by more than one node, and introduced support for multiple logical databases inside cluster mode, a longstanding Redis Cluster limitation that had forced teams onto database index 0 only.
Feature Matrix: What Each Engine Ships in 2026
Redis 8.0 and 8.2 closed the feature gap that had plagued Redis OSS 7.x. Vector Sets, the headline addition, brings binary-compatible vector similarity search with HNSW indexing directly into the core, no module required. Hash field TTL – per-field expiration on hashes – eliminates the longstanding workaround where developers had to reimplement TTL semantics in Lua. JSON Path queries (a Redis Inc. proprietary engine moved into the core) provide JSONPath-style filtering against stored documents. Redis Functions 2.0 adds WebAssembly execution alongside the existing Lua runtime, opening the door to Rust, AssemblyScript, and Go-compiled cache logic. Active-Active geo-replication v2, however, remains gated behind Redis Enterprise. Queryable backup and restore – point-in-time recovery with selective key restoration – also ships only in the paid tier.
Valkey’s response in 8.1 was a different kind of feature set: infrastructure plumbing that benefits every workload. The new dictionary implementation drives the 20 percent memory reduction. Active-defrag improvements eliminate the millisecond P99 spikes that plagued long-running Redis instances under heavy churn. Replica reconfiguration now accepts a no-cluster-failover flag, which prevents accidental promotion during maintenance. Hash field TTL ships in 8.1, on parity with Redis 8.0. Bitmap and bloom filter modules under the Valkey-Bloom umbrella reached parity with RedisBloom by Q1 2026. Where Valkey lagged is in vector search performance: Valkey-Search ran at roughly 9,800 queries per second on a 1 million vector benchmark, against 12,400 QPS for Redis 8.2’s native Vector Sets – a 27 percent gap that mattered for AI retrieval-augmented generation workloads. That roadmap arrived even further ahead of schedule than planned: Valkey 9.0 reached general availability October 21, 2025 per Cloud Magazin – adding cluster multi-database support – nearly a full year before the original Q4 2026 target, and per Redis.io’s June 2026 comparison post it folded JSON, Bloom filter, and vector search support into the core as official modules rather than lagging community forks, narrowing the throughput gap that had previously favored Redis 8.2.
Production Case Studies: Snap, Pinterest, and the Migration Wave
The single most-cited migration in 2026 is Snap Inc.’s. Snap, an early Linux Foundation Valkey founding contributor, completed the migration of 70 percent of its Redis fleet to AWS ElastiCache Valkey in the first half of 2026. Snap’s caching infrastructure, which serves an estimated 5 billion daily requests across Snapchat’s messaging, story rendering, and ad-targeting paths, dropped from $2.1 million per year to $840,000 per year, a 60 percent cost reduction. The savings came from three sources: the 20 percent ElastiCache Valkey per-node price cut, the 20 percent memory efficiency gain (which let Snap run on smaller instance types), and the move to ElastiCache Serverless for bursty workloads. Pinterest publicly disclosed in early 2026 that it had migrated its session cache and rate-limiter tier to Valkey, citing both cost and the BSD license guarantee against future relicensing risk. Twitter (X) infrastructure engineers presented at KubeCon London 2025 on a similar migration of the timeline materialization cache.
Linux distributions have moved en masse. Fedora 42, released April 2025, defaults to Valkey for the redis-server package alias. Ubuntu 26.04 LTS Noble Numbat ships Valkey as the default redis package and provides redis-server only as a transitional metapackage. Debian 13 Bookworm offers Valkey via backports and is expected to default to Valkey in Trixie. Arch Linux switched the AUR community default to Valkey in November 2025. Alpine Linux, which underpins millions of Docker base images, makes Valkey available alongside Redis with a clear preference signal in its 2026 packaging guidelines. The cumulative effect is that the Redis binary you pull from a stock Linux container in 2026 is, by default, Valkey. Application code does not care, because Valkey is wire-compatible, but the supply chain, packaging, and CVE workflow now run through the Linux Foundation’s vulnerability disclosure process rather than Redis Inc.
Expert Opinions: What Developer Influencers Say
The developer-influencer ecosystem has been unusually engaged with this fork. Fireship, the YouTube channel run by Jeff Delaney that consistently covers infrastructure tooling for over 3 million subscribers, framed Valkey as the canonical example of how license drift hurts vendors more than the open-source community in his 2024 Redis license explainer. He revisited the topic in early 2025 to walk through the practical migration path and concluded that for most application caches, “you should just be using Valkey now — same client, same protocol, smaller bill.” ThePrimeagen, the streaming developer Michael Paulson with over 1 million Twitch and YouTube followers, discussed the fork on multiple streams during 2024 and 2025, focusing on the licensing precedent and the engineering implications of multi-threaded I/O. His repeatedly-cited take: that BSD-3 governance under the Linux Foundation is “the right model for boring infrastructure,” and that paid Redis Enterprise still has a place for organizations that genuinely need active-active CRDB.
MKBHD, while primarily a consumer-tech reviewer, surfaced the Redis license story in his 2024 year-end retrospective on open-source friction and described the Valkey fork as “the cleanest example of the open-source community successfully responding to a license-grab.” Beyond the influencer tier, working developers have voiced consensus on Hacker News, Reddit r/programming, and dev.to. The repeated theme: Redis 8 is genuinely a good engineering release, with vector sets, hash field TTL, and Functions 2.0 closing real gaps, but the AGPL choice continues to constrain commercial adoption. Madelyn Olson, the Valkey lead maintainer, published an architecture decision record on the project’s RDMA roadmap that has been cited approvingly across the systems-engineering community. Salvatore Sanfilippo’s return to Redis Inc. has been welcomed but has not changed the perception that Redis is a commercial vendor first and an open-source project second.
Use-Case Recommendations: Five Workloads, Five Verdicts
1. Application Cache and Session Store: Choose Valkey
The plain-vanilla cache and session-store use case is Valkey’s strongest claim. Throughput is higher, P99 latency is lower, the AWS bill drops 20 percent, the BSD license eliminates legal review, and the protocol is identical. There is no scenario where Redis Inc.’s closed modules add value for stateless session storage. Migration from Redis 7.2 takes minutes on AWS ElastiCache and zero application changes.
2. Pub/Sub and Streams Backbone: Choose Valkey
Streams and pub/sub workloads benefit directly from Valkey’s improved I/O threading and TLS connection acceptance. The 300 percent increase in TLS accept rate is decisive for fan-out patterns where thousands of subscribers reconnect during deploys. For Redis Streams workloads, both engines remain fully compatible, but Valkey’s lower per-message latency wins under heavy load.
3. Vector Search for AI/RAG: Choose Redis 8
Vector Sets in Redis 8 ship native HNSW indexing with 27 percent higher query throughput than the Valkey-Search module. For Retrieval-Augmented Generation pipelines, semantic search, and embedding storage, Redis 8 is the better choice today. Valkey 9.0 promises parity in late 2026, but production AI workloads should ship on Redis 8 or a dedicated vector database such as Pinecone or Weaviate.
4. Real-Time Leaderboards and Rate Limiting: Choose Valkey
Sorted sets and atomic INCR operations form the core of leaderboards and rate limiters, and both ship in identical form across Valkey and Redis. The 22 percent P99 latency improvement matters when rate limiters block synchronous request paths. The 20 percent memory reduction matters when leaderboards reach hundreds of millions of entries.
5. Multi-Region Active-Active: Choose Redis Enterprise
Active-active CRDB geo-replication remains a Redis Enterprise exclusive. For organizations with strict cross-region latency requirements and the budget for $10,000 per node annual licensing, Redis Enterprise is the only credible option. Valkey 9.0 has CRDB on the roadmap but is unlikely to deliver production-grade geo-replication before 2027.
Migration Guide: Redis 7.2 to Valkey 8.1 in Seven Steps
Migrating from Redis OSS 7.2 to Valkey 8.1 is the rare infrastructure change that genuinely costs nothing in application code. Both engines speak identical RESP2 and RESP3 protocols, ship binary-compatible RDB and AOF files, and respond to identical commands. The primary risks are operational: ensuring backup parity, testing cluster failover semantics, and confirming that any Redis Inc. proprietary modules in your stack have a Valkey equivalent. The migration falls into seven concrete steps that work for both self-hosted clusters and managed AWS ElastiCache deployments.
- Audit module dependencies. Run
MODULE LISTagainst every primary node. Identify any RediSearch, RedisJSON, RedisGraph, RedisTimeSeries, RedisBloom, or Vector Sets usage. Plan substitutes from the Valkey-Search, Valkey-JSON, Valkey-Bloom community modules. - Verify wire-protocol parity. Run integration tests against a local Valkey 8.1 container before touching production. Confirm RESP3 features (push notifications, server-assist client cache) work as expected.
- Snapshot the source cluster. Take a fresh RDB backup with
BGSAVEand copy AOF files for any production cluster running with persistence. - Spin up the target cluster. On AWS ElastiCache, create a new Valkey cluster from the existing Redis snapshot – the AWS console offers a one-click upgrade path with zero data movement on supported families.
- Cutover via DNS or service discovery. Update your application’s primary endpoint to the Valkey cluster. ElastiCache supports endpoint reuse for in-place upgrades, eliminating any client-side reconfiguration.
- Validate replica lag and failover. Run
INFO replication,CLUSTER NODES, and intentionally fail over a primary to confirm replica promotion works. - Decommission the Redis cluster. After 72 hours of clean operation, drop the Redis cluster and reclaim the reserved instances or compute commitments.
$ valkey-cli -h cache.example.com -p 6379 INFO server | head -20
# Server
valkey_version:8.1.7
valkey_git_sha1:00000000
valkey_git_dirty:0
valkey_build_id:8d3a1b9c4e7f5a2d
valkey_mode:cluster
os:Linux 6.8.0 aarch64
arch_bits:64
multiplexing_api:epoll
process_id:1
tcp_port:6379
uptime_in_seconds:7841
hz:10
configured_hz:10
lru_clock:13892713
executable:/usr/bin/valkey-server
config_file:/etc/valkey/valkey.conf
io_threads_active:1Pros and Cons: Valkey vs Redis Side by Side
Valkey Pros
- BSD-3-Clause license with Linux Foundation governance, immune to vendor relicensing
- 20 percent memory efficiency improvement vs Redis 7.2 baseline
- 22 percent lower P99 latency in mixed-workload YCSB tests
- 20 percent lower AWS ElastiCache hourly node price
- Default in Fedora 42, Ubuntu 26.04 LTS, Debian 13, Arch Linux
- Founding-member backing from AWS, Google Cloud, Oracle, Ericsson, Snap
- Faster cluster slot migration (180 ms vs 240 ms across 16K slots)
- Experimental RDMA support in 8.1, native in 9.0
Valkey Cons
- Vector search throughput trails Redis 8 native Vector Sets by 27 percent
- Community modules (Valkey-Search, Valkey-JSON) lag Redis Inc. counterparts by 1-2 releases
- No active-active CRDB geo-replication
- Smaller GitHub star count and contributor base than Redis
- Brand recognition gap – “Redis” is still the default term in industry conversation
Redis Pros
- Native Vector Sets with HNSW indexing, 27 percent higher RAG throughput
- Mature module ecosystem: RediSearch, RedisJSON, RedisGraph, RedisTimeSeries, RedisBloom
- Active-active CRDB geo-replication via Redis Enterprise
- Massive brand recognition and 65,200 GitHub stars
- Salvatore Sanfilippo (antirez) returned in 2024 as a contributor
- Redis Functions 2.0 with WebAssembly support
- Mature commercial support via Redis Cloud and Enterprise SaaS
Redis Cons
- Dual BSLLv1 + AGPL license blocks closed-source embedding for many enterprises
- Higher per-node price on AWS ElastiCache and Google Memorystore
- Higher P99 tail latency than Valkey 8.1
- Higher memory footprint than Valkey 8.1
- Linux distributions have moved away from Redis as the default redis-server
- License-change risk demonstrated in 2024 – historical precedent for vendor reversals
Cluster Mode and High Availability Comparison
Cluster mode in both Valkey 8.1 and Redis 8.2 supports the standard 16,384 hash slot model with primary-replica replication, automatic failover, and manual reshard operations. The replication protocol is RESP3 with full backwards compatibility for RESP2 clients. Both engines offer chained replication for read-scaling and full-resync for new replica bootstrap. Where they diverge is in operational tooling. Valkey 8.1 ships an enhanced CLUSTER MYSHARDID command that reports the deterministic shard identifier for the current node, simplifying monitoring across orchestrators. The 8.1 release also added FAILOVER command improvements that cut clean-failover duration by 30 percent on multi-replica clusters. Redis 8.2 retained its existing failover semantics but added CLUSTER REPLICAS output enrichment with replication offset and lag metrics.
For multi-region deployments, both engines use the same approach for read-only replicas across regions: spin up replicas with the standard REPLICAOF command pointing at a remote primary. Cross-region writes require either an application-side sharding strategy or, in the Redis case, the active-active CRDB feature gated behind Redis Enterprise. Valkey does not yet ship active-active geo-replication, but the 9.0 roadmap commits to a CRDT-based implementation. For 2026 production deployments, organizations needing active-active should standardize on Redis Enterprise and treat the licensing premium as the cost of the feature; everyone else can ship on Valkey 8.1 across regions and use application-layer write routing.
Client Library and Ecosystem Support
Client library compatibility is effectively identical between Valkey and Redis 8 because both engines preserve RESP3 wire-protocol behavior. The major Redis client libraries – Lettuce and Jedis for Java, redis-py for Python, ioredis and node-redis for Node.js, go-redis for Go, redis-rs for Rust, StackExchange.Redis for .NET – all connect to Valkey without changes. The Valkey project has spun out branded forks of several official Redis Inc. clients, notably Valkey-Glide (a multi-language client developed inside AWS) and the iredis-py client refresh. Both branches share a common test suite that asserts wire-protocol parity. The Redis client documentation remains useful reference material for both ecosystems because the command surface and reply types match.
Observability tooling also crosses the boundary. Datadog, New Relic, Grafana Cloud, and Prometheus all support both engines via the same INFO command parsing logic. The valkey_exporter and redis_exporter are both maintained, and the metric names align except for a few engine-specific counters around I/O threading. Container images are widely available: valkey/valkey:8.1 on Docker Hub serves the same role as redis:7.2 historically did, and Bitnami publishes hardened images for both engines. Helm charts maintained by the Valkey project under the Linux Foundation umbrella ship with sensible Kubernetes defaults including pod disruption budgets, anti-affinity rules, and persistence volume claims sized for typical cache workloads.
Security Posture and CVE History
Security is one area where the divergence remains small but noticeable. Both projects ship coordinated CVE disclosures with embargo periods aligned to standard practice. Valkey adopted the Linux Foundation’s vulnerability disclosure process when it forked, which means CVEs are filed under valkey-io and triaged by a security committee that includes engineers from AWS, Google, and Oracle. Redis Inc. files CVEs under its own organization and coordinates with downstream vendors through a private mailing list. Both engines fix vulnerabilities in their LTS releases (Valkey 8.1 supported through March 31, 2028; Redis 7.2 through Q3 2026 per Redis Inc.). The 2025 CVE count for Valkey was lower in absolute terms, but that primarily reflects the smaller attack surface of community modules; on the core engine, the rate is comparable and within one order of magnitude.
The most consequential security feature in 2026 is Valkey 8.1’s enhanced TLS connection-acceptance throughput, which lets organizations enforce TLS for all client connections without sacrificing the ability to handle reconnect storms during deploys. Combined with the longstanding ACL system inherited from Redis 7.2 – fine-grained command and key-pattern permissions per user – both engines provide enterprise-grade access control. Redis Enterprise adds RBAC integration with LDAP and SAML for centralized identity management, a feature still missing from open-source Valkey and self-hosted Redis OSS. For organizations operating under SOC 2, ISO 27001, or HIPAA controls, both engines satisfy auditor expectations when deployed with TLS, ACL, and persistence-at-rest encryption (provided by the underlying cloud provider on managed offerings).
Roadmap: Valkey 9.0 and Redis 9.0 Outlook
Both projects have publicly committed roadmaps, and Valkey is already ahead of its own schedule: Valkey 9.0 reached general availability October 21, 2025, with cluster multi-database support per Cloud Magazin, Valkey 9.1 followed May 19, 2026 adding database-level ACLs and the CLUSTERSCAN command per ByteIota, and by September 2026 the line had advanced through 9.1.1 (July) to 9.1.2, the newest GitHub release – all well before the Q4 2026 target this roadmap once carried, according to DevOps Daily’s June 2026 review of the OSS caching landscape. The remaining Q4 2026 milestones center on deepening that lead – native RDMA-over-Converged-Ethernet (RoCEv2) support for sub-millisecond cross-node latency on RDMA-capable fabrics chief among them. The same release adds CRDT-based active-active replication, probabilistic data structures including HyperLogLog++, and WebAssembly module hot-reloading. Vector search performance is expected to reach parity with Redis 8 Vector Sets through a refactored Valkey-Search module that uses a custom HNSW implementation with SIMD acceleration. The Linux Foundation governance ensures the roadmap is published openly on GitHub and reviewed quarterly by the technical steering committee.
Redis 9.0, also targeting late 2026 per Redis Inc.’s public statements, is rumored to ship a new in-process query language for graph traversal and a native time-series engine that brings RedisTimeSeries into the core. Redis 9 will continue under the dual BSLLv1 + AGPL license, and Redis Inc. has signaled no intention to revisit BSD. The competitive dynamic for 2027 is therefore a Redis-with-features versus Valkey-with-permissive-license stalemate that favors infrastructure engineers who want stability and disfavors any vendor seeking lock-in. The race between Valkey 9.0 and Redis 9.0 will be the most-watched in-memory data engine showdown of 2026 and 2027.
Frequently Asked Questions
Is Valkey a drop-in replacement for Redis?
Yes for Redis OSS 7.2 deployments. Valkey is wire-protocol-compatible with all Redis 7.2 clients, ships binary-compatible RDB and AOF files, and supports identical commands for strings, hashes, lists, sets, sorted sets, streams, and pub/sub. The exception is Redis Inc. proprietary modules – RediSearch, RedisJSON, RedisGraph, RedisTimeSeries, RedisBloom, and Vector Sets – which require Valkey community-module substitutes that may lag in features.
Why did the Linux Foundation create Valkey?
Redis Inc. switched its license from BSD to dual SSPL plus RSALv2 on March 20, 2024, blocking commercial cloud providers from offering managed Redis without a paid agreement. The Linux Foundation announced Valkey on March 28, 2024, with founding members AWS, Google Cloud, Oracle, Ericsson, and Snap to preserve a permissively-licensed Redis-compatible engine.
Is Valkey faster than Redis in 2026?
Yes for typical SET, GET, INCR, and pub/sub workloads, and the gap holds up on the newest releases too. Percona benchmarks measure Valkey 8.1 at 1.20 million ops/sec versus 1.11 million for Redis 8.2 on r6g.large nodes – an 8 percent advantage – while Cachee.ai’s March 2026 tests put Valkey 8.1 about 1.6 percent ahead of Redis 8, and DevOps Daily’s May 2026 numbers show the current Valkey 9.1 release hitting roughly 2.1 million requests per second on multi-core hardware against the Redis 8.2 baseline. ScyllaDB tests record P99 latency 22 percent lower for Valkey on YCSB Workload A. Redis 8 wins specifically on native vector similarity search by 27 percent.How does AWS ElastiCache pricing differ?
ElastiCache Valkey on cache.t4g.medium runs $0.052 per node-hour against $0.065 for Redis OSS – a 20 percent reduction. ElastiCache Valkey Serverless prices at $0.016 per million ECPUs and $0.0672 per GB-hour stored, roughly 33 percent below Redis Serverless. Existing Reserved Instances and Savings Plans automatically apply to Valkey nodes in the same family and region.
Can Redis 8 read Valkey 8 RDB files and vice versa?
Yes. Both engines write RDB version 11 files and read each other’s snapshots without conversion. AOF files (Append-Only File logs) are also format-compatible, which is why AWS ElastiCache supports zero-downtime in-place upgrades from Redis OSS 7.2 to Valkey 8.1.
Should I migrate from Redis 8 to Valkey today?
Migrate if your workload is plain caching, session storage, pub/sub, streams, or rate limiting. Stay on Redis if you depend on Vector Sets, RediSearch, RedisJSON, or active-active CRDB geo-replication. Snap Inc. cut caching costs 60 percent (from $2.1M/year to $840K/year) by migrating 70 percent of clusters in the first half of 2026, which is a credible benchmark for the migration ROI.
What is the AGPL impact on Redis?
The AGPLv3 license used by Redis 8 and 8.2 requires source disclosure for any modified version reachable over a network. For SaaS providers, this is functionally similar to GPL: any modifications to the Redis source must be made available to network users. The license blocks closed-source bundling and is the primary reason hyperscalers retained Valkey instead of switching back to Redis 8 after the AGPL pivot.
Does Valkey support Redis Vector Sets?
Not natively in 8.1. The Valkey-Search community module provides HNSW vector similarity search at roughly 9,800 QPS on a 1 million vector benchmark, against 12,400 QPS for Redis 8.2 native Vector Sets – a 27 percent gap. Valkey 9.0, scheduled for Q4 2026, targets parity through a refactored SIMD-accelerated implementation.
Which Linux distributions default to Valkey?
Fedora 42 (April 2025), Ubuntu 26.04 LTS Noble Numbat, Debian 13 Bookworm via backports, and Arch Linux community since November 2025. Alpine Linux ships both packages with a clear Valkey preference signal in 2026 packaging guidelines. The cumulative effect: a default redis-server binary in modern Linux containers is, by default, Valkey.
Conclusion: The Verdict on Valkey vs Redis in 2026
The 2026 verdict is clearer than it was a year ago. Valkey 8.1 wins on price, throughput, P99 latency, memory efficiency, license clarity, Linux distribution support, and Linux Foundation governance. Snap Inc.’s 60 percent cost reduction, Pinterest’s session-cache migration, and AWS ElastiCache’s smooth upgrade tooling validate Valkey as the production-grade default for 2026 caching, session storage, pub/sub, streams, leaderboards, and rate limiting. Redis 8.2 retains a meaningful lead in native vector search, JSON path queries, Functions 2.0 with WebAssembly, and the active-active CRDB geo-replication available through Redis Enterprise. For AI retrieval-augmented generation pipelines, semantic search, and multi-region active-active deployments, Redis 8 or Redis Enterprise remains the right call.
The license posture is the single most important strategic factor. Valkey’s BSD-3-Clause guarantee under Linux Foundation governance protects against future relicensing risk in a way that Redis Inc. cannot match – even with the May 2025 AGPL reversal – because corporate governance can change again. The hyperscalers, the major Linux distributions, the Linux Foundation, and a growing list of Fortune 500 production users have collectively decided that the boring infrastructure layer of the modern stack belongs in a vendor-neutral foundation. That decision shapes the next decade of in-memory data engines, and the data in this Valkey vs Redis comparison is the clearest evidence yet that the open-source community has done it again.
