CaelLab BY-SA Code License
An attribution and share-alike license for code. Use it, modify it, ship it, sell it — as long as you credit the author and keep the whole of your modified version open on the same terms.
Plain text: https://www.caellab.com/license/cbs-v3.txt · First published September 30, 2026
This is a human-readable summary of (and not a substitute for) the license below.
You are free to:
- Share — copy and redistribute the work, in source or built form, in any medium or format.
- Adapt — remix, transform, translate, and build upon the work.
- Use commercially — for personal, commercial, or non-commercial purposes.
- Run it privately — including on your own servers, without publishing your changes.
The licensor cannot revoke these freedoms as long as you follow the license terms.
Under the following terms:
- Attribution (BY) — keep the copyright notice, credit the author, link to this license, and state whether you made changes.
- ShareAlike (SA) — release your modified version — the whole of it, not only the files you changed — under the CaelLab BY-SA Code License, Version 3, or a later version if the work says "or any later version", with no additional restrictions.
- Source code available — if you distribute the work or a modified version in built form, the complete corresponding source of that version goes with it, under this license.
- License preservation — the copyright notice and this license must be included in all copies or substantial portions of the work.
Notices:
- No trademark rights are given. This license grants copyright and patent rights only.
- A patent license is granted, and it ends if you file a patent suit over the work.
- The work is provided "as is", without warranties of any kind, express or implied, and the contributors are not liable for damages arising from its use.
Full License Text
Reproduced verbatim from the canonical plain text file. The text of this license is itself released under the CaelLab Zero Subject License.
What You Must Do
Four obligations, all of which trigger only when you distribute the work or a modified version.
Credit the author. Keep the copyright notice and the license text intact, name the Licensor, and link back to the original when you publish over the network.
Mark your changes. Say that you modified the work and identify which files you changed.
Ship the source. If you distribute a build, bundle, or minified copy, the complete corresponding source of that same version goes with it, under this license.
ShareAlike. The whole modified version — not only the files you changed — must be released under the CaelLab BY-SA Code License, Version 3, or a later final version of it if the work says "or any later version". That keeps the result free and open source. No extra restrictions, no DRM on top.
What's New in Version 3
Version 3 restates the Version 2.0 obligations in the CaelLab house style, and tightens ShareAlike the way GPLv3 does: the whole work, and pinned to the version you received it under.
| Change | 2.0 | 3 |
|---|---|---|
| Version numbering | 2.0 | 3 |
| Publication date on the text | None | September 30, 2026 |
| Publisher named in the text | CaelLab throughout | Steward (Section 0) |
| Where later versions come from | "canonical URL" of one file | /license/ (Section 6a) |
| Purpose of the conditions | Not stated | Stated in Section 3 |
| ShareAlike scope | The Modified Version | The whole work, as a whole |
| ShareAlike version | Any later final version | The version received, unless the work says "or later" |
| Attribution, source availability, patent, termination | Set out | Unchanged |
Works already published under 1.0 or 2.0 stay under that version unless their copyright holder says otherwise. New works should adopt Version 3, or any later version.
Comparison
Version 3 next to the licenses it is usually weighed against.
| Feature | MIT | Apache-2.0 | GPLv3 | CBSv3 |
|---|---|---|---|---|
| Commercial use | ✓ | ✓ | ✓ | ✓ |
| Private use | ✓ | ✓ | ✓ | ✓ |
| Modification | ✓ | ✓ | ✓ | ✓ |
| Explicit patent grant | ✗ | ✓ | ✓ | ✓ |
| "or later version" clause | ✗ | ✗ | ✓ | ✓ |
| Sublicensing | ✓ | ✓ | ✗ | ✗ |
| Closed-source derivatives | ✓ | ✓ | ✗ | ✗ |
| SaaS use triggers copyleft | ✗ | ✗ | ✗ | ✗ |
| Termination with cure period | ✗ | ✓ | ✓ | ✓ |
| License length | Short | Medium | Long | Medium |
How to Apply It
Put the full text in a file named LICENSE at the root of your project, and add a short header to each source file if you like.
// Copyright (c) 2026 [Your Name] // Licensed under the CaelLab BY-SA Code License, Version 3 // or any later version. https://www.caellab.com/license/cbs-v3.txt // Source: https://github.com/you/repo
<!-- Copyright (c) 2026 [Your Name] Licensed under the CaelLab BY-SA Code License, Version 3 or any later version. https://www.caellab.com/license/cbs-v3.txt Source: https://github.com/you/repo -->
/* * Copyright (c) 2026 [Your Name] * Licensed under the CaelLab BY-SA Code License, Version 3 * or any later version. https://www.caellab.com/license/cbs-v3.txt * Source: https://github.com/you/repo */
# Copyright (c) 2026 [Your Name] # Licensed under the CaelLab BY-SA Code License, Version 3 # or any later version. https://www.caellab.com/license/cbs-v3.txt # Source: https://github.com/you/repo
Frequently Asked Questions
Short answers, with the section that decides each one.
Does this apply to websites and web apps?
Yes. The term "Work" is defined in Section 0 to cover any code, markup, stylesheets, scripts, or configuration files used to build or run a website or application.
Can I use this in proprietary software internally?
Yes. The ShareAlike obligation in Section 3.3 only triggers when you distribute the work to others. Section 0 also makes clear that running the work on your own systems is not Distribution.
If I only run it as a network service, must I publish my changes?
No. Running the work on your own systems, including serving it as a website or API, is not Distribution. If you want that obligation, use AGPL-3.0 instead.
Can I relicense a modified version as MIT?
No. Section 3.3 requires the entire Modified Version, as a whole, to stay under this license, and Section 1 does not grant sublicensing rights.
What does "or any later version" mean?
You may follow the rules of Version 3, or the rules of any final version CaelLab releases under a higher, unsuffixed version number. Development, draft, preview, experimental, and modified versions, including forks of this license text, are not "later versions". As an author, the clause means people using your code can upgrade without asking you. It is also what lets a derivative move on at all: without the phrase, Section 3.3 keeps it on the exact version it received the work under.
Can I use this for docs, images, or articles?
No. This license is written for code: it talks about Source Code and Object Code, and Section 3.2 requires source to travel with a build. The CaelLab BY-SA Content License is no longer recommended — use CC BY-SA 4.0 for non-code works.
Is the text on this page the license itself?
The binding version is the plain text file at /license/cbs-v3.txt; the copy on this page is reproduced from it for reading. When you cite the license, link to that URL, not to this page.
Can I modify the license text?
Yes. The text of this license is itself released under the CaelLab Zero Subject License, so you may copy and adapt it freely. A modified text is not the CaelLab BY-SA Code License, and the CaelLab name and marks are not licensed for presenting it.
Can I dual-license?
Only the copyright holder can. A licensor may offer the same work under another license in addition to this one, but a recipient of the work cannot add or swap licenses.
Is this an OSI-approved license?
No. It is a custom license, not reviewed or approved by the OSI or the FSF. Some organizations have policies that block custom licenses, so check before adopting it for critical projects.
CaelLab Notice
CaelLab is not a party to its public licenses. Notwithstanding, CaelLab may elect to apply one of its public licenses to material it publishes and in those instances will be considered the "Licensor." The text of this license is itself released under the CaelLab Zero Subject License, so it may be copied and adapted freely. Except for the limited purpose of indicating that material is shared under a CaelLab public license or as otherwise permitted by CaelLab, CaelLab does not authorize the use of the trademark "CaelLab" or any other trademark or logo of CaelLab without its prior written consent. For the avoidance of doubt, this paragraph does not form part of the public licenses.
CaelLab may be contacted at caellab.com.