On this page
The selected condition is about a modified program and its users
AGPLv3 section 13 addresses a modified version that supports remote network interaction. It requires a prominent offer to all users interacting with that version remotely to obtain its Corresponding Source from a network server at no charge, through standard or customary copying means.
Corresponding Source covers the code and scripts needed to generate, install, run and modify the covered work, with the licence’s stated exclusions. This does not mean every database record, every unrelated program or every hosted product is automatically covered. Establish the actual program, modifications and boundaries first.
A download-only checklist can miss the live service
Fictional example: the parent modifies a covered scheduling program and its U.S. partner offers that version to customers through a browser. The release checklist says no customer installer, so no source work. That does not answer section 13’s modified-network-interaction question.
| Service record | What management needs to establish |
|---|---|
| Actual program | Licence/version and the code actually used. |
| Modifications | What changed, by whom and the assessed covered-work boundary. |
| Remote users | Which users interact with that modified version. |
| Source offer | Where the relevant users see it and how the actual source is obtained. |
| Updates | Who keeps the offer and source matched to the deployed release. |
Rehearse the recipient’s route
Using an authorised test account, ask the release team to demonstrate the offer and the corresponding version that a user can obtain. Record missing links, access failures and version mismatches. A source archive in a private developer folder is a different thing.
The technical and licence reviewers must decide the actual package, boundaries and other conditions. Do not assume the operating company may delete required source material merely because it considers it commercially sensitive.
Allocate deployment and continuing responsibility
The overseas developer, hosting operator and U.S. partner may perform different jobs. Agree who approves releases, who operates the source route and who handles a licence question after an update. Include the continuing work in the service model.
Keep customer data, credentials and private legal records out of the ELN worksheet. A source-licence assessment does not settle customer-data access, security or service permissions.
Scope
- Selected AGPLv3 provisions and a fictional service example. No particular application, modification, combined-work scope, source package, privacy or complete licence compliance is determined.
Next step
Use Management dependence to assign the program-boundary review, deployment/source-offer jobs and the backup person for updates.
Sources & review notes
Free Software Foundation
Passage, dates and research notes
public-software-licence · Sections 0–2 and 13, complete selected text; modified remote-network interaction and Corresponding Source
Read actual definitions/source/basic permissions and both paragraphs of 13. The guide does not infer every hosted service is modified/covered or determine combined-work boundaries.
Detailed rule records (1)
Section 13 requires a modified version supporting remote interaction to prominently offer all users interacting with it remotely an opportunity to receive its Corresponding Source from a network server at no charge through standard/customary copying means.
GNU Affero General Public License, version 3Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.