Don’t trust the agent. Audit it.
Not a badge we print — the structure of the platform. Every action recorded and replayable, every smith sealed off, your data in Europe and yours to take. Below is exactly how each one works.
What “on the record” actually buys you.
Four structural promises — each one something you can check for yourself, not a claim you take on faith.
Every action on the record
Each run is a persisted, replayable sequence of steps — every model call, tool invocation, approval, and euro. Open one weeks later and see exactly what happened, and what it cost.
run.started → tool.executing → approval.required → run.completedSealed per smith
Each smith holds its own memory, tool connections, and history. One user's data structurally cannot surface in another's — the scoped token carries the tenant boundary on every request.
scope: smith · per-project isolationEuropean by architecture
Agent state lives in European infrastructure. Residency isn't a setting we toggle — it's where the platform runs. Pair it with the trace and you can prove, action by action, exactly what touched your data.
built & hosted in the EUYour data, yours to take
Read it through the same API you write it with, export it, or delete it. There's no proprietary store you can't get back out of.
GET /v1/... · export · deleteInfrastructure you can leave.
The best reason to trust a young company with production is that you’re never trapped by it. So we make leaving easy on purpose.
- Standards in
OpenAI-compatible API, MCP for tools. The integration is one you already know.
- Your data out
Full export through the same API, anytime. No proprietary format holding it hostage.
- No rewrite to go
Because the surface is standard, switching off us doesn't mean rebuilding from zero.
We document what ships.
Overselling is the fastest way to lose a trust argument. So here’s the plain version.
- Webhooks are one signed attempt today
We deliver each lifecycle event once, signed for you to verify. There's no automatic retry yet — so the append-only events feed, not the webhook, is the durable source of truth. Poll it to reconcile.
- Certifications we haven't earned, we don't claim
Ask where we are on SOC 2 or ISO 27001 and you'll get the honest answer, not a logo wall. What we can show you today is the architecture above and the docs below.
- If it reads as aspirational, it isn't here yet
The docs describe behaviour that ships. When something is on the roadmap, we say roadmap.
Put it in front of your customers.
Give your users the data guarantees they're already asking you for — and the receipts to back them up.