Comparison · Database
Redis vs Valkey: developer guide
Redis relicensed to a source-available SSPL / RSAL combination. Valkey forked off the last BSD-licensed commit, backed by AWS, Google Cloud, and Oracle. For developers, the question now is which one to track — and the answer depends on how you deploy.
See also: Redis Goes Source-Available, Sparks Fork Discussions
The licence in one paragraph
Redis 7.4+ ships under SSPL (Server Side Public License) + RSAL (Redis Source Available License). You can read the code, modify it, deploy it internally. You can't offer it as a managed service without open-sourcing your entire stack.
Valkey stays on the BSD-3-Clause license that Redis used through version 7.2. No restrictions on commercial offerings.
Compatibility today
| Capability | Redis 7.4 | Valkey 8.0 |
|---|---|---|
| RESP protocol | Yes | Yes |
| Streams, Pub/Sub, Cluster | Yes | Yes |
| Lua scripting | Yes | Yes |
| Client library compatibility | Yes | Yes (no client changes needed) |
| RedisJSON / RediSearch / RedisGraph | Yes | No (Redis-only modules) |
| License | SSPL + RSAL | BSD-3-Clause |
| AWS Elasticache fork | Compatible | Tracks Valkey going forward |
| Google MemoryStore | Compatible | Tracks Valkey going forward |
Decision tree
You self-host on EC2 / a VPS / your own metal: Both work. Track whichever you find easier to upgrade. License doesn't affect you because you're not redistributing.
You sell Redis as a service: Valkey. Redis's SSPL bars you, and the BSD license guarantees you no future relicense surprises.
You use AWS Elasticache, GCP MemoryStore, or Azure Cache: Watch your provider's roadmap. Each is transitioning to Valkey on the back end. Customer-facing differences should be minimal in 2026 — both speak RESP — but module support (RedisJSON / RediSearch) will diverge.
You depend on Redis modules (RedisJSON, RediSearch, RedisGraph, RedisBloom): Stay on Redis. The modules are authored by Redis Ltd and aren't available under Valkey. Be aware that managed-Redis pricing may shift as hyperscalers move traffic to Valkey.
What changes in 18 months
- Cluster behaviour — Valkey will likely optimize for hyperscaler operations (faster scaling, smoother re-sharding). Redis Ltd will likely double down on Enterprise features (RBAC, audit, search).
- Module ecosystem — Valkey may ship a parallel JSON or full-text module under BSD. Until then, anything beyond core key-value semantics is Redis-only.
- Client libraries — Major clients (redis-py, ioredis, lettuce, redis-rb) will support both via the same connection code. Expect optional module-feature detection.
- Migration — RDB and AOF formats remain cross-compatible. A Redis → Valkey switch is a configuration change, not a data migration.
Bottom line
For most application developers in 2026, the license change is a non-event at the code level — both forks speak the same protocol and your client library doesn't care.
The real decision is at the platform-strategy level: if you distribute, package, or resell, Valkey removes a class of legal risk. If you rely on Redis modules, you stay on Redis. Everyone else should track Valkey for the next year and revisit if something material happens.