Licensing
What's free, what's licensed, and why the terms hold.
The app suite and the specifications are open source under Apache 2.0, free to use and to run yourself, with community support or a paid support agreement. The enforcement hardware is licensed under published FRAND terms. And the whole regime is held by an independent Foundation no single owner, including Triodian, controls.
The app suite
Open source, with support if you want it.
The app suite (the Obligations Atlas, Board Direction, Risk Appetite, Use Assessment and Confidentiality Exposure), its installer and the Metamodel are open source under the Apache License 2.0. Anyone may use, change and run them, including in their own environment, without paying Triodian.
| What | Terms |
|---|---|
| The code: the five apps, the installer, the practice hub and the Metamodel | Apache License 2.0. Use, change, run and share it, commercially or not; free to self-host. Each app’s page links its repository on GitHub. |
| The framework text and the Atlas records | Apache License 2.0 as well. The laws, standards and guidance an Atlas record cites keep their own terms. |
| The Triodian name and logo | Trademarks of Triodian Pty Ltd, which the Apache License does not grant (section 6). You may say a version is built on the Triodian app suite; a changed version carries its own name and is not presented as Triodian’s. |
Ask in the open.
Ask questions and report problems in the issues on each app’s GitHub repository, and in the Obligations Atlas discussions. The people who build the apps read them, and so do others who run them. Answers are best effort, with no response time. Report security problems privately, from the Security tab of the repository.
The repositories →For organisations that run the suite themselves.
A support agreement covers help to install, configure and upgrade the suite in your environment, answers from the people who build the apps within agreed response times, and notice of security fixes and new versions. Its terms and fee are agreed with you.
Ask about a support agreement →What Triodian charges for
- Engagements: we run the method in the suite with your counsel and board, with the independent check. Fees are published.
- Standing support: our people beside yours between engagements, by the quarter.
- Support agreements: for the suite you run yourself, as above.
- Deployments: we run the suite for you, or for a practitioner’s clients; see Partners.
A summary only: the LICENSE and NOTICE files in each repository govern. Funding the project is kept apart from paid services; see Support the project. The apps record facts and the positions people take; they are not legal advice.
The map
Three lanes: what's open, what's licensed, and how you'd extend it.
The app suite and its installer (Apache 2.0) · UGP specifications, conformance suites and SDKs (Apache 2.0) · the Metamodel (Apache 2.0) · the content-provenance open dedication, C2PA / Content Credentials, CAWG, open consent registries, irrevocably royalty-free.
Understanding, teaching and studying never require a licence.
Explore the open protocol →The DGA claim set under FRAND. Software conformance is free; the cryptographic attestation regulators and procurement accept comes only from licensed hardware. The compliance token is the boundary object.
The appliance →Further implementations, including deployments where model, tools and actuators share a chassis, and the constraint-authoring methodology are licensed separately; see the platform. Ask us for either.
The regime in five commitments
Headline level, the detail lives in the SEP page.
Published rates
Identical across the pool.
Anti-accumulation ceiling
On aggregate exposure, royalty stacking structurally impossible.
Small-entity exemption
Thresholds in the prospectus.
Annual transparency mandate
Agreements, allocations and distributions published yearly.
The open dedication
Content-provenance, irrevocable and royalty-free.
Why the terms hold
The IP will be custodied by the independent Casuarina Foundation, a charity being established with ACNC registration underway. The anti-acquisition provision, never exclusively transferable to a single private entity, is stated as the licensee's protection.
"The party that would benefit from tightening the terms does not control them."
How we're structured →How to engage
Three steps.
Request the prospectus
Evaluation licence
Pool admission
Existing product-tier customers are pre-qualified. A deployment contract and a licence are different instruments, the prospectus says which questions belong to which.
The honest boundary
A licence conveys rights to the claim set, not validation status. Mode A capabilities inherit the validation gate regardless of who holds a licence, and no licence constitutes a compliance endorsement of a licensee's product. Conformance questions belong to the UGP test suites; assurance questions to the product tier.
The transparency mandate is Rule 3 applied to the licensor itself, terms verifiable by parties who do not need our account of them to be true. The eight rules →
Three layers of rights
What an insurance partner would be licensing.
The protocol is open, the hardware is FRAND, and only a third, separate layer, insurance commercialisation, can be competitively allocated. Because that layer is not a patent licence, exclusivity can attach there and nowhere else without ever colliding with the FRAND commitment.
Any exclusivity is narrow, time-limited, and conditional on agreed validation, product-development and market commitments; the same structure that gives a partner counterparty durability keeps every position narrow. Arm licenses cores · Bluetooth certifies radios · HDMI licenses content protection, open spec drives adoption; a proprietary component anchors trust and value.
Commercial logic for discussion, to be confirmed with IP counsel against the Master Licence Agreement and Foundation deed.