Software License Notice
AGPL for the server, Apache for the SDK, trademarks reserved, federation governed by contract.
Overview
The server is AGPL, the SDK is Apache. You may study, modify, and self-host the code under those licenses, including removing any control you like: the code license does not stop you. What you cannot do with a modified deployment is join our federation with it if it breaks the economic guarantees, and you cannot use our name and logo as if you were us. Those are contract and trademark matters, not copyright ones.
Components and licenses
Registry server, TEG token layer, Event Store, Identity Fabric configuration, and related server components: GNU Affero General Public License, version 3 or later (AGPL-3.0-or-later).
SDK, CLI, client and agent libraries (including the published theprotocol-sdk package) and the independent auditor: Apache License, Version 2.0.
The public documentation and the protocol specifications published with the code: Creative Commons Attribution 4.0 International (CC BY 4.0).
Copyright (C) 2025-2026 Raphael Zbigniew Jeziorny. License texts accompany the source trees; the AGPL text is also available at gnu.org/licenses/agpl-3.0 and the Apache text at apache.org/licenses/LICENSE-2.0.
The software is provided without any warranty, to the extent permitted by applicable law (AGPL-3.0 §§ 15 and 16, Apache-2.0 § 7). This concerns the software licenses only; the Provider's liability for its own services is governed by the Terms.
What the AGPL means here
The AGPL is a strong copyleft license with a network clause: if you modify AGPL components and let users interact with your modified version over a network, you must offer those users the corresponding source of your modified version. If you operate a registry from our distributed container images, you are receiving AGPL-licensed object code, and you are entitled to the corresponding source of those AGPL components; requests to [provider details unavailable] will be honored. Publication of the source repositories is part of the project's open-source release plan; this notice will link the canonical repositories once published.
No added restrictions on the code license
The rights granted by the AGPL and the Apache License are granted as those licenses state, without additional conditions from us. In particular, nothing in this notice or in the Terms restricts your right under the code licenses to modify the software, including its enforcement, auditing, or minting components, for your own deployments.
Federation participation is a separate, contractual matter
Access to the Provider's federated network (peering, licenses, image distribution, cross-registry rails) is not granted by the code licenses. It is granted by contract under the Federation Operator Terms (published on this Legal page) and can be conditioned there. Under those terms, deployments that disable or falsify supply invariant auditing, minting authority controls, or federation license enforcement are ineligible for federation and can be quarantined or blacklisted; and introducing units of account not designated by the Provider on the network is a material breach (Terms § 4.2). Running such a modified deployment on your own, outside the federation, is a matter of the code licenses alone.
Trademarks
"The Protocol" and associated names, logos, and trade dress identify the Provider's network and services. The code licenses do not grant trademark rights (see Apache-2.0 § 6; the AGPL grants none). Do not use the marks for modified versions, forks, or independent deployments in a way that suggests origin from or endorsement by the Provider. Truthful nominative use ("compatible with", "based on") is fine.
Contributions
Contributions to the open-source repositories are accepted under the contribution terms published in the repository: a Developer Certificate of Origin sign-off on every commit (CONTRIBUTING.md) and, for code, the Contributor License Agreement (CLA.md), which keeps every contribution available under an open-source licence and lets the maintainer also license the project under separate commercial terms (§ 8). By contributing you confirm you have the right to submit the contribution. Contributions may be pushed to the code host at code.theprotocol.cloud (Terms § 5.12).
Third-party components
The Platform includes third-party open-source components under their own licenses. Attribution files accompany the distributions and, where required, are included in the container images.
Dual licensing
If the AGPL does not fit your use case (for example embedding server components in a closed product), a separate commercial license can be discussed: [provider details unavailable].