Licensing and source availability

This page separates the upstream license, the recorded deployment configuration, and source-availability work that must not be assumed complete. The governing text is the repository’s LICENSE, not this operational summary. Evidence: LICENSE:1-6,540-551.

License identity

OpenMAIC identifies its license as GNU Affero General Public License version 3, dated 19 November 2007. Package metadata uses the identifier AGPL-3.0, and the README links the same license text. Evidence: LICENSE:1-6; package.json:5; README.md:478-480.

This is not a statement that a separate commercial license has been acquired. The README documents commercial-license enquiries as a separate option; it does not itself grant alternative terms to this deployment. Evidence: README.md:445-447; LICENSE:210-216.

The license expressly permits running the unmodified program. The remote-interaction obligation below has its own modification condition; “a website exists” is not a substitute for reading that condition. Evidence: LICENSE:142-147,540-548.

Source identity and revision

The upstream repository is THU-MAIC/OpenMAIC. Its package name is openmaic and its application title is OpenMAIC. Evidence: README.md:83,474; package.json:2; app/layout.tsx:19-22.

The recorded source baseline for this showcase is 8c6c8f68eecf60a3472d12f1d0098e055c4cd5a6. The deployment’s source-review header records the matching abbreviated revision 8c6c8f6; retain the full baseline when preparing a source release. Evidence: deploy/nginx/maic.loca.zone.conf.

The Compose overlay selects the image tag maic-showcase:d088. A tag alone does not establish that an image contains the recorded commit: the overlay does not specify an immutable image digest or a source-archive URL. Treat exact built-image provenance as unknown from this configuration. Evidence: deploy/compose.yml.

Section 13: remote-user source offer

Section 13 applies if you modify the program and the modified version supports users interacting with it remotely through a computer network. That version must prominently offer those users an opportunity to receive the Corresponding Source of that version from a network server, at no charge, using a standard or customary means of copying software. Evidence: LICENSE:540-551.

The important words are “your version.” An upstream repository link is useful provenance, but does not by itself provide local modifications that are absent from upstream. Keep the offered source matched to the version users encounter. Evidence: LICENSE:542-548; LICENSE:122-140.

Corresponding Source includes the source needed to generate, install, run, and modify the work, including scripts controlling those activities. The definition contains exclusions for System Libraries and certain unmodified general-purpose tools; it is not simply “every file on the host.” Evidence: LICENSE:122-140.

For an operator, the conservative release practice is to publish the matching source and relevant nonsecret build/deployment material together, and make that offer easy for every remote user of a modified version to discover. This is an operational recommendation, not a conclusion that every external reverse-proxy setting is necessarily part of the covered work. Basis: LICENSE:122-140,542-548.

Notices and modifications

When conveying verbatim source copies, preserve appropriate copyright notices, license notices, applicable additional terms, and absence-of-warranty notices. Give recipients a copy of the license with the program. Evidence: LICENSE:185-191.

Modified source must carry prominent notices that it was modified and give a relevant date. It must also carry prominent license notices, and the whole covered work is subject to the terms described in section 5(c). Evidence: LICENSE:198-216.

Section 5(d) addresses Appropriate Legal Notices in interactive interfaces, with an explicit exception where the original interfaces did not display them. That exception must not be confused with section 13’s separate source-offer requirement for a modified network-interactive version. Evidence: LICENSE:91-98,218-221,542-548.

The README asks researchers to “please consider” citing OpenMAIC. Do not recast that research request as an additional mandatory deployment attribution term; preserve the actual license and copyright notices instead. Evidence: README.md:451-453; LICENSE:185-191.

Deployment overlay versus upstream

The following are configuration-level differences documented by the overlay, not a claim that application source has been patched or that the running service has been exercised. The upstream Compose file remains a separate input. Evidence: deploy/compose.yml; docker-compose.yml:1-15.

Area	Recorded overlay change	Evidence
Image selection	Uses a separately built image tag instead of an implicit Compose build.	deploy/compose.yml
Network exposure	Publishes the app port on loopback, with nginx as the public edge.	deploy/compose.yml; deploy/nginx/maic.loca.zone.conf
Data persistence	Uses a host bind mount for application data instead of the upstream named volume.	deploy/compose.yml; docker-compose.yml:8-15
Resource controls	Specifies memory/CPU limits, log rotation, and no-new-privileges.	deploy/compose.yml
Edge policy	Configures a whole-app HTTP Basic gate, request limits, and streaming proxy behavior.	deploy/nginx/maic.loca.zone.conf
Service lifecycle	Supplies a system service invoking the overlay’s Compose deployment.	deploy/maic.service
Provider setup	Supplies an example environment with empty LLM credential slots and no default model.	deploy/maic.env.example

These files document how the showcase is configured differently from upstream. They do not prove the absence of other source changes, the contents of the built image, or that the edge configuration is loaded in production. Evidence boundary: deploy/compose.yml; deploy/nginx/maic.loca.zone.conf.

Publish reusable templates and relevant build instructions, not live credential files. The supplied environment template explicitly distinguishes itself from the private runtime environment file and describes browser-supplied keys. Evidence: deploy/maic.env.example.

Current source-offer status

State	What this page can establish	Evidence
Configured	The source tree contains AGPLv3 and the README links it.	LICENSE:1-6; README.md:478-480
Configured	A deployment overlay and credential-free example environment exist.	deploy/compose.yml; deploy/maic.env.example
Not found	No in-app source-download link was found in the inspected UI; the home footer is plain project text.	app/page.tsx:687-690
Unknown	A matching deployed-source archive and a prominent remote-user offer are not established by the cited deployment files.	deploy/compose.yml; deploy/nginx/maic.loca.zone.conf
Blocked for sign-off	Do not sign off section 13 readiness for a modified deployment until its matching source and prominent offer are established.	LICENSE:542-548

The footer text “OpenMAIC Open Source Project” is not itself a download offer. The README’s license link and this wiki’s upstream link are documentation; neither proves that remote users can obtain the exact deployed modified version. Evidence: app/page.tsx:687-690; README.md:478-480; LICENSE:542-548.

“Unknown” is not an allegation that source is unavailable everywhere. It records the limit of the cited source/configuration evidence; this page claims neither live source-download verification nor human acceptance. Evidence scope: deploy/compose.yml; deploy/nginx/maic.loca.zone.conf.

Commercial licensing

Use the institutional project contact in the upstream README’s Commercial Licensing section for enquiries about alternative terms. The contact need not be duplicated here. A commercial deployment and a separately negotiated commercial license are not interchangeable concepts; preserve AGPL obligations unless alternative permission has actually been obtained and its scope established. Evidence: README.md:445-447; LICENSE:193-194,210-216.

Operator checklist

• Record the full upstream revision, local changes, and the release’s build inputs before publishing source; make the release match the served version. Basis: LICENSE:122-140,542-548; deploy/compose.yml.
• Include LICENSE, preserve copyright and no-warranty notices, and retain applicable license notices in conveyed source. Basis: LICENSE:185-191.
• Give modified source prominent modification notices and relevant dates; include the required license notices rather than silently replacing identity. Basis: LICENSE:202-216.
• Include the scripts and nonsecret configuration needed for the covered work to be generated, installed, run, and modified; document deployment differences. Basis: LICENSE:122-140; deploy/compose.yml; deploy/maic.service.
• Use the public environment example for configuration shape; keep private runtime credentials out of source archives and public documentation. Basis: deploy/maic.env.example.
• For a modified network-interactive version, provide a prominent, no-charge source offer accessible to all its remote users, not merely an operator note. Basis: LICENSE:542-548.
• Check the offered download against the actual release after every change; do not use an image tag as the only record of source provenance. Basis: LICENSE:542-548; deploy/compose.yml.
• Review interactive legal notices separately from the section 13 source offer, respecting the section 5(d) exception without treating it as a blanket waiver. Basis: LICENSE:91-98,218-221,542-548.

Return to the overview or read the quickstart.