Redis 8 went AGPL — can I still use Redis?
Teams choosing Redis distributions or managed offerings need to reassess legal and operational risk after Redis 8 added AGPL alongside RSAL and SSPL, especially where Valkey or cloud-managed alternatives are already under consideration.
Depends on your distribution. AGPL copyleft applies to Redis 8+. Valkey (BSD) is the safe fork.
Blockers
- Redis 8+ tri-licensed under RSALv2, SSPLv1, and AGPLv3; AGPL is OSI-approved but copyleft — network use of modified versions triggers source-availability obligations; not equivalent to Redis 7.2 BSD-3
- Redis 8.6 includes RedisJSON, RedisBloom, RedisTimeSeries as unified package without separate modules
- replaces: vendor/valkey → vendor/redis
- Snapshot copy, replication, or key-by-key migration from Redis OSS 7.2-compatible versions — Redis CE 7.4 and later data files are not compatible with Valkey; cannot do direct in-place jump from CE 7.4+ — Pain: medium
- ElastiCache for Valkey: zero-downtime upgrade from ElastiCache for Redis OSS; supports Valkey 8.2, 8.1, 8.0, 7.2.6 — Version cadence follows AWS not upstream; 100 MB minimum metered data storage floor on Serverless; serverless pricing 33% lower than other engines — Pain: low
- AGPL copyleft: network use of modified Redis triggers source-availability obligations; RSALv2 forbids managed-service commercialization; SSPLv1 requires public release of management layers
- package/redis-8.6 incompatible with package/valkey-9.0.3: Redis CE 7.4 and later data files are NOT compatible with Valkey; cannot do direct in-place migration from Redis 7.4+/8.x to Valkey
Who this is for
- enterprise
- compliance
- low-ops
- cost-sensitive
- small-team
- high-scale
- real-time
Source-linked facts
Facts updated: 2026-03-15
Published: 2026-03-27
Try with PocketLantern
$ npm install -g pocketlantern # Then ask: $ pocketlantern "Redis 8 AGPL vs RSAL/SSPL Adoption After the 2025 License Change"
Missing something? Request coverage