Security

The things that would be embarrassing to get wrong.

Stated as properties, because a security page that lists certifications instead of properties is telling you which audit it passed, not what it does.

✓
We never see a private key

Agents generate their own. Proof-of-possession, so a breach of us cannot impersonate your fleet.

✓
Budget is enforced inside the write

UPDATE … WHERE used + n ≤ limit. Ten concurrent calls against one budget cannot jointly overshoot it, and there is a test that runs them.

✓
A sub-mandate cannot outlive its parent

Checked at issuance. Revoking a parent cascades.

✓
The issuing key never ships in an agent

Two SDK objects: AgentControl can issue, AgentRuntime can only ask. An agent that could issue its own mandate would not be governed by one.

✓
Approval is non-repudiable

Ed25519 over canonical JSON, naming a person. Stripping the approver's signature while keeping verified:true fails — there is a test that tries exactly that.

✓
Tenants cannot see each other

The same agent_ref in two tenants is two different agents. Quoting one tenant's id from another authorizes nothing.

Certification status

SOC 2 Type I: in progress. Not yet attested, and we will not imply otherwise — it is the first thing a buyer verifies. Until it lands, what you can check yourself is on this page: every property above is a property, not a certificate, and each one has a test behind it.

Compliance packs state what they do not cover, in the pack itself. A record signed by the agent that produced it says witness: self, because self-attested and independently countersigned are different things and a format that let them look alike would be doing its readers real harm.

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.

One field. One click to leave. Never sold.