PROVIDER Β· Linux Foundation hosted Redis fork

Valkey

Valkey is the BSD-licensed fork started by Redis core contributors and cloud vendors, fully compatible with Redis 7.2 commands and protocol under neutral Linux Foundation governance as an open replacement avoiding Redis licensing changes.

Backend & Database United States 2026.11.15
Backend & Database United States Linux Foundation hosted Redis fork
4.2pts

Pros

4 items
The BSD three-clause licence imposes no extra limits on commercial use or redistribution
Protocol and command compatibility with Redis 7.2 reuses clients and tools directly
Neutral Linux Foundation governance with contributions from multiple cloud vendors
Official stable releases and container images simplify replacement deployments

Cons

4 items
New features such as vector search and JSON land later than in official Redis
Fewer hosted and support options than Redis with regional coverage still filling in
The brand and docs are young while Chinese tutorials mostly reference Redis
Fast community growth, yet the long-term roadmap still needs watching

Product Information

valkey
Category Backend & Database
Company Valkey
Service Region United States
Official Website https://valkey.io/
Recommendation Score 4.2 pts
Published 2026-11-15

Detailed Notes

Overview

Valkey was launched in March 2024 by Redis core contributors with several cloud vendors including AWS, Google, and Oracle, became a Linux Foundation project in September 2024, and forked from Redis 7.2.4 under the BSD three-clause licence in response to licence changes that worried open source users.

For Backend & Database work the value is direct, since protocol compatibility plus a permissive licence let existing clients and tools connect unchanged, distributions and clouds can package it freely, and teams already fluent in Redis swap images and connection strings while avoiding licensing risk.

Real concerns are ecosystem inertia, because after Redis returned to AGPLv3 in 2025 differences show in how quickly new features such as vector search, JSON, and modules land, hosted and commercial support options for Valkey remain fewer, and the long-term roadmap needs tracking.

Core Strengths

  • The BSD three-clause licence imposes no extra limits on commercial use or redistribution
  • Protocol and command compatibility with Redis 7.2 reuses clients and tools directly
  • Neutral Linux Foundation governance with contributions from multiple cloud vendors
  • Official stable releases and container images simplify replacement deployments

Product Ecosystem

Core data structures

Strings, hashes, lists, sets, sorted sets, bitmaps, HyperLogLog, and streams behave identically to Redis commands.

High availability and clustering

Replication, Sentinel, and cluster sharding work with unchanged clients such as redis-py or ioredis.

Distribution and ecosystem

Major Linux distributions and clouds package it, and third-party monitoring and admin tools speak the Redis protocol.

Drawbacks

  • New features such as vector search and JSON land later than in official Redis
  • Fewer hosted and support options than Redis with regional coverage still filling in
  • The brand and docs are young while Chinese tutorials mostly reference Redis
  • Fast community growth, yet the long-term roadmap still needs watching

Use Cases

  • Licence-clean Redis replacement (β˜…β˜…β˜…β˜…β˜…) - BSD terms with no licensing friction
  • Session caches and leaderboards (β˜…β˜…β˜…β˜…β˜…) - Full command compatibility
  • Managed cache underpinnings on clouds (β˜…β˜…β˜…β˜…) - Already offered by major clouds
  • Workloads needing Redis modules (β˜…β˜…β˜…) - Check feature parity

Pricing

Plan Price Scope
Valkey open source $0 BSD licensed, self-managed
Cloud managed Valkey Monthly per instance size Backup and automatic failover
Third-party support Annual per node SLAs and hot fixes

The community edition is free with cost tracking memory, since cache sizing is the budget and maxmemory plus eviction policy must be set to avoid unbounded growth, while managed instances from one to two gigabytes bill in the tens of dollars monthly.

FAQ

  • How does Valkey differ from Redis? Same lineage with identical commands and protocol, differing mainly in new features and governance, since Valkey is foundation-hosted while Redis is vendor-led.

  • Does migration need code changes? Usually only images or endpoints change, though Redis-specific module features should be checked for equivalent support in Valkey.

  • Is it production ready as a cache? Yes with replication plus Sentinel or cluster mode and no licensing risk, and a month on non-critical paths before switching core traffic is prudent.

Visit Valkey Website β†’ https://valkey.io/
Visit Website β†—