Skip to content

Contact

Commercial licensing

pygslb is distributed under the AGPL-3.0-or-later; LICENSING.md in the repository explains what that grants and does not grant. A commercial licence — the same software under negotiated terms, without the AGPL obligations — is available on request, and a written agreement is required: there is no automatic or implied grant.

To ask for one, open an issue on the project (https://gitlab.com/claw-prj/pygslb/-/issues) titled Commercial licence with your organisation name and the intended use. A dedicated address replaces this channel when the project becomes public.

What the conversation covers, so the first answer is useful:

  • how pygslb is deployed today (single host, fleet, appliance) and at what scale;
  • what prevents you from using the AGPL version: closed-source redistribution, embedding in a product, an internal policy, or a support expectation;
  • the support or maintenance level you need, if any.

A commercial licence covers copyright and licence terms only. It does not grant any right on the project's name, and it carries no support, maintenance or SLA unless the contract says so.

Everything else

  • Bugs, documentation errors, feature discussions: the issue tracker, same address.
  • Security reports: please do not open a public issue; use a confidential issue on the same tracker, marked Security.
  • Operator questions about a deployment: the Troubleshooting page first, then the issue tracker.