Skip to content

Lesson 5 · network

Network interaction and AGPL

Evaluate the modified program and its interacting users.

GPL distribution obligations do not ordinarily arise solely because software runs on a server. AGPL section 13 addresses a different event: users interacting remotely with a modified version of the program, where that version supports such interaction.

The source offer is to the interacting users. Do not substitute a claim that every dependent HTTP client must be published. Determine the scope of the covered program and any combined work from the supplied facts.

Internal-only deployment does not by itself answer the AGPL network question. Employees can be interacting users too. Conversely, the mere presence of an unmodified AGPL executable on a machine does not make every local program part of it.

Here the modified library and app are expressly one combined network service. The app owner authorizes compatible release terms. Repair the release terms and source offers for this modeled combined work.

Try it: The modified service

The modified AGPL library and app are one service exposed to remote users. The app owner authorizes an AGPL release. Meet the combined-work terms and source-offer obligations.

Before inspecting the result

What does this supplied release need before its modeled requirements are met?

Prediction

Project boundary

2 components
bundleappLicenseRef-ProprietarylibraryAGPL-3.0-only
Dependency relationships
From → toConnectionSemantics
app → librarybundleintimate

Supplied facts

Distribution
private
Network interaction
Yes
Intended use
commercial-service
Evaluation date
2026-10-24
Policy
learning

These facts define the simulation. Evidence declarations stand in for actual corresponding source, relinkable objects and release materials.

Components

Declared license
LicenseRef-Proprietary
Modified files
None
Artifact
code

Third-party grants remain fixed unless this scenario supplies authority to change them.

Project artifacts

Evidence artifact format

Source offers contain “component: id” and “source: https://…” on separate lines. Covered-file offers also list the covered paths. Relinking declarations contain “replace-compatible-library” for dynamic linking or “relink-object-files” for static linking, and “reverse-engineering-permitted”. These declarations model supplied release artifacts.

License reference

permissions
commercial-use, modifications, distribution, private-use
conditions
include-copyright, include-license
limitations
liability, warranty
Read authoritative terms ↗

Expression builder

Each row is one selectable alternative. AND retains every term in a row.
AlternativeRequired licenses
1MIT AND LGPL-3.0-only
2Apache-2.0 AND LGPL-3.0-only
Results appear after submission.