Valkey 7.2.5-rc1 was announced on April 16, 2024, but it was not the final release: Valkey’s official blog announced stable Valkey 7.2.5 on the same day. The project has moved on since then; as of October 4, 2026, its homepage listed 9.1.2 as the newest 9.x release. The announcement matters chiefly as an early milestone in the community’s response to Redis’s licensing change, and as a statement of compatibility goals—not as a current version recommendation.
What was announced on April 16, 2024?
The Linux Foundation announced Valkey 7.2.5-rc1 as a release candidate intended for compatibility testing. It said development would continue from Redis OSS 7.2.4 under the BSD 3-clause license. In a separate post that same day, Valkey announced that stable 7.2.5 was generally available. Kyle Davis, author of the project’s release post and identified there as Percona’s general manager for the Valkey ecosystem, wrote: “I’m pleased to announce that you can start using the first generally available, stable Valkey release today.” Linux Foundation announcement · Valkey 7.2.5 stable-release post
That chronology resolves the apparent contradiction in the headline-era coverage: the release-candidate announcement and stable release were separate announcements on the same date. The candidate label describes the Linux Foundation announcement, not the lasting status of the 7.2.5 software.
What is Valkey?
Valkey is an open-source, BSD-licensed key/value datastore. The project describes it as suitable for caching and message queues, and also capable of serving as a primary database. Its documented capabilities include standalone and clustered deployments, replication and high availability, multiple data structures, Lua scripting and modules, and client libraries for languages including Python, Java, Go, Node.js, PHP, C# and Ruby. These are project descriptions; workload suitability depends on an application’s requirements and operational design. Valkey project homepage
#1 Best Overall
Why did the community form?
The Linux Foundation presented Valkey as a response to Redis Inc.’s licensing change. Valkey was announced in March 2024; the project’s retrospective gives its creation date as March 28, 2024. The launch announcement framed the effort around continued access to an open-source Redis-compatible datastore and open governance, with development under the BSD 3-clause license. Those statements describe the project’s launch-era positioning; they should not be read as a current account of the licensing terms for every Redis product. Linux Foundation, April 16, 2024
How compatible is Valkey with Redis?
The claims in the 2024 announcements are specifically about Redis OSS 7.2.4. The Linux Foundation described 7.2.5-rc1 as an initial compatibility release for existing Redis users, based on that version and without backwards-incompatible API changes. Valkey’s stable-release post said 7.2.5 retained Redis 7.2.4’s protocol, API, return values and data file formats. These are project statements about a particular baseline, not proof that every Redis version, product, module, configuration or application will work unchanged.
For an actual migration, validate the application and deployment rather than relying on the release announcement alone. Check the Redis version and features in use, client and framework support, configuration differences, persistence and data handling, and behavior under application-specific tests. Spring Data Valkey is one documented framework integration; its existence does not establish that all Spring applications—or applications built on other frameworks—can switch without changes. Valkey 7.2.5 release details · Spring Data Valkey announcement
What does “growing support” establish?
The Linux Foundation’s April 2024 announcement named Aiven, Alibaba Cloud, Chainguard, Heroku, Huawei, Percona and Verizon as new participants, and AWS, Google Cloud, Oracle, Ericsson and Snap as existing supporters. It also said that “hundreds more community members have voiced their intent to support Valkey.” That is an attributed statement of intent; it does not count active contributors or completed contributions.
In a 2025 retrospective, Valkey reported that corporate participants grew from 22 to 47 during its first year. This is a project-reported ecosystem figure, not an independent measurement of deployments, market share, production performance or user satisfaction. Valkey’s 2025 retrospective
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Which Valkey version is current?
As checked on October 4, 2026, Valkey’s homepage listed these releases, each dated September 1, 2026:
Rank #4
| Branch | Release listed | Release date |
|---|---|---|
| 9.x | 9.1.2 | September 1, 2026 |
| 8.x | 8.1.10 | September 1, 2026 |
| 7.x | 7.2.14 | September 1, 2026 |
Release listings can change; check the official Valkey homepage before choosing a version. The 2024 7.2.5 announcement is historical context, not guidance to install that release today.
How should an organization evaluate Valkey?
Start with the workload and the amount of infrastructure your team wants to operate. The project lists multiple managed-service options, while self-managed deployments put more responsibility for availability, backups, upgrades and incident response on the operating team. Compare supported Valkey versions, regions, data-residency requirements, availability and backup features, and total cost; offerings and prices can change. Valkey project homepage · Aiven Valkey pricing
For support, distinguish community documentation from commercial support or consulting, and assess response requirements and deployment environment. Percona identifies Valkey/Redis services; that listing is not evidence that one provider is universally preferable. Percona services
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
