Question 1

What is the difference between AGPL-3.0-only and GPL-3.0-only?

Accepted Answer

Hosted SaaS: AGPL-3.0-only — AGPL-3.0-only section 13 requires that users interacting with a modified version over a network be offered the corresponding source of the whole work. Your distribution model is hosted SaaS, which triggers that obligation. This is the clause that makes AGPL behave differently from GPL for hosted services. GPL-3.0-only — GPL-3.0-only triggers its obligations on distribution. Your distribution model is hosted SaaS, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure.

Question 2

For hosted saas, is AGPL-3.0-only or GPL-3.0-only more restrictive?

Accepted Answer

AGPL-3.0-only: AGPL-3.0-only section 13 requires that users interacting with a modified version over a network be offered the corresponding source of the whole work. Your distribution model is hosted SaaS, which triggers that obligation. This is the clause that makes AGPL behave differently from GPL for hosted services. GPL-3.0-only: GPL-3.0-only triggers its obligations on distribution. Your distribution model is hosted SaaS, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure.

Question 3

For distributed binary, is AGPL-3.0-only or GPL-3.0-only more restrictive?

Accepted Answer

AGPL-3.0-only: AGPL-3.0-only carries the GPL-3.0 copyleft terms it is built on: distributing a work that incorporates it requires licensing the whole work under the same terms with corresponding source made available. Your distribution model is distributed binary or application, which is distribution and triggers that obligation. Section 13 additionally extends this over a network, so hosting the same code would not avoid it. GPL-3.0-only: GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is distributed binary or application, which triggers that obligation.

Question 4

For on-premises delivery, is AGPL-3.0-only or GPL-3.0-only more restrictive?

Accepted Answer

AGPL-3.0-only: AGPL-3.0-only carries the GPL-3.0 copyleft terms it is built on: distributing a work that incorporates it requires licensing the whole work under the same terms with corresponding source made available. Your distribution model is software delivered to a customer environment, which is distribution and triggers that obligation. Section 13 additionally extends this over a network, so hosting the same code would not avoid it. GPL-3.0-only: GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is software delivered to a customer environment, which triggers that obligation.

Question 5

For internal use only, is AGPL-3.0-only or GPL-3.0-only more restrictive?

Accepted Answer

AGPL-3.0-only: AGPL-3.0-only section 13 applies when users interact with the software remotely over a network, and its inherited GPL terms apply on distribution. Your distribution model is internal use only, so neither obligation arises. GPL-3.0-only: GPL-3.0-only triggers its obligations on distribution. Your distribution model is internal use only, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure.

Question 6

For published library, is AGPL-3.0-only or GPL-3.0-only more restrictive?

Accepted Answer

AGPL-3.0-only: AGPL-3.0-only carries the GPL-3.0 copyleft terms it is built on: distributing a work that incorporates it requires licensing the whole work under the same terms with corresponding source made available. Your distribution model is a published library, which is distribution and triggers that obligation. Section 13 additionally extends this over a network, so hosting the same code would not avoid it. GPL-3.0-only: GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is a published library, which triggers that obligation.

How you ship	AGPL-3.0-only	GPL-3.0-only
Hosted SaaS	Obligation triggered	No obligation	They differ here
Distributed binary	Obligation triggered	Obligation triggered	Same
On-premises delivery	Obligation triggered	Obligation triggered	Same
Internal use only	No obligation	No obligation	Same
Published library	Obligation triggered	Obligation triggered	Same

AGPL-3.0-only vs GPL-3.0-only

Can you use them, and where?

Side by side

AGPL-3.0-only

GPL-3.0-only