GNU Affero GPL 3.0 or later (AGPL-3.0-or-later)
GPLv3 PLUS a network clause: making the software available over a network (SaaS) counts as distribution, so you must offer source to remote users. The clause that catches startups who assumed SaaS never 'distributes'. The 'or later' clause additionally permits using the work under any later version the FSF publishes; none exists today, so it behaves as AGPL-3.0-only in practice.
Key facts
- SPDX id
- AGPL-3.0-or-later
- Category
- Network copyleft
- Copyleft scope
- network
- Express patent grant
- Yes
- SaaS triggers disclosure
- Yes
- GPL-compatible
- GPLv3 family — compatible with GPLv3, AGPLv3, and LGPLv3.
Obligations
When redistributing as open source.
- AGPL-3.0-or-later: retain the copyright notice and license text.
- AGPL-3.0-or-later: state significant changes made to the code.
- AGPL-3.0-or-later: provide complete corresponding source of the combined work.
- AGPL-3.0-or-later: the combined distributed work must be licensed under AGPL-3.0-or-later.
Internal use only (never distributed)
- AGPL-3.0-or-later: retain the copyright notice and license text.
- AGPL-3.0-or-later: state significant changes made to the code.
Proprietary software you distribute as a binary
No obligations.
Public SaaS / hosted web service
- AGPL-3.0-or-later: retain the copyright notice and license text.
- AGPL-3.0-or-later: state significant changes made to the code.
- AGPL-3.0-or-later: offer the source to users interacting with the software over the network.
Commercial use
Commercial use is permitted, but distributing the combined work requires releasing the whole work under AGPL-3.0-or-later with source. A closed-source binary is not possible. Offering it as a network service also triggers source disclosure.
Permissive: include notices (Apache also needs NOTICE + change statements). Weak copyleft: disclose only the modified library/files and, for LGPL static linking, provide a relink path. Strong copyleft (GPL): NOT possible to keep proprietary if GPL code is in the derivative work. AGPL: same as GPL plus network rules.
FAQ
- Can I use AGPL-3.0-or-later in a commercial product?
- Commercial use is permitted, but distributing the combined work requires releasing the whole work under AGPL-3.0-or-later with source. A closed-source binary is not possible. Offering it as a network service also triggers source disclosure.
- Do I have to open-source my code if I use AGPL-3.0-or-later?
- Yes — on distribution and on network use. The network clause extends source disclosure to users who interact with the software over a network.
- Does running AGPL-3.0-or-later software as a SaaS require source disclosure?
- Yes. Making AGPL-3.0-or-later software available over a network counts as distribution; you must offer source to users interacting with it remotely.
- Is AGPL-3.0-or-later compatible with the GPL?
- GPLv3 family — compatible with GPLv3, AGPLv3, and LGPLv3.
Compatibility with other licenses
- Is AGPL-3.0-or-later compatible with MIT? Yes
- Is AGPL-3.0-or-later compatible with BSD-2-Clause? Yes
- Is AGPL-3.0-or-later compatible with BSD-3-Clause? Yes
- Is AGPL-3.0-or-later compatible with ISC? Yes
- Is AGPL-3.0-or-later compatible with Apache-2.0? Yes
- Is AGPL-3.0-or-later compatible with BSL-1.0? Yes
- Is AGPL-3.0-or-later compatible with Unlicense? Yes
- Is AGPL-3.0-or-later compatible with CC0-1.0? Yes
- Is AGPL-3.0-or-later compatible with MPL-2.0? Yes
- Is AGPL-3.0-or-later compatible with EPL-2.0? No
- Is AGPL-3.0-or-later compatible with LGPL-2.1? It depends
- Is AGPL-3.0-or-later compatible with LGPL-3.0? It depends
- Is AGPL-3.0-or-later compatible with GPL-2.0-only? No
- Is AGPL-3.0-or-later compatible with GPL-2.0-or-later? It depends
- Is AGPL-3.0-or-later compatible with GPL-3.0-only? Yes
- Is AGPL-3.0 compatible with AGPL-3.0-or-later? Yes
- Is AGPL-3.0-or-later compatible with LGPL-2.1-or-later? It depends
- Is AGPL-3.0-or-later compatible with LGPL-3.0-or-later? It depends
- Is AGPL-3.0-or-later compatible with GPL-3.0-or-later? Yes