# GNU Affero General Public License (AGPL)

> Like the GPL. But if you run your changed copy as a web app, you must share the code.

**Field:** Software Development  
**Category:** Product & Releases  
**Also known as:** AGPL, AGPLv3, AGPL-3.0, Affero GPL

## Think of it like

It is like a soup rule. Even if you just sell the soup, you must share the recipe.

## Definition

The AGPL is the strongest common copyleft license. It has the rules of the GPL, plus one more for the web. With the GPL, the duty to share code starts when you hand out copies. With the AGPL, it also starts when people use your changed version over a network. So if you run a changed AGPL app as a website, its users can ask for the code.

## Example

Jack's startup changes an AGPL chat server and runs it for customers online. The AGPL means he must offer those customers his changed code.

## Why it matters

Most software today runs on servers, not in copies people download. The AGPL closes that gap, so firms check for it with care.

## Common mistake

Thinking a web service never counts as sharing. Under the AGPL it does. This is a plain summary, not legal advice.

## Three principles

- **GPL plus one.** All the GPL rules still apply.
- **Network use counts.** Users of the service get the code.
- **Strongest common one.** The most rules of the copyleft group.

## Related terms

- [GNU General Public License (GPL)](https://learn.benibix.com/term/development/gnu-gpl)
- [Copyleft](https://learn.benibix.com/term/development/copyleft)
- [Software License](https://learn.benibix.com/term/development/software-license)
- [Open Source Software](https://learn.benibix.com/term/development/open-source)

## Told apart from

- [GNU GPL vs AGPL](https://learn.benibix.com/compare/gpl-vs-agpl): People think the GPL makes you share code for a web app, and it does not. With the GPL, the duty to share starts when you hand out copies. Running changed code on your own server is not handing it out. The AGPL adds that rule, so users of the web service can ask for the code too.

![A line of licences from the fewest rules on the left to the most on the right. Permissive: MIT, BSD and Apache 2.0, where you only keep the notice. Weak copyleft: LGPL and MPL 2.0, where you share changes to the library or the file. Strong copyleft: GPL, where you share the code of the whole program you hand out. Network copyleft: AGPL, where running it as a web service counts too.](https://learn.benibix.com/diagrams/dev5-license-spectrum.svg)

---

Source: https://learn.benibix.com/term/development/agpl
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
