The AGPL, or GNU Affero General Public License, is a strong copyleft license that extends the obligations of the GPL to software accessed over a network, so that anyone who runs a modified version as a service must offer its complete corresponding source code to the users interacting with it. In software licensing, it is the standard answer to the so-called SaaS loophole, the gap that lets providers modify GPL code and run it on servers without ever distributing it.
The current version, AGPL version 3, was published by the Free Software Foundation in 2007. It is recognized as both a free software license and an open source license, yet it is also the license that corporate legal departments restrict most often, which makes its exact scope worth understanding in detail.
How the AGPL closes the network gap
The AGPL closes the network gap by attaching a source obligation to remote interaction, not only to distribution. Under the ordinary GPL, the duty to share source code arises when a program is conveyed to another party, for example as a download or on a device. A web application that never leaves its operator’s servers is never conveyed, so the GPL imposes no sharing duty, even when the operator has heavily modified the code.
The AGPL adds one decisive clause, Section 13, titled remote network interaction. It states that if a licensee modifies the program, the modified version must prominently offer all users interacting with it remotely through a computer network an opportunity to receive the corresponding source, at no charge, through some standard means of software copying. In practice, operators satisfy this with a visible source link in the user interface, an API endpoint or a repository reference in the service footer.
Apart from Section 13, the AGPL version 3 text is nearly identical to GPL version 3. It inherits the same rules on patents, anti-tivoization for user products, and termination with a 30-day cure period. Section 13 of each license also explicitly allows combining GPLv3 and AGPLv3 code into one work, with each part keeping its own terms.
The table below shows which actions trigger the source obligation under the GPL and under the AGPL.
| Action | GPL version 3 | AGPL version 3 |
|---|---|---|
| Distributing binaries or installers | Source must be offered | Source must be offered |
| Running unmodified code as a service | No obligation | No obligation to provide source changes |
| Running modified code as a service | No obligation | Source must be offered to network users |
| Internal use by employees only | No obligation | Obligation to those internal users |
| Private modification never run for others | No obligation | No obligation |
Key terms and versions of the AGPL
Correct application of the AGPL depends on a few defined terms that carry precise legal meaning. The corresponding source includes all source code needed to generate, install and run the object code, including build scripts and interface definition files, but excluding general system libraries. A covered work is the unmodified program or any work based on it.
The license also has a history that explains why two similarly named texts exist. The following table lists the versions and their status.
| Version | Year | Publisher | Current status |
|---|---|---|---|
| Affero GPL version 1 | 2002 | Affero, Inc. | Superseded, based on GPLv2 |
| Affero GPL version 2 | 2007 | Affero, Inc. | Transition license toward AGPLv3 |
| GNU AGPL version 3 | 2007 | Free Software Foundation | Current and widely used |
Projects normally choose between “AGPL-3.0-only” and “AGPL-3.0-or-later”, the two SPDX identifiers for the license. The or-later form lets recipients accept any future version that the Free Software Foundation publishes, while the only form fixes the terms permanently.
How the AGPL compares with other licenses in the topic
The AGPL sits at the strongest end of the copyleft spectrum among widely used licenses. Permissive licenses such as the MIT License, the BSD license and the Apache License require little beyond attribution, while weak copyleft licenses such as the LGPL and the Mozilla Public License confine obligations to specific files or libraries. The GPL covers distributed derivative works, and the AGPL extends that reach to network use.
| License | Copyleft type | Scope of obligation | Network use covered |
|---|---|---|---|
| MIT License | None, permissive | Keep notice and license text | No |
| Apache License 2.0 | None, permissive | Notices, change statements, patent grant | No |
| Mozilla Public License 2.0 | Weak, file-level | Modified files only | No |
| LGPL version 3 | Weak, library-level | The library and its modifications | No |
| GPL version 3 | Strong | Whole derivative work when conveyed | No |
| AGPL version 3 | Strong, network | Whole derivative work, conveyed or served | Yes |
A common confusion concerns the Server Side Public License, a later license modeled on the AGPL that extends obligations to the entire service stack. Unlike the AGPL, it is not approved by the Open Source Initiative, and it should not be treated as an AGPL variant.
When projects and companies choose the AGPL
Projects choose the AGPL when their software is most valuable as a hosted service and they want improvements to flow back to the community. Typical examples are web applications, databases, collaboration platforms, mail servers and federated social networking software, where a cloud provider could otherwise offer a closed, improved fork.
Commercial vendors frequently pair the AGPL with dual licensing: the community edition is released under the AGPL, and customers who cannot accept its terms buy a commercial license. This model requires the vendor to hold all copyrights, which is why such projects often ask contributors to sign a contributor license agreement.
The decision table below summarizes how organizations typically handle AGPL components.
| Situation | Typical choice | Reason |
|---|---|---|
| Using an unmodified AGPL database over a network | Usually acceptable | No modification, so Section 13 is not triggered |
| Modifying an AGPL web application for customers | Publish the source | Remote users must receive the modified code |
| Embedding AGPL code into a proprietary SaaS product | Avoid or buy a commercial license | Whole combined work would fall under the AGPL |
| Starting a server project that must stay open | Choose AGPL-3.0-or-later | Prevents closed hosted forks |
| Building a library meant for broad adoption | Prefer a permissive or weak copyleft license | Many companies block AGPL dependencies |
Limitations, risks and common misconceptions
The main limitation of the AGPL is that its boundaries depend on legal interpretation that courts have rarely tested. Whether a separate service communicating over an API forms a single derivative work, or remains a separate program, is debated, and the answer depends on how tightly the components are integrated and exchange internal data structures.
- Misconception: any use requires publishing code. Running an unmodified AGPL program creates no duty to share changes, because there are none; the original source remains available upstream.
- Misconception: AGPL code cannot be sold. Commercial use and sale are permitted, provided the copyleft terms are respected.
- Risk: accidental contamination. A developer who copies AGPL code into a proprietary service can place the entire combined product under AGPL obligations.
- Risk: corporate policy conflicts. Many enterprises ban AGPL dependencies outright, which can reduce adoption of an AGPL project.
- Limitation: unmodified copies. Section 13 applies only to modified versions, so a provider running stock code owes users no extra source offer.
In plain words
The AGPL is a set of rules that comes with some free programs. It says you may use, change and share the program, but if you change it and let other people use it, you must also let them have your changed recipe.
Ordinary copyleft licenses only ask you to share when you hand the program to someone. Many programs today run on a website, so nobody ever receives a copy. The AGPL treats letting people use it online like handing it over, so the improvements stay open for everyone.
A real-world example
A small company offers a hosted project management service built on an open source collaboration platform released under AGPL-3.0-or-later. Its developers add a custom invoicing module and a faster search feature, then run the modified platform for about 400 paying customers.
Because remote users interact with modified AGPL software, the company adds a “Source code” link to the application footer that points to a public repository containing the complete modified source, including build scripts. Its proprietary billing system communicates with the platform only through a documented REST API and stays separate.
Before an investor review, the legal team audits the arrangement and confirms that the source offer satisfies Section 13. The company keeps its competitive advantage in service quality and support, while its search improvements are later merged upstream by the original project.