Redis 8.0 End of Life: December 1, 2026 (Redis Open Source)

By Scott Bissett  ·  Published: October 6, 2026  ·  Reference guide  ·  Dates read at Redis's Open Source version management page on October 6, 2026.

Redis 8.0 reaches end of life (EOL) on December 1, 2026. That is the EOL date in the supported versions table on Redis's Redis Open Source version management page, which classes 8.0 as a Standard release. Redis 8.0 shipped on May 2, 2025 as the first release of the 8.x series and the release that folded Redis Stack into Redis Open Source. Its successor, Redis 8.2, shipped on August 4, 2025; since then 8.0 has been in the phase Redis describes for Standard releases, security updates and critical bug fixes. This page covers Redis Open Source only. Redis Software (formerly Redis Enterprise) has its own lifecycle table with different version numbers and dates.

The dates, in one table

Redis publishes the end of life date as a single day in its supported versions table, with no separate extended or paid phase for Redis Open Source. The same table marks the release type of every version, and the type decides how long a version lives.

Standard and Extended releases: Redis's two-tier model

Redis's version management page describes two release types within a major version. Standard releases are the first release in a major series (8.0) and the intermediate minor releases (8.4, 8.6 and so on). In Redis's words, "These releases receive security updates and critical bug fixes for 6 months after the following minor version is released." Extended releases are the second minor release in a major series (8.2) and the final minor release in the series, and "receive security updates and critical bug fixes for 5 years after their release date."

Redis 8.0 is the first release of the 8.x series, so it is Standard. The end of life date Redis publishes for it, December 1, 2026, is the date in the table and runs past the six-month minimum the policy promises. Redis 8.2, the second minor, is Extended and carries a five-year date, September 1, 2030. The intermediate minors after it, 8.4 through 8.10, are Standard and show "TBD" in Redis's table because each one's date depends on when the minor after it ships.

Which servers these dates cover

Any Redis Open Source server reporting a version that starts with 8.0, whether installed from source, from a distribution package, from the official Docker image or from a cloud marketplace image. The INFO server command prints redis_version; that number, not the client library version or the Redis Insight version, decides which row of the table applies. Redis 8.0 was the release in which the former Redis Stack modules (JSON, search and query, time series, probabilistic data structures) became part of Redis Open Source, so a server running those capabilities on 8.0 is covered by this page too.

The dates do not cover Redis Software or Redis Cloud. Redis Software has a separate product lifecycle page with its own cluster version numbers, and Redis Cloud handles database versions on the customer's behalf.

Redis 8.0 next to its neighbours

Since 8.0, Redis has shipped a new minor about every three months, so the 8.x series already has six minors. Only one of them, 8.2, is an Extended release with a published five-year date. The table below shows 8.0, the two minors that followed it, and the newest release Redis lists, 8.10. Every version is on our Redis lifecycle page.

Release dates are the General Availability dates of the x.y.0 tags on Redis's GitHub releases page. Release types and end of life dates are from Redis's version management page.

What to do with the time you have

1. Inventory by server version. Run INFO server on every instance and list the ones whose redis_version starts with 8.0. Check managed images and sidecar containers as well as the servers you installed by hand.
2. Pick the target by runway. Redis 8.2 is the Extended release of the series and is supported until September 1, 2030. Redis's own note on the version management page is that it strongly recommends the latest available version, which is 8.10 at the time of writing; 8.10 is a Standard release and has no end of life date set yet, so expect to move again when the minor after it has been out for six months.
3. Upgrade minor by minor if you have modules in use. The former Redis Stack capabilities became core in 8.0, and later minors added features to them. Read the release notes for each minor between your version and the target, in particular any change to the search and query or JSON command sets.
4. Keep patching until you move. Apply any 8.0.x patch release Redis publishes on GitHub before you move; the end of life date is the day those stop, not the day the risk starts.
5. Check the rest of the stack in the same pass. Our EOL Checker and API answer the operating system, the language runtime and the client library next to the Redis server.

Frequently Asked Questions

Related

• Redis — the live lifecycle page with every version's dates and EOL Risk Score
• How we verify our dates — the rules every number on this site is held to