Database

Redis: supported versions and end-of-life dates today

Redis 8.10, 8.2, 8.0, 7.4, 7.2 and 1 older line are supported (8.0 until Dec 1, 2026); 8.8, 8.6 and 8.4 have no announced end-of-life date but no active support; 7.0 reached end of life on Jul 29, 2024; the latest release is 8.10.2.

Last checked against endoflife.date and deps.dev.

Latest release
8.10.2
GitHub stars
76.8k
OpenSSF Scorecard
6.9 / 10

Supported versions

Redis release lines and security support dates from endoflife.date
VersionSecurity supportLatestReleased
Redis 8.10Supported: No end date announced8.10.2
Redis 8.8No end-of-life date announced: No date announced; active support ended8.8.3
Redis 8.6No end-of-life date announced: No date announced; active support ended8.6.7
Redis 8.4No end-of-life date announced: No date announced; active support ended8.4.7
Redis 8.2Supported: Until 8.2.10
Redis 8.0Ending soon: Until 8.0.6
Redis 7.4Supported: Until 7.4.11
Redis 7.2Supported: Until 7.2.16
Redis 6.2Ending soon: Until 6.2.24
Redis 7.0Ended: Ended 7.0.15
Redis 6.0Ended: Ended 6.0.20
Redis 5.0Ended: Ended 5.0.14

Licence

  • Redis 7.4 is source-available (RSALv2 / SSPLv1)

    Redis moved from BSD-3 to RSALv2 / SSPLv1 in 2024 (7.4). Fine for internal use; offering Redis itself as a service is restricted. Redis 8 added AGPLv3 as a third option.

    Licence sourceOpen alternative: Valkey (BSD-3)

  • Redis is tri-licensed (RSALv2, SSPLv1 or AGPLv3) since Redis 8

    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.

    Licence sourceOpen alternative: Valkey (BSD-3)

Maintenance and supply chain

OpenSSF Scorecard 6.9 / 10 (scored )

The Scorecard rates the repository’s security practices, not known vulnerabilities. Recent activity: 30 commits and 9 issue updates found in the last 90 days.

Weakest checks

  • Over-privileged CI tokens (Token-Permissions 0/10)
  • Unsigned releases (Signed-Releases 0/10)
  • Unpinned build dependencies (Pinned-Dependencies 0/10)

Full ScorecardSource repository

Production checklist

Redis / Valkey production checklist: 5 checks before launch

  • Must do: Require authentication (ACL users) and keep it off the public internet
  • Should do: Use TLS between the app and Redis
  • Should do: Set maxmemory and an eviction policy that fits your use
See all 5 checks with how to verify each

Alternatives

  • Memcached

    Simple, high-performance distributed memory caching system

    Strengths

    • Extremely fast for simple key-value operations
    • Multi-threaded architecture scales well

    Trade-offs

    • Only supports simple key-value storage
    • No persistence - data lost on restart
    Memcached health today
  • AWS ElastiCache

    Managed Redis or Memcached service on AWS

    Strengths

    • Fully managed (automatic backups, patching, failover)
    • Supports both Redis and Memcached engines

    Trade-offs

    • AWS vendor lock-in
    • Less control over configuration
    AWS ElastiCache health today
  • Hazelcast

    Distributed in-memory data grid with caching capabilities

    Strengths

    • Distributed architecture (no single point of failure)
    • Supports complex data structures and queries

    Trade-offs

    • More complex to set up than Redis/Memcached
    • Higher resource usage
  • Valkey

    Open-source Redis fork maintained by the Linux Foundation

    Strengths

    • Fully compatible with Redis protocol and commands
    • Community-driven (no license restrictions)

    Trade-offs

    • Relatively new project (forked in 2024)
    • Smaller ecosystem than Redis
    Valkey health today

Check Redis in your own stack

This page checks Redis in general. Your repo pins specific versions: the free dependency check reads your manifests and lists what to fix first. Prism Agent runs the same live checks on your whole stack and turns them into a plan your coding agent can build.