Key facts
- Redis 7.2 and earlier are BSD-licensed. Redis 7.4 moved to RSALv2 or SSPLv1; Redis 8 added AGPLv3 as a third option.
- Valkey forked from Redis 7.2.4 under the Linux Foundation and is BSD-licensed.
- AWS lists ElastiCache for Valkey at 33% lower cost (serverless) and 20% lower (node-based) than other engines.
- Azure Cache for Redis Enterprise tiers retire Mar 31, 2027; Basic, Standard and Premium retire Sep 30, 2028.
What changed
Until version 7.2, Redis was released under the permissive BSD licence. In March 2024 Redis Ltd. moved new releases, starting with 7.4, to a choice of the Redis Source Available License (RSALv2) or the Server Side Public License (SSPLv1). Neither is approved by the Open Source Initiative. Within days, contributors from several companies launched Valkey as a Linux Foundation project, forked from Redis 7.2.4 and kept under BSD.
With Redis 8, Redis added the AGPLv3 as a third licence option. AGPLv3 is OSI-approved, but it carries network copyleft obligations: if you modify Redis and offer it as a network service, you are generally expected to share those modifications.
For most companies running Redis inside their own applications, none of these licences stops you using it. The questions start when you embed it, modify it, or offer it as a service.
Why teams are moving to Valkey anyway
- Licence certainty. Legal teams that prohibit AGPL, or dislike source-available terms, get a BSD option with foundation governance.
- Cost. AWS states ElastiCache for Valkey costs 33% less for serverless and 20% less for node-based clusters than the other supported engines.
- Compatibility. Valkey keeps the Redis wire protocol and commands, so most clients connect without code changes.
Azure Cache for Redis is retiring
Separately from licensing, Microsoft is retiring Azure Cache for Redis in favour of Azure Managed Redis. Enterprise and Enterprise Flash tiers retire on March 31, 2027. Basic, Standard and Premium retire on September 30, 2028, with remaining instances disabled from October 1, 2028. Azure Managed Redis is clustered by default, so client configuration needs checking before the move.
How to migrate safely
- Inventory every cluster, its version, modules and the clients that use it.
- Check data compatibility. Valkey reads data files from Redis OSS 7.2 and earlier. Data from Redis 7.4 or later needs a logical migration.
- Check modules. Redis 8 folds search, JSON and time series into core; Valkey provides some of these as separate modules. Confirm what you use.
- Choose the cut-over method: in-place engine upgrade where the provider supports it, replication, or dual writes.
- Load-test the new cluster and rehearse the switch, including rollback.
This is an engineering guide, not legal advice. Have counsel confirm how a licence applies to your architecture.
Sources
- Redis: What is Valkey? (licensing section)
- AWS Database Blog: How Flickr modernized caching with ElastiCache for Valkey
- Microsoft Learn: Azure Cache for Redis retirement FAQ
Checked on November 15, 2026. Vendors can change dates and terms, so confirm against the source before you rely on them.


