Redis vs Valkey: what actually changed after the fork
Two and a half years after the license fork, Redis and Valkey are both alive and diverging: clients and protocol carry over for older open source workloads, while licenses, governance, features and migration effort now differ. The history, the compatibility rules including the Redis CE 7.4 data-file carve-out and the Stack-module exception, and the decision factors - from Redis's and Valkey's own documentation, read 21 November 2026.
In March 2024, Redis split in two over a license change. Two and a half years later both projects are alive, current and no longer identical: Redis's open source line is at version 8.10.3 (its latest GitHub release, 26 October 2026) under three license options, Valkey is at 9.2.0 under the BSD license it kept. If you run a cache, session store or rate limiter, the choice between them is real - and it turns on license, governance and compatibility, not on rewriting your code. Everything below comes from Redis's and Valkey's own documentation and announcements, the Linux Foundation's launch press release, and the two clouds' service pages, all read 21 November 2026.
What actually happened
Redis was created in 2009 by Salvatore Sanfilippo and stayed under the open source BSD license for fifteen years. In March 2024 Redis Ltd. moved future releases to a dual source-available model (RSALv2 and SSPLv1); Redis's own later account confirms the March 2024 decision in the company's words. Eight days after the change, on 28 March 2024, the Linux Foundation announced Valkey: a continuation of the last BSD release, Redis 7.2.4, launched by six active contributors from Alibaba, Amazon, Ericsson, Google, Huawei and Tencent, with backing from AWS, Google Cloud, Oracle, Ericsson and Snap. Two more turns complete the picture: in November 2024 Sanfilippo rejoined Redis Ltd., and on 1 May 2025 Redis announced it was adding the OSI-approved AGPLv3 as a third license option starting with Redis 8, folding the former Redis Stack technologies (JSON, time series, probabilistic types, the query engine) into core Redis under that license.
The licenses today
Redis's legal page now lists three options for Redis 8 and later, and its own text labels two of them plainly: RSALv2 "is not an open source license" (its key restriction bars using the software in database products, a clause aimed at competing database services), and SSPLv1 "is not an open source license" either (it requires releasing your service's management-layer source if you offer the software as a service). The third, AGPLv3, is OSI-approved open source, with copyleft that can require publishing complete source and modifications when the software is distributed or used over a network. Valkey is simpler: BSD 3-clause, one license, under Linux Foundation governance. Valkey's site says the foundation backing ensures it "will remain open source forever" - that is the project's own statement of intent, not a guarantee anyone can independently make; the checkable facts are the BSD license text and the foundation governance that exist today.
Compatibility: what the fork did not break - and what it does not cover
Valkey's migration documentation is specific about what carries over. Valkey 7.2.4 is a fork of Redis OSS 7.2.4, and migrating from any open source Redis version from 2.x through 7.2.x "is effectively an upgrade": same RESP wire protocol (RESP2 and RESP3), existing Redis client libraries connect without code changes, redis-cli works against Valkey servers and valkey-cli against Redis OSS, Redis-style configuration files are accepted, and RDB and AOF persistence files are compatible. That compatibility is scoped to Redis OSS core, and three caveats from the same documentation keep it honest. First, application code built on the old Redis Stack modules' commands (JSON, search, time series) is not covered; custom modules written against the RedisModule_ API do load in Valkey, which also offers its own ValkeyModule_ API for new modules, but that is module loading, not a promise that every module command behaves identically. Second, data files produced by Redis Community Edition 7.4 and later are not compatible with Valkey, so a file-level move only works from the open source 7.2 line or earlier. Third, for detection: Valkey reports redis_version:7.2.4 in its INFO output for backward compatibility, so monitoring that parses that field needs the server_name or valkey_version fields instead. Even in the fully compatible case, the documented move is a planned operation - Valkey joins the existing server or cluster as a replica, catches up over replication, gets promoted, and the old nodes are retired - with verification steps at each stage. Protocol and client compatibility does not make that zero-effort: test against your own data, modules and traffic before switching production.
Where the two have diverged
Since the fork each project has shipped its own roadmap. Valkey has released six supported lines (7.2 through 9.2; 9.2.0 landed 19 November 2026 with additions such as the Path Hash data type) and presents itself as the vendor-neutral continuation of Redis OSS. Redis 8 integrated the Stack modules into the core server and the open source line is now at 8.10.3 - so capabilities like JSON documents and the query engine ship in core Redis rather than as separate modules, while Valkey builds its own equivalents on its own schedule. On performance, both projects publish their own numbers and third-party benchmarks exist; treat any single benchmark as one test of one setup, not a verdict.
Which one to run
Tie the choice to your situation rather than to a default winner. Running open source Redis 7.2 or earlier on core workloads and want BSD licensing and foundation governance: Valkey's own docs describe that move as effectively an upgrade, with clients and configs carried over - still a planned replication-based operation to test, and any code using Stack-module commands needs its own plan. Running Redis CE 7.4 or later, or Redis 8: your data files are not Valkey-compatible per Valkey's docs, so a switch is a migration project, not an upgrade. Need the integrated JSON, time series or query-engine capabilities in core: Redis 8 ships them under AGPLv3, so weigh the copyleft obligations for how you distribute or serve the software. Want a managed service: AWS ElastiCache offers a Valkey-compatible cache and Google Cloud offers Memorystore for Valkey, while Redis Ltd. sells its own commercial Redis Cloud and Enterprise tiers. And if you are simply deciding whether your app needs a cache at all, that is a different question - our Redis caching guide covers the failure designs to settle first.
Sources, all read 21 November 2026: Valkey documentation, History (fork timeline, six launching contributors, Redis Ltd. trademark as reason for the rename); Valkey documentation, Migration from Redis to Valkey (compatibility scope, the Redis CE 7.4 carve-out, INFO field behavior); valkey.io (BSD license, version 9.2.0 of 19 November 2026, supported lines); Redis, Licenses (the three options with Redis's own not-open-source labels for RSALv2 and SSPLv1); Redis blog, AGPLv3 announcement (published 1 May 2025, updated 13 November 2026; March 2024 decision and antirez's return in Redis's words); github.com/redis/redis releases (Redis Open Source 8.10.3, 26 October 2026); Linux Foundation press release, 28 March 2024 (launch, backers); AWS ElastiCache and Google Cloud Memorystore for Valkey (managed availability).
Frequently asked questions
Is Valkey just a renamed Redis?
No. Valkey is a fork of open source Redis 7.2.4 created in March 2024 by former Redis maintainers and contributors under the Linux Foundation, with its own roadmap - it is now at version 9.2 while Redis's open source line is at 8.10.3. It kept the BSD license and the name changed because Redis Ltd. owns the Redis trademark.
Will my existing Redis client work with Valkey?
Per Valkey's documentation: yes. Valkey speaks the same RESP protocol (RESP2 and RESP3), existing Redis client libraries connect without code changes, and redis-cli works against Valkey servers. This compatibility covers Redis OSS 7.2 and earlier semantics.
Can I move from Redis 8 to Valkey by copying my data files?
No. Valkey's migration guide states that data files produced by Redis Community Edition 7.4 and later are not compatible with Valkey. Moving from those versions is a migration project by another method, not a file-level upgrade.
Is Redis still open source?
Partly, by your choice of license. Redis's own legal page offers three options for Redis 8 and later: AGPLv3, which is OSI-approved open source, plus RSALv2 and SSPLv1, which Redis's own text describes as not open source licenses. Before Redis 8, the post-fork releases were source-available only.
Is Valkey guaranteed to stay open source?
That is the project's stated intent: its site says Linux Foundation backing ensures it "will remain open source forever." Treat that as the project's own commitment rather than an independent guarantee; the verifiable facts are today's BSD 3-clause license and foundation governance.
Do the big clouds offer Valkey as a managed service?
Yes. AWS ElastiCache lists Valkey-compatible caching alongside Redis OSS, and Google Cloud offers Memorystore for Valkey with documented supported versions. Redis Ltd. separately sells Redis Cloud and Enterprise tiers.