Copyleft · includes modified network services
AGPL v3, in plain English.
TL;DR
You can use and change it, even commercially. If people use your modified version over a network, offer them its corresponding source under the AGPL. Sharing copies has source-sharing duties too. Sharing source code is different from sharing users’ content.
Source: SPDX · AGPL v3 license text, including section 13 ↗What can I do with it?
- Self-host it for yourself
- Yes.
- Use it for your business
- Yes. Commercial use is allowed.
- Change the code
- Yes.
- Keep your changes private
- Not from users interacting with your modified version over a network; offer them its source.
- Share or sell copies
- Yes. Meet AGPL source-sharing and notice requirements.
What do I need to do?
- Preserve notices, include the license and mark changes when distributing covered code.
- If you modify the program, prominently offer its corresponding source to users interacting with that version over a network.
- Provide the source needed to build and run the covered version under the AGPL.
AGPL adds a network-service requirement to GPL-style copyleft. Check the exact version and any exceptions in the repository.
A real-world example
You change an AGPL app and host it for customers. Offer those users the corresponding source of your modified version, even if they only use it in a browser.
The code license and the hosting bill are separate.
A license tells you what you can do with the code. It doesn’t make Cloudflare, domains, email delivery or other services free. Check the project’s hosting notes as well.
This is a general explanation. The repository’s exact license, version, exceptions and package-specific terms govern. Other packages, dependencies and images can have different licenses.
Read the complete license terms ↗