# Commercial licensing > **Commercial agreement required.** Any organisation must sign a commercial > agreement with Orchestrum Technologies LLP before using, evaluating, > self-hosting or deploying the Grantex platform, or using the hosted service > commercially. Use without one is not licensed under the > [Orchestrum Personal Use License 1.0](LICENSE) and infringes Orchestrum's > copyright; your rights under the licence end under its section 5 > (Termination). Individuals' own personal use is free, and the SDKs are > Apache-2.0. Contact [sanjeev@orchestrum.in](mailto:sanjeev@orchestrum.in). Grantex is owned by Orchestrum Technologies LLP and has two licences: | Part | Licence | Use by an organisation | |---|---|---| | SDKs and client packages in `packages/`, and `examples/` | Apache License 2.0, open source | Free for any use, including commercial | | The Grantex platform: the server and portal (`apps/`), the protocol specification text, documentation and website | [Orchestrum Personal Use License 1.0](LICENSE), from **21 October 2026**, including every update | Needs prior written permission from Orchestrum Technologies LLP in a signed agreement | [LICENSING.md](LICENSING.md) lists the directories exactly. For the platform, **only an individual using it for their own personal purposes is free. Every organisation needs Orchestrum's prior written permission in a signed agreement with Orchestrum Technologies LLP, whatever the use and whether it is paid or free.** Commercial use of the hosted services needs an agreement too. This page explains in plain language what that means. The licence texts and any signed agreement are what govern; this page is not legal advice. ## Free, no agreement needed - **The SDKs and client packages**, for any purpose, under the Apache License 2.0: build them into commercial products, run them in production and redistribute them, keeping their licence and notices. - **Personal use of the platform.** An individual using, copying and changing the server, portal, specification text or documentation for their own personal purposes, such as learning, personal study, experiments and hobby projects, and not acting for, on behalf of or for the benefit of any organisation. - **Contributing** changes back to this repository as an individual (see [CONTRIBUTING.md](CONTRIBUTING.md)). Personal use does not include distributing the platform. Sharing a copy of the platform, changed or not, needs a written agreement with Orchestrum, and every copy you keep must include the licence and the copyright notice in [LICENSE](LICENSE). ## Needs prior written permission from Orchestrum Any use of the platform by or for an organisation, and any use that is not an individual's personal use. "Organisation" means any company, partnership, LLP, firm, sole proprietorship carrying on a business, charity, non-profit, school, university, research institution, government body or other organisation. There is no exception for evaluation, charities, education, research or government, and it makes no difference whether the use is commercial, internal or free of charge to others. This includes: - **Evaluation, testing and pilots**: trying the auth service or portal for an organisation, including proofs of concept and test deployments. - **Internal use**: running the platform for an organisation's own staff, products, customers or operations, even if nothing is sold. - **Hosting, SaaS and managed services**: offering the Grantex server, or a service based on it, to other people or organisations, on your infrastructure or anyone else's. - **Resale, sublicensing and distribution**: selling, licensing, bundling or redistributing the server, the portal or a changed version of them. - **Embedding**: including the auth service, the portal or the protocol specification text in another product, appliance or platform. - **Consulting and services**: delivering consulting, integration, implementation, training or support work that runs or deploys the server or portal, paid or unpaid. - **The hosted services**: commercial use of `grantex.dev`, `api.grantex.dev` and related endpoints, whichever SDK or version you use to call them. If you are not sure whether your use is personal use, treat it as needing permission until Orchestrum confirms otherwise in writing. ## How to obtain permission Email [sanjeev@orchestrum.in](mailto:sanjeev@orchestrum.in) with: 1. your organisation's name and country; 2. the Grantex components and versions you want to use; 3. how you will use them (evaluation, internal, hosted, embedded, resale or services) and who your users are; 4. the expected scale and deployment (self-hosted, cloud, devices); and 5. when you need to start. Orchestrum will reply with terms. Use may begin only once a written agreement has been signed by Orchestrum Technologies LLP and you. Sending a request, or receiving a reply, is not itself permission. ## Earlier versions and existing users Releases published before 21 October 2026 remain available under the terms they were released with. Those terms do not extend to any version, update, fix or security patch of the platform published on or after 21 October 2026. If an organisation uses the Grantex server or portal today, moving to any later version requires a written agreement with Orchestrum. The SDKs and client packages are not affected: they remain Apache-2.0. No version of the Apache License 2.0 grants rights in the Grantex or AgenticOrg names and logos or access to Orchestrum's hosted services, so commercial use of those needs Orchestrum's prior written approval as described in [TRADEMARKS.md](TRADEMARKS.md). ## Material that keeps its own licence Third-party material in this repository keeps the licence it came with and is listed in [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md): for example the RFC 8785 test vectors, the copied UCP and ACP JSON Schemas, the IETF Internet-Draft texts, and all dependencies installed by package managers. ## Contact Orchestrum Technologies LLP, [sanjeev@orchestrum.in](mailto:sanjeev@orchestrum.in).