Relicensed

Redis license history

Database·Last verified 2026-11-06·Confidence: High

Changed from BSD-3-Clause to RSALv2 / SSPL-1.0 starting with 7.4.0 on 2024-03-20.

Changed from RSALv2 / SSPL-1.0 to RSALv2 / SSPL-1.0 / AGPL-3.0-only starting with 8.0.0 on 2025-05-01.

Versions before 7.4.0 remain under BSD-3-Clause.

Self-hosting
Allowed
Offering as a managed service (SaaS)
Allowed under AGPL terms (source disclosure required)
Commercial impact: Restricted

This is our summary of the license text and may contain errors or omissions. Check the original sources before you decide. Disclaimer and corrections → · Spot an error? Report it

What changed

Redis moved from BSD-3-Clause to a dual RSALv2/SSPL-1.0 license starting with 7.4.0, announced on 2024-03-20. Starting with 8.0.0, AGPL-3.0-only was added as a third option, announced on 2025-05-01. Releases before 7.4.0 remain under BSD-3-Clause.

License timeline

2025-05-01

From 8.0.0

RSALv2Source-available or SSPL-1.0Source-available→RSALv2Source-available or SSPL-1.0Source-available or AGPL-3.0-onlyCopyleft
Restricted
Self-hosting: Allowed
Offering as a managed service (SaaS): Allowed under AGPL terms (source disclosure required)

AGPL-3.0-only was added as an option. Under that option, offering a modified Redis over a network requires making the modified source available.

Sources

Verified 2026-11-06·Confidence: High
2024-03-20

From 7.4.0

BSD-3-ClausePermissive→RSALv2Source-available or SSPL-1.0Source-available
Restricted
Self-hosting: Allowed
Offering as a managed service (SaaS): Restricted

Redis Ltd. moved Redis to a dual source-available license. Offering Redis as a competing managed service requires a commercial agreement. The Linux Foundation launched the Valkey fork from 7.2.4.

Sources

Verified 2026-11-06·Confidence: High

Originally released under BSD-3-Clause

For reference only. Not legal advice. How a license applies depends on your use; the license text and your counsel decide. Methodology and disclaimer →

Forks and alternatives

Valkey

Fork

BSD-3-Clause

KeyDB

Alternative

BSD-3-Clause

Get alerts for Redis

We email you if Redis changes its license again.

Check the box above to show the Google sign-in button.

More Database projects

Dragonfly

BUSL-1.1 → Dragonfly-Enterprise-Source-Available-License · 2.1.0

Restricted

ScyllaDB

AGPL-3.0-only → ScyllaDB-Source-Available-License · 2025.1

Restricted

Elasticsearch

SSPL-1.0 / Elastic-2.0 → SSPL-1.0 / Elastic-2.0 / AGPL-3.0-only · 8.16.0

Restricted

CockroachDB

BUSL-1.1 → CockroachDB-Software-License · 24.3.0

Restricted

ArangoDB

Apache-2.0 → BUSL-1.1 · 3.12.0

Restricted

Couchbase

Apache-2.0 → BUSL-1.1 · 7.0.0

Restricted

Related guides

Source-Available vs Open Source: The Difference

What separates source-available licenses such as SSPL-1.0, BUSL-1.1, RSALv2 and Elastic-2.0 from OSI-approved open source licenses.

Commercial Use Under BUSL, SSPL, RSALv2 and ELv2

What BUSL-1.1, SSPL-1.0, RSALv2 and Elastic License 2.0 restrict for self-hosting, managed services and embedding in products.

How to Stay on the Last Version Before a License Change

What the version boundary means, how to pin a release before a license change, and what to check about security patches.