Subject-agnostic enrolment
One enrolment flow covers people, machines, workloads and agents. Subject type is a label, not a separate product.
Post-quantum identities for every subject you operate.
Trust Kernel issues a cryptographic identity for any subject — an employee, a device, a service account or an AI agent — using ML-KEM-1024 key encapsulation with rotating key material. Each identity carries a stable hash you can reference from your own systems, and can be deactivated the moment a subject is decommissioned.
Built for: Platform and security engineering teams replacing shared secrets and static API tokens.
One enrolment flow covers people, machines, workloads and agents. Subject type is a label, not a separate product.
Keys rotate on a schedule you set. Older material stays verifiable so historical proofs never break.
Deactivating an identity invalidates future proofs immediately and marks the evidence trail accordingly.
Reference identities from your own database with a stable hash instead of copying key material around.
This runs the real logic on our servers — no account, no canned responses. Demo runs are not stored and use a published demo signing key; your tenant uses rotating ML-KEM-1024 material.
Enrol any subject — a person, a device, a workload or an agent. The identity hash is computed with SHA-256 over the canonical subject record, exactly as the platform does it.
Trust Kernel is step one of the platform. Every proof, agent policy, graph node and evidence entry points back to an identity issued here, so this is where an integration normally begins.
See the four-step platform flow →Trust Kernel is included from the Starter plan at $49 / month, with every higher plan including it too. Verification is never charged per check — plans differ on volume, retention, autonomy and governance.