Redis 7.0 end of life
Redis 7.0 reached end of life on 29 July 2024, when Redis 7.4 was released. The final release on the line was 7.0.15. Redis 7.0 was also the last line released under the permissive BSD licence before Redis moved to the dual RSALv2 and SSPL licence in March 2024, which makes the upgrade decision a licensing question as well as a technical one.
- End of life
- 29 July 2024
- Released
- Apr 2022
- Final release
- 7.0.15
- Successor
- Redis 7.2 / 7.4, or Valkey 8
Date published by Redis release lifecycle. We do not publish a lifecycle date we cannot source.
What actually stops on 29 July 2024
- Community patch releases on the 7.0 line. 7.0.15 was the last.
- Security fixes for the server, including the Lua scripting and module interfaces where several past CVEs have landed.
- Nothing about the licence changes retroactively: code released under BSD stays BSD. The licence change applies to versions released after it.
What actually breaks in the upgrade
The upgrade is easy; the licence decision is the real one
Redis point upgrades are usually straightforward — that is precisely why fewer estates get stuck on old Redis than on old Spring or RabbitMQ. The genuine decision in 2026 is not how to upgrade, it is what to upgrade to: a current Redis release under RSALv2 and SSPL, or Valkey, the Linux Foundation fork of Redis 7.2.4 that remains BSD-licensed.
The licence only bites for a narrow set of use cases
RSALv2 and SSPL restrict offering the software as a commercial managed service to third parties. Internal enterprise use is unaffected. Teams reflexively migrating to Valkey on licence grounds should check whether the restriction applies to them at all; for most internal deployments it does not.
Persistence and memory behaviour is where upgrades actually go wrong
Where Redis upgrades do fail, it is rarely the version bump. It is RDB and AOF behaviour under memory pressure during the transition, particularly fork-based persistence on instances sized close to the host's available memory. Check the memory headroom before the upgrade window, not during it.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to Redis 7.2 or 7.4 | Supported to December 2029. Now under RSALv2 and SSPL. | Hours to days | Engineering time | Simplest path. Confirm the licence terms suit your use case; for internal use they almost always do. |
| Migrate to Valkey | The Linux Foundation fork of Redis 7.2.4, BSD-licensed, wire-compatible at the fork point. | Days | Engineering time | Right if you offer Redis as a service to third parties, or if BSD licensing is a procurement requirement. |
| Extended support on 7.0 | Backported CVE fixes to the 7.0 line under its original BSD licence. | Days | Subscription | Narrow use case, since upgrading Redis is usually easy. Real when an appliance or ISV product pins the version. |
| Stay unpatched | No upstream fixes since July 2024. | None | Zero now | Hard to justify given how cheap the upgrade normally is. |
What OSSeva does for Redis 7.0
OSSeva patches this line
OSSeva backports CVE fixes to Redis 6.x and 7.0 under their original BSD licence, and supports Valkey. We will usually tell you to upgrade instead: Redis is the one technology on this list where the upgrade is genuinely cheap, and selling you support you do not need would be the wrong advice.
Redis extended supportWhat your auditor will say
Requirement 6.3.3 where Redis holds or caches cardholder data — including session data, which is frequently overlooked in scoping.
CC7.1. Redis is often outside the formal inventory because it is 'just a cache', which is itself the finding.
Redis 7.0: common questions
When did Redis 7.0 reach end of life?
29 July 2024, when Redis 7.4 was released. The final release on the line was 7.0.15.
Is Redis 7.2 or 7.4 end of life?
No. Both are supported to December 2029 under Redis's published lifecycle. It is the 7.0 and earlier lines that are end of life.
Does the Redis licence change affect my old version?
No. Code released under the BSD licence stays BSD-licensed; the RSALv2 and SSPL dual licence applies to versions released after the March 2024 change. Your existing deployment's terms do not change retroactively.
Should I move from Redis to Valkey?
Only if the licence actually affects you. RSALv2 and SSPL restrict offering the software as a commercial managed service to third parties; internal enterprise use is unaffected. For most internal deployments there is no licensing reason to move.
Can I get security patches for Redis 7.0?
Yes, from a third-party provider. OSSeva backports CVE fixes to Redis 6.x and 7.0 under their original BSD licence — though for most estates upgrading is cheaper and we will say so.
What goes wrong in a Redis upgrade?
Rarely the version change itself. The failures cluster around RDB and AOF persistence behaviour under memory pressure during the transition, particularly fork-based persistence on instances sized close to the host's memory limit.
Still running Redis 7.0?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.