Beta waitlist — not a public launch, and no live checkout. Request early access
Trust & controls

We claim only what we can show.

Most AI products describe their safety. We'd rather show you the control board — what we do on our own operations today, and what's still being built. Nothing here is certified. Every control runs on our own operations before a customer ever touches it.

ControlStatusWhat it means in practice
Human approval gates ◐ In progress Privileged agent actions — credentials, spend, production and DNS changes — pause for an explicit human "approved, go." How we run our own infrastructure today: DNS, spend and production changes wait for a named person's yes. Enforcing that inside the product is still being built.
Least-privilege credentials ◐ In progress The goal is that agents hold narrowly scoped, deny-guarded credentials — for example, a DNS token that can touch only the zones it manages. We are narrowing our own agents' cloud roles toward that. The work is not finished.
Append-only audit trail ◐ In progress Still being designed. The approval-record schema — who approved what, when, under which policy — is the next piece, and it comes before the platform opens to customers.
Tenant isolation ◐ In progress Login and API routes on our company desk are bound to the tenant by the Host header, and that is tested on our own tenant, Vetworx (tenant zero). Separation between two different customer tenants is not yet proven, and we do not offer multi-tenant service.
Per-customer compliance profiles ○ Planned A control set that flexes by configuration: a full set, or a solo site owner's minimal one. Same platform, your profile. Not built yet.

Your identity, your call

Guardrails only mean something if they're anchored to an identity system you trust. These are the options we are building toward. None is open to customers yet.

Bring your own

Active Directory / Entra

You will be able to verify approvals and permissions against your existing directory. Your users, your groups, your conditional access — the plan is to integrate, not replace.

Bring your own

AWS infrastructure

You will be able to anchor the permission envelope in your own IAM — roles you define, deny rails you can read, credentials that stay under your account's control.

Fully managed

We run the envelope

No directory? We plan to operate the guardrails and permission sets for the tasks being done, documented and auditable. Not available yet; public checkout is not open.

Why the board looks like this

An honest "in progress" beats a decorative "certified." Buyers who've been burned know the difference.

We run ourselves as tenant zero. The gates, credentials, and audit design on this board are built on the agents that help operate our own infrastructure first.

By the time a control reaches a customer, it has been used on our own operations — not written for a brochure. When a planned control lands, its row moves, and the evidence moves with it.

Ask us the hard questions.

Compliance requirements, identity constraints, an auditor with opinions — bring them. That conversation is the product working as intended.

Request early access Or email us