Glossary
AGPL (GNU Affero General Public License)
GPLv3 with one extra clause: if you modify the software and let people use it over a network, you must offer them your modified source. It closes the gap that let hosted services keep changes private.
General definition
AGPL (GNU Affero General Public License), currently version 3, published by the Free Software Foundation in 2007, is an open-source licence approved by the Open Source Initiative. It carries the terms of the GNU General Public License version 3: you may use, study, modify and redistribute the software, and if you distribute it, modified or not, you must do so under the same licence with source available. Section 13 adds the network condition: if you modify the program and let users interact with it remotely through a computer network, you must offer those users the corresponding source of your modified version. Under the plain GPL, running software on a server is not distribution, so a hosted service could modify it freely and never share; the AGPL removes that gap.
- Unmodified use: run the software, including as a service, with no new obligation beyond keeping the licence notices
- Modified and run as a service: you must offer the modified source to the users of that service
- Modified and distributed: ordinary GPLv3 terms apply, with source under the AGPL to recipients
- Combining: the AGPL and GPLv3 each contain a clause allowing code under the two licences to be combined
- Internal use: a modified copy run only for your own staff is not distribution; whether staff count as network users is a question most legal teams answer conservatively
Compared with permissive licences such as MIT and Apache 2.0, which let you embed code in a closed product with attribution only, the AGPL is the strongest form of copyleft in common use. Compared with source-available licences (the Business Source License, the Server Side Public License), it is a genuine open-source licence with no restriction on who may use it or for what; what it restricts is keeping modifications private. It is the usual choice for projects that want to stay open while discouraging cloud providers from offering a modified version as a competing service without contributing back. Infrastructure projects common in self-hosted stacks, such as Grafana and MinIO, use it, and several open-source LLM tools do as well.
For a buyer the practical questions are two. Will you modify the code? If not, the AGPL costs you nothing. If yes, and the modified system is reachable over a network by people outside your organisation, plan to publish those modifications or to obtain a commercial licence from the vendor, which is how open core companies typically offer the choice.
In the Ethora ecosystem
Ethora’s open-source core on GitHub, the monorepo at github.com/dappros/ethora, is published under the AGPL. If you run it unmodified and build your product against its API, the AGPL obligations do not reach your application, because the licence covers the Ethora code and modifications to it rather than separate programs that talk to it. If you modify the server itself and operate that modified server for users over the network, the AGPL asks you to make your modifications available to those users.
The packaged install route is licensed separately. The Ethora Core distribution, the Docker images, Helm chart and marketplace images described on the self-hosted team chat page, ships under the Ethora Core Software License: free to run with per-server limits, raised after free registration on the admin License page. Enterprise customers on a dedicated server get source access under their agreement. Read the licence that applies to the artefact you deploy, the GitHub source or the packaged Core, and ask when it is not obvious. For most teams, running Ethora unmodified as the chat and AI layer of their own product creates no AGPL obligation; this entry is an explanation, not legal advice.