Redis 8 AGPL vs Valkey BSD — what do I need to change?
Teams standardizing on an in-memory store need a current licensing decision card on whether Redis’s return to AGPL in 2025 changes the prior move to Valkey under BSD terms for commercial or self-hosted deployments.
Blockers
- breaking_change_in: package/redis-community-edition-7-4-plus → package/valkey
- requires_version: package/valkey → package/redis-oss-7-2
- Lock-in via vendor/linux-foundation
Who this is for
- cost-sensitive
- enterprise
- compliance
- low-ops
Candidates
Standardize on Redis Open Source 8 under AGPL-aware governance
As of 2026-03-19, Redis Open Source 8 and later are offered under a tri-license of RSALv2, SSPLv1, or AGPLv3, with AGPL added on 2025-05-01. Redis’s official licensing page says Redis 7.2.x and earlier remain BSD-3-Clause, while Redis Community Edition 7.4.x to 7.8.x remain RSALv2 or SSPLv1. Redis 8.6 is the current GA line, and the official release index lists Redis 8.6.1 tarballs dated 2026-02-23. Redis also states that most community users are not impacted when using Redis 8 as-is, but modified versions offered over a network under AGPL trigger source-availability obligations.
When to choose
Use this when you specifically want upstream Redis 8 features and are prepared to operate under AGPL obligations for self-hosted use or to review alternative Redis license options with counsel. The decisive factor is needing Redis 8’s upstream feature set more than needing a permissive license for redistribution or managed-service packaging.
Tradeoffs
You get the upstream Redis 8 codebase, including integrated Redis Stack technologies in core and the current Redis release cadence. The cost is licensing complexity: Redis 8 is open source again, but it did not return to BSD, and AGPL is materially stricter for modified network services.
Cautions
Do not treat Redis 8 as a simple return to the pre-2024 BSD model. If your team embeds the server in a commercial product, modifies the engine, or operates a hosted service, involve legal review. For Redis Cloud or Redis Software commercial pricing, check official docs.
Standardize on Valkey for BSD-licensed commercial and hosted use
As of 2026-03-19, Valkey’s official site describes it as an open source BSD datastore backed by the Linux Foundation. The official download page lists Valkey 9.0.3 as the current 9.x release, with 8.1.6 and 7.2.12 as latest supported past releases, all dated 2026-02-24. Valkey’s migration documentation states that Valkey 7.2.4 forked Redis 7.2.4 and that Valkey is compatible with Redis OSS 7.2 and earlier. That keeps Valkey the cleaner default for teams that want permissive BSD terms for commercial distribution, internal platforms, or self-hosted managed offerings.
When to choose
Use this when licensing simplicity is the primary decision driver for enterprise, compliance, or cost-sensitive teams, especially if you may redistribute the server or expose it as a service. The decisive factor is avoiding AGPL, SSPL, and RSAL review overhead while staying in the Redis-compatible ecosystem.
Tradeoffs
You get BSD licensing, vendor-neutral governance, and a straightforward story for commercial packaging or hosted deployments. The tradeoff is that you are standardizing on the forked ecosystem rather than upstream Redis, so some Redis-branded tooling, docs, or features may not map one-to-one.
Cautions
Valkey’s migration docs explicitly say Redis Community Edition 7.4 and later are not open source and that their data files are not compatible with Valkey. If you are already on Redis CE 7.4+ or Redis 8, plan a migration method rather than assuming an in-place file swap. Managed-service pricing is provider-specific, so check official provider docs.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Redis 8 AGPL vs Valkey BSD — what do I need to change?"