docsloth.dev
Licensing
Three repositories, three licences, no ambiguity. The AGPL is not a SaaS-competition ban: you may run the engine as a service, and if you modify and offer it to users you publish your modifications.
| Repository | Licence | What it covers |
|---|---|---|
docsloth-components | Apache-2.0 | Contracts, renderer, SDKs, registry client and the 48 first-party components. Reusable in any project, including commercial ones. |
docsloth-core | AGPL-3.0-only | The server, CLI, studio, extractors, planner, verifier and adapters. Self-hosting is free; modified versions offered over a network must publish their corresponding source. |
docsloth-cloud | Proprietary | The managed control plane, billing, fleet and commercial sites. It consumes the public contracts and operates the public engine; it does not reimplement it. |
Practical consequences
- Browser packages never bundle AGPL server code, so your static site stays permissively licensed.
- Release artifacts carry an SBOM and, where required, the corresponding source for AGPL components.
- Contributions are accepted under a Developer Certificate of Origin; contributor rights are never inferred from repository ownership.
- Trademarks are separate from copyright: forks must not imply endorsement.