Deployment Architecture
Runs on Hedera (testnet or mainnet), self-hostable, with configurable, sovereign HCS topics.
What it does
The Deployment Architecture runs on Hedera — testnet or mainnet — and is self-hostable, with configurable, sovereign HCS topics so an organisation can own its own registries and evidence anchors. Deploy in the cloud, on-premise, or federated across parties, wherever the data and regulation require.
Inside Deployment Architecture
The core functions this engine provides across the Trust Fabric.
Deployment Architecture composes with the Trust Fabric
Every engine is independently useful and interoperates through one API-first Trust Fabric — so identity, evidence, policy, risk and certification stay consistent across your AI estate.
Related engines
Trust Fabric
The substrate that links identity, policy, evidence and the trust index into one consistent, on-chain view.
- Deterministic policy-core
- Identity (DIDs)
- Signed evidence on Hedera
- The Trust Index
Identity Engine
Issues each agent a verifiable, self-certifying DID and proves control of its key — the root every other engine trusts.
- did:hedera / did:key
- Key proof (verify-key / BYOK)
- Public DID resolver
- HCS registry anchoring
Ownership & Delegation
Binds an agent to its owner and to a VC-issued mandate — with instant revocation.
- Verified principal (KYC/KYB), or a disclosed free-tier allowance
- VC-issued mandate (scope, caps, merchants)
- Resource scope — which systems and data
- Sub-delegation that can only narrow
- Delegated issuance
See Deployment Architecture in action
Book a demo and see how the platform establishes trust across your AI systems.