License
Yagra is licensed under the GNU Affero General Public License v3.0 only
(AGPL-3.0-only) — see the
LICENSE file in the repository.
Every source file carries an SPDX license header.
Because Yagra is typically operated as a network service, note AGPL §13: if you run a modified version and let users interact with it over a network, you must offer those users the Corresponding Source of your modified version.
What this means in practice
Section titled “What this means in practice”The AGPL is more often avoided on reputation than on what it actually says, so, in plain language — the LICENSE text is what governs, and the following is a summary, not legal advice:
Running Yagra unmodified triggers nothing
Section titled “Running Yagra unmodified triggers nothing”§13 applies only if you modify the Program. Deploy the published images, configure them, monitor your network — no source-disclosure obligation arises, whether the users are your own staff or your customers.
Your data and configuration are not covered
Section titled “Your data and configuration are not covered”§13 reaches Yagra’s own source code. Your node inventory, dashboards, thresholds, alert history, collected metrics, credentials, and the configuration you feed Yagra are yours, and disclose nothing.
“Offer to users” is not “publish to the world”
Section titled ““Offer to users” is not “publish to the world””If you do modify Yagra and serve it over a network, the Corresponding Source goes to the people interacting with that instance — your own staff for an internal deployment, your customers if you host it for them. There is no obligation to publish it publicly or to contribute it upstream.
Writing a client is not modifying Yagra
Section titled “Writing a client is not modifying Yagra”Independent programs that talk to Yagra’s REST API or MCP surface are generally treated as separate works. Code added inside the workspace — a new check kind, a poller change, a WebUI change — is a modification.
Redistribution is the other trigger, and it is GPL-standard
Section titled “Redistribution is the other trigger, and it is GPL-standard”Passing Yagra’s binaries or images to a third party carries the usual §6 source obligation whether or not you modified it. That is identical under GPL-3.0 and is not an AGPL-specific term.
Commercial licensing
Section titled “Commercial licensing”For use under terms other than the AGPL — for example embedding Yagra in a proprietary product, or operating a modified version without the source-disclosure obligation — a separate commercial license may be available. Ask by opening an issue — GitHub Issues is the only contact channel for the project, and there is no contact e-mail address. Describe how you intend to use Yagra, since that is what determines whether the AGPL is a problem for you.
This documentation site
Section titled “This documentation site”This documentation site is a separate repository and is MIT-licensed; the Yagra product itself is AGPL-3.0-only as described above.