SA-SDL: a source-available software license
Publish your source code, let people modify and fork it, let them use it in products that make money. You only step in when someone sells the software itself and crosses the revenue threshold you choose.
What SA-SDL allows
The line is simple: build anything with the code, but selling the code itself as the product has conditions.
Allowed without asking
Section 1 and 2 of the license
- Modify the code, rename things, restructure it, fork it
- Use it in personal, internal and organizational projects
- Earn from ads, donations, stores, hosting and affiliate programs
- Use it as a component of a paid product: status page, admin panel, internal tool
- Skip attribution (it is appreciated, not required)
Needs the licensor's approval
Sections 3 and 4 of the license
- Selling the software as a standalone product, paid service or subscription once monthly revenue passes the threshold
- Using the licensor's names, logos, icons or favicons in public projects
What happens above the threshold
Only applies when the software is the product being sold. Every deadline is a number you set in the generator.
Revenue passes the threshold
Gross monthly revenue from the software as a standalone product exceeds the amount in the license.
The project is submitted
The licensee sends the project for review within the reporting window, for example 60 days.
The licensor decides
The licensor commits to a decision within the decision window, for example 60 days.
Approved, or stop selling
With approval, sales continue. Without it, commercial use stops or a separate commercial license is agreed.
What you fill in
The license text is fixed. These values make it yours.
| Parameter | Where it applies | Example |
|---|---|---|
| Copyright years and owner | Header | 2025 - 2026, MyCompany |
| Revenue threshold | Section 3 | 1,500 USD / month |
| Reporting window | Section 3 | 60 days |
| Approval window | Section 3 | 90 days |
| Licensor decision window | Section 3 | 60 days |
| Liability limit | Section 5 | 1.00 USD |
| Jurisdiction | Section 6 | the Republic of Poland |
SA-SDCL for approved SaaS projects
SA-SDCL is granted by the licensor on top of SA-SDL when a SaaS or subscription built on the code passes the revenue threshold. It does not replace SA-SDL, and most projects never need it.
Generate SA-SDCL- Requires an existing SA-SDL license
- Issued only with explicit written approval or a paid commercial license
- SA-SDL keeps covering non-commercial and lower-revenue use
- Trademark use still needs separate written consent
Adding SA-SDL to your project
Save the generated text as LICENSE in the repository root and point to it from your source files.
// Copyright (c) 2026 MyCompany // Licensed under SA-SDL v1.0, see the LICENSE file. // SPDX-License-Identifier: LicenseRef-SA-SDL-1.0
SA-SDL is not on the SPDX list, so LicenseRef- is the standard way to reference it.
Questions about SA-SDL
Is SA-SDL an open-source license?
No. SA-SDL is source-available. Anyone can read, modify and fork the code, but selling the software itself as a standalone product, paid service or subscription above the revenue threshold needs the licensor's approval. That condition means it does not meet the Open Source Definition.
Can I use SA-SDL software in a commercial project?
Yes. Ads, donations, online stores, hosting, affiliate programs and paid features inside a larger product are all allowed without asking. Consent is only needed when the software itself is what you sell.
When do I need the licensor's approval?
When the software, original or modified, is offered directly as a standalone product, paid service or subscription and the gross monthly revenue it generates exceeds the threshold written into the license. You then submit the project within the reporting window and need approval to keep selling it.
What is SA-SDCL and do I need it?
SA-SDCL is a commercial extension the licensor grants on top of SA-SDL for approved SaaS projects above the threshold. It is not a standalone license. Most projects never need it.
Do I have to credit the original author?
No. Attribution is not required, though it is appreciated. What you cannot do is use the licensor's names, logos or icons in public projects without permission.
What happens when a newer version of SA-SDL is published?
Nothing changes for you. You keep the rights of the version you received the software under.
Does the generator send my data anywhere?
No. The generator runs entirely in your browser. Your values are only kept in your browser's local storage so they are still there next time.
Ready to license your code?
Fill in seven values and copy the result, or download it as a LICENSE file.