On-Device Licensing · Triodian
← Licensing overview The on-device / self-hosted claim family.

Licensing · On-device

Licensable IP · local-device topology Mode B licenses now · Mode A lanes validating-gated

On a personal device there is no API boundary. The governance has to live on the chassis.

The claim family for governed on-device AI actuation, the gate between model output and local tool execution, the attested constraint store on the device, and token-gated local actuation, licensable at the OS, runtime, or silicon layer.

Talk to us about a platform evaluation licence The topology ↓

The topology difference

Cloud has a boundary. A device does not.

Cloud

Model | API boundary | World

Device

Model + Tools + Actuators one chassis · no boundary

Cloud governance assumes an API boundary between model and world. On a personal device or edge SoC there is none, and the party the governance protects is the device owner, not a remote operator.

Integration patterns per licensee class

Three layers to license at.

Agent / MCP runtimes

Gating tool invocation at the runtime that mediates local actions.

OS & endpoint-security vendors

Offering governed-AI as a platform capability of the operating system.

SoC vendors

Implementing the interlock in silicon at the edge.

Alongside, not against

Platform vendors' own guardrails are administered by the vendor, the rule-maker and the rule-taker in one company, the exact collapse The Missing Layer names.

This is enforcement the device owner's declared policy controls, verifiable without trusting the platform.

The Missing Layer →

The honest boundary

Mode B capabilities license and integrate now; Mode A lanes inherit the validation gate. FRAND terms and Foundation custody are the shared regime, see the licensing hub; they are not restated here.

Talk to us about a platform evaluation licence.

Talk to us →
Licensing Overview (hub) SEP Licensing Semantic Enforcement Appliance Bounded Command Governance The Missing Layer