License
OpenTremor uses two open source licences: the GNU AGPL v3 or later for the server, and Apache-2.0 for its packs and supporting projects. Both are approved by the Open Source Initiative. This page summarizes what those licences mean for people who use or extend OpenTremor.
The short version
Section titled “The short version”- Use it — yes. You can self-host it for your team or company, including for commercial use.
- Change it — yes. If you modify the server and people use it over a network, offer those users the modified source under the AGPL.
- Extend it — yes. You can write a pack under any licence if it meets the pack plugin exception’s requirements. You can also fork the Terraform provider or Helm chart under Apache-2.0.
Which licence covers what
Section titled “Which licence covers what”| Modules | What they are | Licence | In practice |
|---|---|---|---|
core · platform · dashboard · task-scheduler | The server: the API, the analysis engine, the web UI and the scheduler | AGPL-3.0-or-later + pack plugin exception | You can use and modify them. The AGPL applies to modifications to these components. |
pack-* · terraform-provider · mcp · deployments · monitoring · docs | Packs, the Terraform provider, MCP, deployment files, monitoring assets and docs | Apache-2.0 | You can fork and redistribute them under Apache-2.0 terms. Keep required licence and notice text, and mark changed files as required by the licence. |
Can I…?
Section titled “Can I…?”| I want to… | Allowed? | What I owe |
|---|---|---|
| Self-host OpenTremor for my team or company, as it ships | Yes | The licences impose no fee for this use. |
| Call it from my own scripts, CI jobs or MCP agents | Yes | The AGPL covers OpenTremor. Whether separate code forms a combined work depends on the circumstances. |
| Write my own pack and keep it closed-source | Yes | It must meet the pack plugin exception’s requirements, including using core only through the pack plugin API. |
| Fork a pack, the Terraform provider, the Helm chart or the Grafana dashboards | Yes | Follow Apache-2.0, including keeping required licence and notice text and marking changed files. |
| Modify the server and run it for my own company | Yes | Offer the modified source under the AGPL to people who interact with it over a network. |
| Run OpenTremor as a hosted service for my own customers | Yes | If you modify the server, offer the modified source under the AGPL to users who interact with it over a network. The licences grant no rights to the OpenTremor name. |
| Ship the server inside my own product — an image, an appliance, an installer | Yes, under the AGPL or a separate commercial licence | Follow the AGPL terms for the server and any work covered by it, or arrange a commercial licence. |
| Copy parts of core’s source code into my own product | It depends | Copying or incorporating code beyond the pack plugin API is not covered by the pack plugin exception. The applicable obligations depend on how the code is used and distributed. |
Examples
Section titled “Examples”| Who | Situation | Outcome |
|---|---|---|
| A platform team | Runs OpenTremor on its own Kubernetes cluster for 200 engineers, every pack on | The licences allow this use. |
| A consultancy | Builds a paid pack for a client’s in-house configuration language | The pack may use any licence if it meets the plugin exception’s requirements. |
| An SRE | Forks the Helm chart for an unusual cluster setup and keeps it private | Apache-2.0 applies. Follow its terms, including preserving required notices and marking changed files. |
| A fintech | Patches core to plug in an internal approval system | If engineers interact with the modified server over a network, offer them the modified source under the AGPL. |
| A startup | Adds features and sells it as its own hosted review service | If customers interact with the modified server over a network, offer them the modified source under the AGPL. The licences grant no rights to the OpenTremor name. |
| A security vendor | Wants to bundle the server in a closed-source on-premise appliance | Follow the AGPL terms for the server and any work covered by it, or arrange a separate commercial licence. |
Questions
Section titled “Questions”Is OpenTremor really open source? Yes. The GNU AGPL v3 and Apache-2.0 are OSI-approved. The modules use these licences; there is no source-available tier or time-delayed licence.
Will the AGPL spread to my own code? The answer depends on how your code relates to OpenTremor. Scripts, CI jobs and agents that call the API are separate programs in many cases, and packs that meet the plugin exception’s requirements are covered by that exception. For other cases, review the licence terms.
Do I have to publish my changes on GitHub? The AGPL requires you to offer source to the people who interact with your modified version over a network. It does not require you to publish changes to the whole world.
Why not one licence for everything? The server uses the AGPL, while packs and supporting projects use Apache-2.0. The pack plugin exception allows qualifying packs to use a licence of their author’s choice. Without the exception, writing a pack would require licensing it under the AGPL because it necessarily imports from core.
What does “or later” mean? You may follow the terms of AGPL version 3 or of any later version the Free Software Foundation publishes.
The AGPL doesn’t suit my use. Now what? A separate commercial licence is available. Contact
the copyright holder at the address in a module’s NOTICE file.