AGPL-3.0, in plain words.

The core — engine, reflex gate, manifests, workflows, A2A, the sidecar contract, the CLI, the console, observability — is licensed AGPL-3.0, an OSI-approved open-source license. In practice:

• Self-host, forever, for anything — internal tools, client work, production fleets. No seat counts, no usage telemetry, no feature gates.
• Modify it — the source is yours to read, fork, and adapt.
• Share it — redistribution comes with source obligations, the standard copyleft deal.
• The network clause — if you run a modified version as a service others use, AGPL-3.0 requires you to offer those users the modified source. That clause is the point: the engine cannot be quietly closed into a competing hosted product.

The engine’s NOTICE announces a commercial line that will ship separately under a commercial license: SAML/SSO, user teams, analytics, evals, and multi-project tasks — plug-ins through documented extension points, not a hostage feature inside the AGPL core. The boundary is structural, not a promise about what might get carved out later: governance stays in the open core, because governance is the product.

Until that offer exists, everything is the AGPL core, and the publisher block on the Legal page stays “personal, non-commercial” — it will change when the offer is real, and this page will say so first.

Contributions are welcome and require the project’s Contributor License Agreement (docs/cla.md in the repository, published with the source). It grants the maintainer the rights needed to keep the open-core / commercial-boundary split clean — including the ability to license the announced commercial line — while the AGPL guarantees the core itself stays open whatever happens to the project or the company that might one day exist around it.

One maintainer, one bus factor: the CLA is the paperwork that lets the project’s future survive its present.