Do I have to open-source my code if I use AGPL-3.0?

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 software as a SaaS require source disclosure?

Yes. Making AGPL-3.0 software available over a network counts as distribution; you must offer source to users interacting with it remotely.

Is AGPL-3.0 compatible with the GPL?

GPLv3 family — compatible with GPLv3, AGPLv3, and LGPLv3.

GNU Affero GPL 3.0 (AGPL-3.0)

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'.

Key facts

SPDX id: AGPL-3.0-only
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: retain the copyright notice and license text.
AGPL-3.0: state significant changes made to the code.
AGPL-3.0: provide complete corresponding source of the combined work.
AGPL-3.0: the combined distributed work must be licensed under AGPL-3.0-only.

Internal use only (never distributed)

AGPL-3.0: retain the copyright notice and license text.
AGPL-3.0: state significant changes made to the code.

Public SaaS / hosted web service

AGPL-3.0: retain the copyright notice and license text.
AGPL-3.0: state significant changes made to the code.
AGPL-3.0: 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-only with source. A closed-source binary is not possible. Offering it as a network service also triggers source disclosure.

AGPL-3.0: retain the copyright notice and license text.
AGPL-3.0: state significant changes made to the code.
AGPL-3.0: provide complete corresponding source of the combined work.
AGPL-3.0: the combined distributed work must be licensed under AGPL-3.0-only.

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 in a commercial product?: Commercial use is permitted, but distributing the combined work requires releasing the whole work under AGPL-3.0-only 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?: 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 software as a SaaS require source disclosure?: Yes. Making AGPL-3.0 software available over a network counts as distribution; you must offer source to users interacting with it remotely.
Is AGPL-3.0 compatible with the GPL?: GPLv3 family — compatible with GPLv3, AGPLv3, and LGPLv3.

Compatibility with other licenses

Open the checker with AGPL-3.0 selected