Redis Licensing Overview

A three-column chart displaying Redis licenses and associated products

About the Redis Source Available License 2.0 (RSALv2)

RSALv2 is a permissive, non-copyleft license created by Redis Ltd., allowing users the right to “use, copy, distribute, make available, and prepare derivative works of the software” and has only two primary limitations. You may not:

Note that RSALv2 has not been approved by the OSI, and we do not refer to it as an Open Source license.

About SSPL

SSPL is a source-available license created by MongoDB, who set out to craft a license that embodied the ideals of open source, allowing free and unrestricted use, modification, and redistribution, with the simple requirement that if you provide the product as a service to others, you must also publicly release any modifications as well as the source code of your management layers under SSPL.

SSPL is based on GPLv3, and is considered a copyleft license. This means that if you use the source code and create derivative works, those derivative works must also be licensed under SSPL and released publicly. For more information, MongoDB has a good FAQ.

Note that SSPL has not been approved by the OSI, and we do not refer to it as an Open Source license.

About our dual license

Starting on November 15th, 2022, our default binary distributions of Redis Stack and Redis modules will be under RSALv2. When using the source code, users can apply either RSALv2 or SSPLv1. As shown in the table below, RSALv1 is applied to older versions of Redis Stack and Redis modules, including fixes and patches.

ModuleRSALv1Binary distribution: RSALv2
Source code: RSALv2 or SSPLv1
Redis Stack<= 6.2.4>= 6.2.6
RediSearch<= 2.4>= 2.6
RedisJSON<= 2.2>= 2.4
RedisTimeSeries<=1.6>= 1.8
RedisBloom<= 2.2>=2.4
RedisGears<=1.2>= 2.0


Can you summarize the changes from RSALv1 and explain your motivations?

It’s been almost four years since we introduced the Redis Source Available License 1.0 (RSALv1) for our Redis modules. During this time, we’ve held an open dialogue with the Redis community about our approach to licensing. Most users like our license’s permissive, non-copyleft spirit. But we’ve also seen a couple of challenges: first, it’s hard for many users to understand the practical implications of the text of the RSAL license; second, we have not standardized on any widely-used source-available license.

RSALv2 maintains the permissive, non-copyleft spirit of RSALv1 while making its permissions and limitations more simple and clear.

And, for those users who require a more standardized license, we hope that the added option to use our software under the SSPL opens Redis Stack and our Redis modules to an even wider audience.

Why are you offering a dual license strategy?

We believe the permissive approach of RSALv2 and the standard wording we use to define its limitations solves many of the challenges raised by our community, but we are also aware that, like any newly created license, it will take time for some users (and their legal teams) to digest it and therefore we’ve added an option to use SSPL. Created by MongoDB and adopted by Elastic and many others, SSPL is becoming the de facto standard for source available licenses and is being used by millions of developers worldwide.

This dual-license approach will allow users to choose between a permissive but less known license, RSALv2, or a more standardized but copyleft license, such as SSPL.

Does this change affect the license of open source Redis?

No. Open source Redis remains licensed under the 3-Clause-BSD license. We continue to support open source Redis by sponsoring the core team, maintaining the roadmap, adding new features, and fixing bugs in the same way we always have.

I’m a Redis Stack or a Redis modules user; how does this license change affect me?

Nothing changes for you. Our default distribution continues to be free and open under the Redis Source Available License, as it has been for nearly the last four years. With the Redis Source Available License 2.0, we have standardized the license terms and kept the license very permissive. If you build applications on top of Redis modules, nothing changes for you.

Our client libraries continue to be licensed under the open-source MIT license.

I contribute to one of the Redis modules; how does this affect me?

First, a big thank you! As long as you have signed the Contributor License Agreement, you can continue contributing to the Redis modules as you always have.

I’m a customer or partner; how does this affect me?

This change will not affect customers and partners using our Redis Enterprise Cloud or Software products.

I built a SaaS application using Redis Stack or one of the Redis modules as the backend; how does this affect me?

This source code license change should not affect you – you can use our default distribution or develop applications on top of it for free under the RSALv2. This source-available license does not contain any copyleft provisions, and the default functionality is free of charge.

For further clarification, please reach us at

How does this affect me if I’m offering Redis Stack or Redis modules as a service for internal-only use?

This should not affect you.

We do not consider providing Redis modules as a service internally or to subsidiary companies as making them available to a third party. For further clarification, please reach us at

Can I provide commercial support for Redis Stack and your Redis modules?

Absolutely! The idea behind the Redis Source Available License is to help grow the ecosystem around Redis Stack and Redis modules. Commercial support by a third party is more than welcome in this spirit.

Can I modify the Redis modules I use?

Yes. In this sense, RSALv2 is similar to many permissive open-source licenses. You can modify the software, integrate the variant into your application, and distribute and sell your application as long as your application is compliant with the limitations defined under the RSALv2 license.