Skip to main content
License encyclopedia

License comparison

AGPL-3.0 vs GPL-3.0: network source duties

A patched service is where these licenses part company. If users interact remotely with your modified AGPL program, section 13 requires a prominent offer of that version's corresponding source, at no charge. GPL-3.0 has no equivalent network condition. Both licenses impose source and licensing duties when you distribute covered software, so a hosted service and a customer download need separate review.

Compare the permissions, limits and obligations recorded in each guide. Read the license text for the full conditions that apply to your release.

Permissions

AGPL-3.0-only

  • Commercial use

    You may ship the code inside a paid product. The license does not restrict commercial use.

  • Modify

    You may change the code, including keeping those changes private, unless a later obligation says otherwise.

  • Distribute

    You may give copies to others. Distribution is what usually turns notice and source duties into real work.

  • Private use

    Use inside your company, including internal forks, does not by itself trigger distribution duties.

GPL-3.0-only

  • Commercial use

    You may ship the code inside a paid product. The license does not restrict commercial use.

  • Modify

    You may change the code, including keeping those changes private, unless a later obligation says otherwise.

  • Distribute

    You may give copies to others. Distribution is what usually turns notice and source duties into real work.

  • Private use

    Use inside your company, including internal forks, does not by itself trigger distribution duties.

Limits

AGPL-3.0-only

  • Hold liable

    The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.

  • Use trademark

    The license is not a trademark license. Names, logos and product marks stay with their owners unless a separate grant says otherwise.

  • Open your product

    Copyleft can reach a combined work you distribute, not only the original files. How far that reaches in your stack is a counsel question.

  • Network copyleft

    Hosting is not a loophole here. Network interaction with a modified covered work is what wakes the source duty.

  • Later AGPL

    AGPL-3.0-only pins version 3. Recipients cannot elect a later Affero GPL from the FSF.

GPL-3.0-only

  • Hold liable

    The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.

  • Use trademark

    The license is not a trademark license. Names, logos and product marks stay with their owners unless a separate grant says otherwise.

  • Open your product

    Copyleft can reach a combined work you distribute, not only the original files. How far that reaches in your stack is a counsel question.

  • Network copyleft

    Classic GPL has no network clause. Offering the program as a hosted service, without distributing a copy, does not by itself trigger the source offer.

Obligations

AGPL-3.0-only

  • Include copyright

    Keep copyright notices on distributed copies.

  • Include license

    Give recipients a copy of the license with the program.

  • Disclose source

    When you distribute a binary of a covered work, corresponding source has to be offered in the way the license describes.

  • Same license

    The combined work you distribute has to stay under this license. You cannot close the covered work with a more restrictive grant.

  • Disclose source

    AGPL adds a network trigger. If users interact with a modified covered work over a network, they must be able to get the corresponding source.

GPL-3.0-only

  • Include copyright

    Keep copyright notices on distributed copies.

  • Include license

    Give recipients a copy of the license with the program.

  • Disclose source

    When you distribute a binary of a covered work, corresponding source has to be offered in the way the license describes.

  • Same license

    The combined work you distribute has to stay under this license. You cannot close the covered work with a more restrictive grant.

  • Installation Information

    Section 6 also asks for Installation Information when a binary ships in a User Product, so the owner can run a modified build on the device.

License texts

Practical guidance for procurement review, not legal advice. Confirm high-stakes use with counsel.

Cookies on sourcetrust.dev

We use essential cookies for security, including abuse prevention on our site scan and walkthrough request form. With your permission, we also use optional analytics and diagnostics (Google Tag Manager on this site, and the Sentry browser SDK on the SourceTrust application when configured). See our cookie policy.