LoopX uses the Apache License 2.0 as the primary license for its unified open
source core beginning with v0.4.8. The complete current license is in
LICENSE, and the
attribution notices distributed with the project are in
NOTICE.
- Releases and tags through
v0.4.7remain permanently available under the MIT License that governed those releases. - Beginning with
v0.4.8, the unified LoopX open source core is distributed under Apache-2.0. - The previous MIT license text and its copyright notice are preserved
verbatim in
LICENSE-MIT. They continue to document and govern the rights already granted for historical MIT releases and portions first distributed under those terms.
Changing the license of a current distribution does not revoke or narrow the permissions already granted for an earlier release. Users may continue to use an older LoopX release under its original MIT terms.
Apache-2.0 keeps the core permissive for commercial and non-commercial use while adding an explicit patent-license framework for covered contributions. That clearer framework is useful when model providers, infrastructure teams, and large enterprises adopt or contribute to LoopX as shared long-horizon agent infrastructure. The change is intended to make ecosystem collaboration easier, not to restrict commercial use.
The transition does not manufacture a retroactive Apache patent grant from people who contributed solely under MIT terms. The patent-governance value of Apache-2.0 accumulates primarily through code distributed in the new release line and through future contributions submitted under the Apache-2.0 and DCO terms. Historical copyright and attribution records remain intact.
Unless a contributor explicitly states otherwise before submission, future
contributions accepted into LoopX are submitted under Apache-2.0, as described
by section 5 of that license. Each commit in a pull request must also carry a
Developer Certificate of Origin 1.1 sign-off. See
CONTRIBUTING.md
and DCO for the exact
workflow and certification.
No contributor license agreement or copyright assignment is introduced by this transition. Copyright remains with contributors for their respective contributions.
This repository's unified open source core is Apache-2.0. A separately delivered Managed Control Plane, enterprise-only modules, hosted operations, or implementation and support services may use separate commercial terms when they are not part of this repository's Apache-2.0 core distribution.
Apache-2.0 itself permits commercial use, modification, and distribution
subject to its terms. The separate project-name and logo guidance in
TRADEMARKS.md
still applies; the software license does not create endorsement or trademark
rights.
This document explains the project's public licensing policy and is not legal advice.