Flux package licensing boundary
Status: accepted under O-002 at independent review 5330686985, 27 September 2026. This document does not change the license of an existing file.
The repository currently has an AGPL-3.0 license. Keep the Flux application in app/apps/web, app/apps/server, app/apps/worker, app/packages/core, app/packages/db and app/packages/agent-runtime under AGPL-3.0. Use Apache-2.0 for independently usable app/packages/contracts, app/packages/sdk and app/examples/external-agent, with each package’s own license, SPDX metadata and notices. Their source must avoid imports from AGPL-only application modules so external developers can implement an agent in Python or another frontend against the documented HTTP API. No closed enterprise edition is proposed; possible paid services are hosting, deployments, migrations, maintenance and enterprise support, subject to a later business decision. A paid hosting service would keep the F-022 agent runtime (FLUX_AGENT_RUNTIME) off: Anthropic’s Commercial Terms would bind its operator, and OpenAI sends a paid or remotely hosted app to its interest form.
The Apache Software Foundation’s compatibility explanation and the GNU license list support Apache-2.0 code being included in GPLv3-family works in that direction; they do not establish that AGPL application code may be copied into an Apache-only SDK. The first package PR must identify ownership of new files, add package-level license texts and notices, and check the dependency tree before distribution. Treat legal interpretation and third-party terms as a release review item. Keep the existing root license and product direction intact until the accepted package boundary is implemented.