Database

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

Valkey 9.1, 9.0, 8.1, 8.0 and 7.2 are supported; the latest release is 9.1.2.

Last checked against endoflife.date and deps.dev.

Latest release
9.1.2
GitHub stars
27.4k
Licence
BSD-3-Clause

Supported versions

Valkey release lines and security support dates from endoflife.date
VersionSecurity supportLatestReleased
Valkey 9.1Supported: Until 9.1.2
Valkey 9.0Supported: Until 9.0.6
Valkey 8.1Supported: Until 8.1.10
Valkey 8.0Supported: Until 8.0.11
Valkey 7.2Supported: Until 7.2.14

Maintenance and supply chain

deps.dev has no OpenSSF Scorecard for this repository.

Source 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

  • Redis

    In-memory data store with pub/sub, persistence, and Lua scripting

    Strengths

    • Rich data structures (lists, sets, sorted sets, hashes)
    • Built-in pub/sub messaging

    Trade-offs

    • Single-threaded (can bottleneck on CPU)
    • Memory-intensive for large datasets
    Redis health today
  • 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

Check Valkey in your own stack

This page checks Valkey 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.