User guide
You’ve seen what TrustPlane Auth does; this guide explains how it works and how to run it. Use it when you’re designing an integration, planning a rollout, or operating an adapter in front of real traffic.
Architecture
Section titled “Architecture”How the runtime fits together: the components, the verification flow, and the small set of versioned contracts (passport, transcript, signer taxonomy, bundle, audit event) that everything else depends on. Also covers the adoption path from a standalone Auth deployment to fleet management with TrustPlane Control.
Start at Architecture overview.
Capabilities
Section titled “Capabilities”Every capability TrustPlane Auth ships today, one page each: passports, transcript-v1 request binding, replay protection, bundle policy and freshness, signed bundle lifecycle, trust anchors, the brownfield adapter, broker-attested workloads, and audit events.
Start at Capabilities.
Deployment
Section titled “Deployment”How to put the adapter in front of an existing API: the provider-neutral deployment model, gateway and ingress integration patterns, the Helm chart, an end-to-end example deployment, Control-signed bundle files, and refreshing bundles without rebuilding infrastructure.
Start at Deployment overview.
Operations
Section titled “Operations”Proving the runtime behaves correctly and managing route policy at scale: the deterministic acceptance gate that defines “healthy”, and route policy maps that let one adapter protect many routes with per-route source rules.
Start at The acceptance gate.