Redis Source Available License 2.0
Also known as RSAL 2.0, RSALv2, Redis Source Available License 2.0 Agreement.
- Commercial use
- allowed
- Share alike
- required
- Attribution
- required (keep the copyright and license notices)
Write this as a license text (needs an account) DALICC reads the model above and writes what it permits, requires and prohibits in plain English. Without an account, the Text download above writes the model out from the vocabulary.
Permissions
-
Commercial use from the text Using the work to generate income, directly or indirectly, for example by selling it or by using it in advertising.
-
Derivative works from the text Distributing an adaptation of the work and making it available to the public.
-
Derive from the text Creating a new work from the work, such as a translation, adaptation or arrangement of it or of a part of it.
Duties
- Modification notice from the text Marking a changed work as changed, saying how it differs from the original and keeping earlier notices of change.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Share alike from the text Adaptations have to be licensed under the same license or one the license names as compatible.
-
Duties
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Share alike from the text Adaptations have to be licensed under the same license or one the license names as compatible.
-
Modified works from the text Distributing a modified version of the work that does not amount to a new, derivative work.
-
Modify from the text Altering the work, for example by updating it, without creating a new work; an alteration that creates a new work is Derive.
Duties
- Modification notice from the text Marking a changed work as changed, saying how it differs from the original and keeping earlier notices of change.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Share alike from the text Adaptations have to be licensed under the same license or one the license names as compatible.
-
Patent grant from the text Granting a license under the patent claims that a contributor holds and that the contribution necessarily infringes.
-
Reproduce from the text The text says: "The Licensor grants You a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the Software, in each case subject to the limitations and conditions below." Making copies of the work in any form.
Prohibitions
-
Change license from the text Not permitted: Change license. Replacing the license of the work, or of an adaptation, with another license, or changing its terms.
-
Promote from the text Not permitted: Promote. Using the name or trademarks of the licensor or of contributors to endorse or promote a product.
-
Sublicense from the text Not permitted: Sublicense. Granting a third party rights in the work under a license of the licensee's own, rather than passing on the original license.
License-wide duties
This license states no duties that apply to the work as a whole.
What applies by default
The statements above are the library's reading of this license: each is marked with the sentence it rests on, or as a library convention where the text is not explicit. The statements below are the ones the DALICC reasoner supplies for acts the license says nothing about, from the default rules of the dependency graph it reasons with. Each one names the legal source it rests on. None of it is in the record.
No default rule of that graph reaches this license: it speaks about every act the rules are about.
Further terms
These are the things the license says about itself beyond the acts it permits, forbids and requires: when it ends, how long there is to put a breach right, which law governs it, and so on. A term that comes from the DALICC vocabulary links to its definition.
- Patent license ends if you sue
- Yes. Not a ban on suing: a patent claim over the work ends the patent license, or the whole license, as the text provides.
- Cure period
- 30 days
- Field of use restriction
- any use other than making the functionality of the software available to third parties as a service or in a distributed form that gives them that functionality
- Governing law
- the law of the State of California, the State of Israel or England and Wales, according to where the licensee is located
- Terminates on breach
- Yes
Clauses
Warranty disclaimer
As far as the law allows, the Software comes as is, without any warranty or condition, and the Licensor will not be liable to You for any damages arising out of this Agreement or the Use or nature of the Software, under any kind of legal claim.
Additional clauses
This Agreement sets forth the terms and conditions on which the Licensor makes available the Software. By installing, downloading, accessing, Using, or distributing any of the Software, You agree to all of the terms and conditions of this Agreement.
Info
- Target asset types
- Software
- Region / jurisdiction
- Worldwide
- Validity
- Perpetual
- Source
- https://github.com/redis/redis/blob/unstable/LICENSE.txt
- Legal code
- https://raw.githubusercontent.com/redis/redis/unstable/LICENSE.txt
- This description is published under
- Creative Commons Attribution 4.0 International
- Publisher
- Redis Ltd.
- SPDX identifier
RSALv2(provisional, the record declares none)- Version
- 2.0
- DALICC identifier
RSALv2
This record is published under CC BY 4.0. Credit it as: DALICC License Library, DALICC - Verein zur Förderung der Rechtssicherheit in der Datenbewirtschaftung, https://dalicc.net, CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). The license it describes belongs to its publisher.
Use this license
Everything below is generated from this record. Replace the example address with the address of your own work.
JSON sidecar
{
"license-uri": "https://dalicc.net/licenselibrary/RSALv2",
"license-title": "Redis Source Available License 2.0",
"spdx-id": null,
"asset": null,
"generated-by": "DALICC"
}
RDF, Turtle
@prefix cc: <http://creativecommons.org/ns#> .
<https://example.org/my-work>
cc:license <https://dalicc.net/licenselibrary/RSALv2> .
RDF, JSON-LD
{
"@context": {
"cc": "http://creativecommons.org/ns#"
},
"@id": "https://example.org/my-work",
"cc:license": {
"@id": "https://dalicc.net/licenselibrary/RSALv2"
}
}
This license carries no attribution duty, so no credit line is offered here.
Badge
Markdown
[](https://dalicc.net/license-library/RSALv2)
HTML
<a href="https://dalicc.net/license-library/RSALv2"><img src="https://dalicc.net/license-library/RSALv2/badge.svg" alt="License: Redis Source Available License 2.0"></a>
Review
- Written from the license text by
- Giray Havur
- Written on
- 2026-09-22
- Second review
- not yet done
- Record changed since this review
- yes (version 2, 2026-09-24)
- Findings
- 13 recorded, 9 applied to the record, 0 proposed
The record models the Redis Source Available License 2.0. It is built on the same skeleton as the Elastic License 2.0 and grants the same acts, with one limitation that goes further: you may not make the functionality available to third parties as a service, and you may not distribute the software in a way that gives them that functionality either. It is not an open source licence. The licence also picks a governing law that depends on where the licensee is.
13 findings
-
info Rubric 1
spdx:licenseIdappliedFile name, record identifier and IRI local name agree. The triple is left out: the SPDX list does not carry this licence and no identifier is invented. cc:legalcode points at the file the publisher ships and dct:source at the same file's page. dct:publisher is Redis Ltd., which the definition of Licensor names.
-
minor Rubric 1
cc:legalcodeappliedThe file the text comes from holds three licences, this one and then the Server Side Public License and the GNU Affero General Public License, because the project offers a choice between them. Only the first part is modelled here; the other two have their own records.
-
info Rubric 2
odrl:targetapplieddcmitype:Software only. The text defines the Software as components designed to work with the publisher's database.
-
major Rubric 3
odrl:permissionapplied'The Licensor grants You a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the Software.' That gives odrl:reproduce, odrl:distribute, odrl:modify, odrl:derive, cc:DerivativeWorks and dalicc:ModifiedWorks, and the Patents section gives dalicc:patentGrant. cc:CommercialUse is permitted, because the limitation is about offering the software itself to third parties and not about earning money with it.
-
minor Rubric 3
odrl:distributeappliedodrl:distribute stays permitted although the limitation also bars distributing 'in a manner that makes the functionality of the Software available to third parties'. The grant names distribution expressly, and the limitation qualifies the manner rather than withdrawing the act, so the act is permitted and the limitation is quoted and named in dalicc:fieldOfUseRestriction. A reader has to weigh the two.
-
major Rubric 4
odrl:prohibitionapplieddalicc:sublicense for 'non-sublicensable'. dalicc:ChangeLicense for 'The terms and conditions of this Agreement do not imply any Licenses other than those expressly granted in this Agreement', read with the Notices section. dalicc:promote, because no trademark rights are granted and 'Any use of the Licensor's Trademarks is subject to applicable law'. dalicc:patentRetaliationTermination for the written-claim sentence of the Patents section.
-
major Rubric 5
odrl:dutyappliedcc:Notice and cc:ShareAlike on odrl:distribute for 'You must ensure that anyone who gets a copy of any part of the Software from You also gets a copy of the terms and conditions in this Agreement', and dalicc:modificationNotice added on odrl:modify and odrl:derive for the prominent-notice sentence.
-
major Rubric 6
dalicc:WarrantyDisclaimerappliedThe No Liability section is one sentence covering warranty and liability, quoted whole into dalicc:WarrantyDisclaimer as in CAL-1.0 and Elastic-2.0. Thirteen further clauses are quoted in dalicc:additionalClauses, including all three governing-law paragraphs.
-
major Rubric 7
dalicc:governingLawapplieddalicc:governingLaw is a single literal naming the three laws the text picks between, because the property takes one short literal and the choice depends on where the licensee is: California for Asia, the Pacific and the Americas, Israel for Israel, England and Wales for Europe, the United Kingdom, the Middle East and Africa. All three paragraphs are quoted. cc:jurisdiction stays dalicc:worldwide, because the grant says worldwide; the governing law is not the territory of the grant. dalicc:terminatesOnBreach is true with a 30 day cure.
-
gap Rubric 8
dalicc:fieldOfUseRestrictionnoneThe service bar has no term. dalicc:fieldOfUseRestriction is the nearest literal and the clause is quoted in full. Proposed term: dalicc:competingServiceRestriction, the same term Elastic-2.0 needs, with a note that this text extends it to distribution that has the same effect.
-
gap Rubric 8
dalicc:governingLawnoneThe governing law depends on the licensee's location, which the property cannot express: it takes one literal and says nothing about who the licensee is. Proposed term: dalicc:governingLawByLocation, an annotation that pairs a territory of the licensee with the law that then governs. dalicc:governmentRightsLimitation is the only existing property that makes the governing law depend on who the licensee is, and it is about governments, so it is not used here.
-
info Rubric 9
recordnoneThe consistency check of app.services.composer, run against licensedata/dependencygraph/dg_default.ttl, returned no conflicts.
-
major Rubric 10
recordnoneAgainst Elastic-2.0 this record differs in three places: it has no licence-key clause, so no gap is recorded for circumventing one; its service bar also reaches distribution; and it carries dalicc:governingLaw, which Elastic-2.0 does not. The statement sets are otherwise the same.
Report an issue The review record as JSON The review checks the model against the license text. It is not legal advice.
History
This license model has 2 versions. Version 2 is the one served today; every earlier version keeps its own address, so a conclusion drawn from one of them can still be checked against it.
-
Version 2 current2026-09-24 Giray Havur
The changes since version 1 recorded which sentence of the text each statement rests on, named the license the record itself is published under and removed the quotes that do not name the act they support.
View version 2 JSON-LD Turtle RDF/XML
4 changes
-
changed
permission odrl:reproducewas
permission odrl:reproduceManual edit The statement now quotes the sentence of the licence text it rests on: "The Licensor grants You a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the Software, in each case subject to the limitations and conditions below."
-
changed
prohibition dalicc:ChangeLicensewas
prohibition dalicc:ChangeLicenseManual edit The statement now quotes the sentence of the licence text it rests on: "The terms and conditions of this Agreement do not imply any Licenses other than those expressly granted in this Agreement."
-
added
dct:license <https://creativecommons.org/licenses/by/4.0/>Manual edit Every record is published under CC BY 4.0. cc:license names the record DALICC keeps of that licence; dct:license now names it by the address Creative Commons publishes it at, so that a consumer matching the canonical IRI finds it.
-
changed
prohibition dalicc:ChangeLicensewas
prohibition dalicc:ChangeLicenseManual edit Removed the quoted evidence of prohibition dalicc:ChangeLicense: the quoted sentence does not name the act. The statements stay, read from the text without a linked quote.
-
-
Version 1
Created from the license text on 2026-09-22 (Source-available licences and riders).
Every change names the reason behind it: a finding of the content review, one of its library-wide decisions, the metadata that review wrote onto every record, or a hand edit. None of it is legal advice.
Nothing on this page is legal advice. What a license means is decided by its text; ask a legal advisor before you rely on it.