Question 1

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

Accepted Answer

Distributed binary: 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. LGPL-3.0-only — LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it. On-premises delivery: 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. LGPL-3.0-only — LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it. Published library: 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. LGPL-3.0-only — LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it.

Question 2

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

Accepted Answer

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. LGPL-3.0-only: LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it.

Question 3

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

Accepted Answer

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. LGPL-3.0-only: LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it.

Question 4

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

Accepted Answer

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. LGPL-3.0-only: LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it.

Question 5

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

Accepted Answer

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. LGPL-3.0-only: LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it.

Question 6

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

Accepted Answer

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. LGPL-3.0-only: LGPL-3.0-only requires publishing modifications to the library itself, but under dynamic linking that obligation does not extend to the code that calls it.

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

GPL-3.0-only vs LGPL-3.0-only

Can you use them, and where?

Side by side

GPL-3.0-only

LGPL-3.0-only