Valkey

What it is

Valkey is an in-memory key-value datastore — a drop-in replacement for Redis, forked from the last BSD-licensed Redis codebase (7.2.4) after Redis Inc. moved to SSPL/RSALv2 in March 2024. It does what Redis did: caching, pub/sub, session storage, leaderboards, rate limiting, queues, and general low-latency data structures (strings, hashes, sets, sorted sets, streams). If your app talks the Redis protocol (RESP), it talks to Valkey without code changes.

Who builds it and why

Valkey is a Linux Foundation project, spun up within days of Redis's license change by the maintainers and companies who depended on Redis staying open. AWS, Google Cloud, Oracle, Ericsson, Alibaba Cloud, and Percona are among the founding backers, and several of the original Redis core maintainers moved over to work on it. The motivation is straightforward: these companies run Redis at massive scale in managed services (ElastiCache, Memorystore, etc.) and needed a permissively licensed fork they control instead of being at the mercy of a vendor's licensing decisions. 1011 contributors is a large number for a datastore this young — reflects both the fork's popularity and the fact that it inherited Redis's long contributor history in spirit, if not in commit log.

Production readiness signal

26,396 GitHub stars and commits as recent as July 2026 indicate active, well-funded development — this isn't a fork that got announced and abandoned. Latest release 9.1.0 shows real version progression past the initial 7.2.4 base, including new features (dual-channel replication, improved cluster scaling) rather than just security patches. The project runs under Linux Foundation governance with a real TSC and RFC process, not a single-vendor BDFL model. CNCF maturity level is not publicly available (Valkey is a Linux Foundation project, not currently a CNCF sandbox/incubating/graduated project — don't confuse the two foundations). Given that AWS and Google are already shipping Valkey in their managed cache offerings, production readiness at scale is not really in question — the bigger question is long-term feature parity/divergence from Redis, which is worth watching release-over-release.

Who should use this

• Teams currently on Redis OSS who want to stay on a permissive license without vendor lock-in risk.
• Anyone building on AWS ElastiCache or Google Memorystore, since both have adopted Valkey as their go-forward engine.
• New projects that need a caching/session layer and don't want to deal with Redis's post-2024 licensing terms for commercial/managed use cases.
• Organizations that want multi-vendor governance (not one company's roadmap) for a piece of core infrastructure.

Who should NOT use this

• Teams needing Redis Enterprise-only features (RedisGears, active-active CRDTs via Redis Enterprise, certain modules) that haven't been reimplemented in Valkey — check module compatibility before migrating.
• Anyone wanting a durable primary datastore: this is a cache/fast-data-structure store, not a substitute for a transactional database — don't reach for it if you need ACID guarantees or complex querying.
• Small teams with no ops capacity who'd rather pay for a fully managed proprietary cache (e.g., Redis Cloud) and let someone else own upgrades, patching, and failover — self-hosting Valkey still requires real operational investment.
• Shops already deep into Redis Stack modules (RedisJSON, RediSearch) with no plans to migrate — verify module support maturity in Valkey first.

Alternatives

• Redis (post-license-change) — same lineage, richer enterprise module ecosystem, but SSPL/RSALv2 terms restrict certain commercial/managed use.
• Memcached — simpler, pure cache-only, no data structures or persistence — pick this if you truly just need a flat key-value cache with less operational surface.
• KeyDB — another Redis-compatible fork with a multi-threading focus, smaller community and less foundation backing than Valkey.

Pricing

Fully open source, BSD-3-Clause license. No paid tier, no license fees, no feature gating. Cost is entirely your own hosting/ops, or whatever a cloud provider charges for a managed Valkey-based service (e.g., ElastiCache, Memorystore).