The things people actually ask.
Including the awkward ones, which are the only ones worth a page.
Is this production-ready?
The enforcement path is heavily tested — see the numbers on the home page, which are generated from the suites rather than typed. What it has not had is a decade of other people's traffic. That is what the founding-partner term is for, and why it is free: you are taking the risk of being early and should not also be paying for it.
How many customers do you have?
We are selecting the first ten. There are no logos on this site because we have not been given any, and putting one there is the first thing a security buyer checks.
What happens if you disappear?
Your agents keep working. Records are signed with keys you hold, in published formats with cross-language vectors, and the verifier is a standalone binary that needs no account and no network — including no us. Self-host and the enforcement point is inside your own boundary already. This is the question we designed the format around, not one we prepared an answer for.
Can we self-host it?
Yes, and it is the recommended shape wherever the data plane cannot leave. Runs in your VPC, your KMS holds the keys, the traffic never reaches us. The hosted and self-hosted control planes are the same code.
Do you see our secrets?
No. Agents generate their own keypairs and prove possession, so there is no private key of yours here to leak. Provider credentials sit at the enforcement point — inside your boundary if you self-host, sealed under your KMS if not — and are never handed to an agent. A vault hands the key over and hopes; this never hands it over.
What does it cost?
The gate, the four outcomes and the free tools are free forever — charging for enforcement means charging people to be safe, and they turn it off. The evidence is what you buy. There is no published per-seat number during the partner term because we have not tested one against a real deployment, and quoting it now would be a number we had to retract.
Do you have SOC 2?
Type I is in progress and not yet attested; we will not imply otherwise. Until it lands, the security page states properties rather than certificates, and each one has a test behind it.
Why not just use Okta, or a vault, or our framework's own auth?
Each was built for a different actor. An identity provider governs people at login; a vault governs who may read a key; a framework orchestrates and trusts everything in-process. An agent acts as a chain — human → agent → sub-agent → action — and the question 'may this actor do this, right now, and who is accountable' is one nobody in that list owns.
Design partners
Bring one agent.
Design partners get the gate, the signed evidence and a direct line to the people building it. One field — we will not make you fill in a form to find out what this costs.
Request access
One email. Leave in one click. We never sell it.