Copyleft, by default
Everything we start is GPLv3 or AGPLv3, and a fork keeps its upstream’s license so fixes can flow back. Nothing here is source-available, “open source with a commercial license for production use”, or a core with the useful parts held back.
| Project | License |
|---|---|
| inbuxa | AGPL-3.0-only; webmail AGPL-3.0-or-later |
| inbuxa-migrate | Apache-2.0 OR MIT (fork; keeps its upstream’s license) |
| ihasmail | AGPL-3.0-or-later |
| ihasvpn | AGPL-3.0-or-later |
| Cairn OBS | AGPL-3.0-or-later, including enterprise/ |
| stalwart-migrator | GPL-3.0 |
| ihasmail-oneshot | AGPL-3.0-or-later |
| SysAdminAutomation | GPL-3.0 |
Why AGPL for some and GPL for others
AGPL where the software is something you would run as a service for other people, GPL where it is a tool you run on your own machine. The distinction is the one the licenses themselves draw: AGPL closes the gap where a network service can be built on copyleft code without ever handing the improvements back, and mail and observability are exactly that shape. A migration script is not, so it does not need the extra clause.
No paid tier, no license carve-out
Cairn OBS has an enterprise/ directory in the tree, and the name
invites a fair question. It is not a paid edition, and the license does not
change when you open that directory: it is AGPLv3, like every other path in
the repository. Multi-tenant RBAC, the
directory integration, the alerting evaluator, the Terraform provider and the
AI-assisted query authoring are all in the same tree under the same terms.
There is no build with more features in it than the one you can compile.
What this costs
The trade is deliberate. Copyleft makes some commercial arrangements awkward, and a company that wants to embed one of these in a closed product will need a different conversation rather than a different download. That is the intended outcome. The reason to accept it is the one on how we work: the code under an incident should be code you can read, and a license is what makes that true next year as well as today.
If you are trying to work out whether your intended use is compatible, the license text in each repository governs and this page does not — it describes what is there, it does not grant anything. Ask at licensing@coffeylabs.org if it is genuinely unclear.