Valkey is a high-performance key/value data structure server: an in-memory store that speaks the Redis wire protocol, persists to disk, replicates across machines and can be clustered for horizontal scale. It is the community fork of the last BSD-licensed Redis release (7.2.4), created in 2024 when Redis Ltd moved its own server to a source-available licence, and it is now governed by the Linux Foundation under the BSD-3-Clause licence.
Because the protocol and command set are unchanged, Valkey is a drop-in replacement in practice: existing Redis client libraries connect as they always did, legacy tooling such as redis-cli and Helm charts keep working against it, and a migration usually means re-pointing a connection string rather than rewriting an application. What changed is the licence and the governance model – development happens in the open on GitHub, and the project ships regular releases on several maintained branches at once (9.1.3, 9.0.7, 8.1.11, 8.0.12 and 7.2.15 were all published in the same week of October 2026).
It runs as a standalone daemon or as a cluster, and it is used for the whole range of key/value workloads: caching, session storage, rate limiting, leaderboards, queues and job metadata, pub/sub messaging, and – for many teams – as a primary database where the working set fits in memory.
EVAL and EVALSHA, Functions, and a module API for compiled extensions that add new commands and data types. In the 9.1 line Lua itself is a module, so a deployment that does not need scripting can leave the engine out entirely.db= in ACL SETUSER; TLS; slow log; keyspace notifications; INFO metrics and JSON-format server logs for log pipelines.HGETDEL, MSETEX and CLUSTERSCAN.valkey/valkey name on Docker Hub, a generally available Valkey Helm chart (1.0.0, with Sentinel failover, TLS, ACL authentication and Prometheus metrics) and a separate Valkey Operator for managing clusters on Kubernetes.Valkey is a single C binary plus a configuration file, so the fastest route is the official container: docker run --name valkey -p 6379:6379 valkey/valkey:9.1 gives a working server on the default port, and the image documentation covers persistence volumes and configuration mounts. On a host, building from source is a plain make after installing a C compiler and, for TLS, the OpenSSL development headers; optional flags add TLS (BUILD_TLS=yes), systemd support (USE_SYSTEMD=yes), Zstandard compression (BUILD_ZSTD=yes) or RDMA (BUILD_RDMA=yes).
Configuration lives in valkey.conf: set maxmemory and an eviction policy for a cache deployment, appendonly yes and the RDB save points for durability, a requirepass or ACL users for access control, and the cluster-enabled option when running in cluster mode. Client libraries are the Redis ones – Redis-py, Jedis, Lettuce, go-redis, node-redis, Predis and their peers all work unchanged over RESP, which is why adopting Valkey rarely touches application code.
Operationally it is a piece of infrastructure that wants memory headroom and a monitoring hook: the INFO sections give hit ratios, evictions, connected clients and replication offsets, and the project publishes a Prometheus-friendly metrics story through its Helm chart and Operator.
If the workload is caching only, Memcached’s simplicity is a legitimate choice; if the workload needs data structures, persistence, pub/sub and replication under an OSI licence, Valkey and Redict are the two direct successors to the old Redis OSS line.