Licence

Grantex SDKs are open source under Apache-2.0. The Grantex server, portal and docs are under the Orchestrum Personal Use License 1.0: free for individuals’ personal use; organisations need written permission.

Summary

Grantex has two licences.

Part	Licence	Use by an organisation
SDKs and client packages in packages/ (TypeScript, Python and Go SDKs, framework integrations, verifiers, MCP, x402 and MPP packages, CLI, Terraform provider and the rest) and the examples	Apache License 2.0, open source	Free for any use, including commercial
The Grantex platform: the server and developer portal (apps/), the protocol specification text, this documentation and the website	Orchestrum Personal Use License 1.0, source-available, from 21 October 2026 including all updates	Needs prior written permission from Orchestrum Technologies LLP in a signed agreement

The licensor for both is Orchestrum Technologies LLP. LICENSING.md lists the directories exactly.

Server, portal and hosted services

Use	Needs written permission?
An individual’s own personal use: learning, personal study, experiments, hobby projects, not acting for any organisation	No
Any use by or for an organisation (company, partnership, LLP, firm, sole proprietor’s business, charity, non-profit, school, university, research institution or government body)	Yes
Evaluation, testing, pilots and proofs of concept for an organisation	Yes
Internal use by an organisation, even if nothing is sold	Yes
Hosting, SaaS or a managed service offered to others	Yes
Resale, sublicensing, bundling or redistribution of the server or portal	Yes
Embedding the server, portal or specification text in another product	Yes
Consulting, integration or other services that run or deploy the server	Yes
Commercial use of the hosted services (grantex.dev APIs)	Yes

Only an individual using the platform for their own personal purposes is free. Every organisation needs prior written permission from Orchestrum Technologies LLP in a signed agreement, whether the use is paid or free. There is no exception for evaluation, charities, education, research or government. Write to [e-mail], or see commercial licensing for what to include and how an agreement is put in place.

SDKs and client packages

The SDKs and client packages stay open source under the Apache License 2.0. You can use them in commercial products, run them in production and redistribute them, keeping their licence and notices. Calling the hosted services commercially is a separate matter covered above.

Existing users and earlier releases

Releases published before 21 October 2026 remain available under the terms they were released with. Versions, updates, fixes and security patches of the platform published from that date are covered by the Orchestrum Personal Use License 1.0, so an organisation needs written permission to use them, whether or not it used an earlier release before.

Names, logos and brand

“Grantex” and “AgenticOrg” and their logos are trademarks of Orchestrum Technologies LLP. Commercial use of the names, logos, hosted services or brand needs Orchestrum’s prior written approval, including with the Apache-licensed SDKs and earlier versions. See TRADEMARKS.md.

Copies and sharing

Keep the licence and the copyright notice with every copy of the platform you make, including changed copies, and do not remove or alter any licensing, copyright or trademark notice. Distributing the platform, changed or not, is allowed only under a written agreement with Orchestrum Technologies LLP.

Material under other licences

Third-party material keeps its own licence: dependencies installed by package managers, the RFC 8785 test vectors, the copied UCP and ACP JSON Schemas and the IETF Internet-Draft texts. See THIRD_PARTY_NOTICES.md.

Contributions

Contributors agree to the contribution licence in CONTRIBUTING.md, which lets Orchestrum Technologies LLP distribute contributions under these licences and license them to organisations.

The licence texts and any signed agreement govern; this page is a plain-language summary, not legal advice.