AGPL‑3.0‑or‑later
Stella Ops is free / libre / open‑source software. Run it, study it, modify it, and redistribute it — even as a hosted service — so long as you ship the source under the same license.
Your four essential freedoms
- Use Stella Ops in any environment, commercial or private.
- Study every line of source (transparent SBOM included).
- Modify the code, add plug‑ins or fork entirely.
- Share copies, forks or SaaS instances — as long as recipients get the source under AGPL.
Reciprocity & the network‑use clause
The GNU Affero GPL v3 adds a network‑use requirement: if you modify Stella Ops and make it available over a network (e.g. SaaS), your users must be able to download the full source code of your modified version.
Action | Requirement |
---|---|
Run unmodified binaries | No extra steps |
Publish a fork | Keep AGPL & provide full source |
Offer as SaaS | Provide source of your running version to every user |
Embed in a closed‑source product* | Permitted only if the entire combined work is distributed under AGPL‑3.0‑or‑later and the complete corresponding source is offered. |
*“Closed‑source” in the proprietary sense — you may bundle Stella Ops inside commercial software, but the resulting product must remain AGPL and users must receive the full source code.
Fork freely — sustain via donations
Experiment, fork, and build bespoke editions — it’s encouraged. If your variant gains traction, contribute upstream or maintain it independently. Financial support for security updates and roadmap velocity is handled via Open Collective.
Governance details live in /governance/.
Supply‑chain attestation
Every release is cosign‑signed with our public key (SHA‑256: AB12…EF90
) and ships a full, Buildx‑attested SPDX SBOM.
--key https://stella‑ops.org/keys/cosign.pub \
registry.stella-ops.org/stella-ops/stella-ops:<VERSION>