Caching and messaging
Redis has 9 supported release lines and Valkey has 5. Redis 8.0 reaches end of life on Dec 1, 2026. Redis offers RSALv2, SSPL-1.0 or AGPL-3.0; Valkey is open source (BSD-3-Clause).
Last checked against endoflife.date and deps.dev.
Every value links to its source. Where a row doesn’t apply to one of them, the cell says why.
| Compared on |  Redis | Valkey |
|---|---|---|
| Support and releases | ||
| Supported release lines | ||
| Latest release | ||
| Releases in the last 12 months | ||
| Security | ||
| Advisories published in the last 12 months | Not tracked as a package on OSV.dev | Not tracked as a package on OSV.dev |
| OpenSSF Scorecard | No Scorecard published | |
| Licence and hosting | ||
| Licence | RSALv2, SSPL-1.0 or AGPL-3.0 Open source under the AGPL-3.0 option AGPLv3 is OSI-approved, but you must publish your changes if you serve a modified Redis over a network. Versions 7.4–7.x are RSALv2 / SSPLv1 only. | |
| How you run it | Self-hosted, or Redis Cloud, the vendor’s managed service | Self-hosted, or managed by AWS (ElastiCache, MemoryDB) and Google Cloud (Memorystore for Valkey) |
| Adoption | ||
| GitHub stars | ||
| Redis | Valkey |
|---|---|
| Supported release lines | |
| Latest release | |
| Releases in the last 12 months | |
| Redis | Valkey |
|---|---|
| Advisories published in the last 12 months | |
Not tracked as a package on OSV.dev | Not tracked as a package on OSV.dev |
| OpenSSF Scorecard | |
No Scorecard published | |
| Redis | Valkey |
|---|---|
| Licence | |
RSALv2, SSPL-1.0 or AGPL-3.0 Open source under the AGPL-3.0 option AGPLv3 is OSI-approved, but you must publish your changes if you serve a modified Redis over a network. Versions 7.4–7.x are RSALv2 / SSPLv1 only. | |
| How you run it | |
Self-hosted, or Redis Cloud, the vendor’s managed service | Self-hosted, or managed by AWS (ElastiCache, MemoryDB) and Google Cloud (Memorystore for Valkey) |
| Redis | Valkey |
|---|---|
| GitHub stars | |
Read across for what matters to you. Each answer comes from the data above or the project’s licence and hosting options.
| If you need | Redis | Valkey |
|---|---|---|
| An open-source licence | Yes: Under the AGPL-3.0 option | Yes: BSD-3-Clause |
| Someone else runs it for you | Yes: From Redis Cloud | Yes: From AWS and Google Cloud |
| You can run it on your own servers | Yes: Yes, it’s software you install | Yes: Yes, it’s software you install |
| A long support window | 8.2 is supported until Sep 1, 2030 | 9.1 is supported until May 19, 2031 |
| Redis | Valkey |
|---|---|
| An open-source licence | |
Yes: Under the AGPL-3.0 option | Yes: BSD-3-Clause |
| Someone else runs it for you | |
Yes: From Redis Cloud | Yes: From AWS and Google Cloud |
| You can run it on your own servers | |
Yes: Yes, it’s software you install | Yes: Yes, it’s software you install |
| A long support window | |
8.2 is supported until Sep 1, 2030 | 9.1 is supported until May 19, 2031 |
In-memory data store with pub/sub, persistence, and Lua scripting
Open-source Redis fork maintained by the Linux Foundation
From StackPrism’s curated notes. Pricing isn’t covered here: it changes often, so check each vendor’s pricing page.
Valkey is the Linux Foundation fork of Redis, created in 2024 when Redis moved away from the BSD licence. It keeps the Redis protocol and commands, so the comparison usually comes down to licence and to which one your cloud or hosting provider runs.
Release lines and end-of-life dates come from endoflife.date, release counts from deps.dev’s publish dates, and advisories from OSV.dev, counted once per flaw even when it’s listed under several ids, and checked against CISA’s list of vulnerabilities known to be exploited. Status and incident history come from each vendor’s public status feed; licences from each project’s licence file or the vendor’s licensing page, linked in the table.
The data refreshes every few hours and the time it was checked is shown above. There’s no pricing and no overall winner: which one fits depends on your constraints. To see how the versions you actually run hold up, check your repo.
Paste a public GitHub repo and see what’s vulnerable, end of life or deprecated in it today. Free, no sign-up.