Search

Suggested keywords:
  • Java
  • Docker
  • Git
  • React
  • NextJs
  • Spring boot
  • Laravel

Redis Adopts Dual Source Available Licensing

  • Share this:
post-title

Redis has recently announced that starting from Redis 7.4, they are planning to use Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1) as dual source available license. Customers have choice of using either of the license. Previously Redis was distributing its source under BSD-3-Clause license and now they no longer will support BSD.

 

Why this change?

Redis following MongoDB and Elastic has done changes to their licensing to protect its products from cloud providers. Cloud providers are using the open source version of the product and make their money but they are not contributing anything back to the community and also paying price for the software being used. Though open source software is considered to be free, it is not actually free. Redis is sponsoring for the development for the community.

Redis code will be available in dual license Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). There will be no change in the client modules. It will be under MIT.

 

Redis Source Available License (RSALv2)

RSALv2 is a permissive, non-copyleft license created by Redis Ltd. It allows to use, copy, modify and distribute. It does not allows to commercialize the software or provide it to others as a managed service.

 

Server Side Public License (SSPL)

SSPL is a source-available license created by MongoDB. It is based on GPLv3, and is considered a copyleft license. It allows to use, copy, modify and distribute but if you provide the product as a service, you must also publicly release any modifications as well as the source code of your management layers under SSPL.

 

More and more companies going to adopt similar model. They will make the source available for public but will not allow cloud providers and other commercial vendors to mis use its products.

Editorial Team

About author
This article is published by our editorial team.