Unlike GPL, AGPL adds a source-offer duty for modified versions reached over a network. Re-check it whenever you modify a networked instance.
FREE LICENSE REVIEW TOOL · NOT LEGAL ADVICE
Which AGPL-3.0 obligations apply to your MonkeyCode use?
MonkeyCode is published under GNU AGPL-3.0. Answer four questions about how you deploy it, and this navigator lists the obligation areas to bring to qualified counsel. It surfaces questions; it does not interpret your situation.
OBLIGATION AREAS · 1 area to reviewReview with counsel
This tool lists questions and obligations to review with qualified counsel. It is not legal advice, does not interpret your specific facts, and does not replace reading the license.
Read the AGPL-3.0 textHow to read this
Obligation areas, not a compliance verdict.
Navigator version 2026-07-14. The baseline notice-and-source obligation always applies; each checked scenario adds an area to document before deployment.
Document the exact revision, changes, users, delivery, and dependencies. A current inventory is stronger than a product label.
Trademarks, model or provider terms, dependencies, and any hosted-service terms are reviewed independently of the code license.
Static example
Internal, unmodified use is the lightest case.
With nothing checked, the navigator lists the areas below. Check any box to add scenario-specific areas.
| Obligation area | What to confirm |
|---|---|
| Keep license notices and source access | AGPL-3.0 keeps the software free to run, study, and modify. Preserve the license text and copyright notices, and keep a path to the corresponding source for any version you run or convey. |
| Internal, unmodified use is the lightest case | Running an unmodified instance for your own team is the simplest scenario. Still confirm license notices, your update and inventory process, and re-run this check before you modify, network-expose, or distribute it. |
AUTHORITATIVE TEXT
Use the repository License and counsel, not this summary.
Method: This navigator maps deployment answers to obligation areas from the AGPL-3.0 license. It is not legal advice, does not cover every clause, and does not replace reading the license and consulting counsel.
What does the AGPL-3.0 obligation navigator do?
It maps four deployment answers—modifying the source, network use, distribution, and combining MonkeyCode with your own code—to the AGPL-3.0 obligation areas to review. It surfaces the questions to bring to counsel; it does not interpret your situation or cover every clause.
Is this legal advice?
No. The navigator is an educational checklist, not legal advice. Confirm your obligations by reading the AGPL-3.0 text and consulting qualified counsel with your exact revision, changes, users, delivery, and dependencies.
What makes AGPL-3.0 different from the GPL here?
AGPL-3.0 adds Section 13: users who interact with a modified version over a network must be able to obtain the corresponding source. Re-check this obligation whenever you modify a networked instance.