Vertirite exists because deploying AI on regulated infrastructure requires a layer your existing PAM, SIEM, and OPA stack cannot give you: classification of intent, mode authority, and an append-only audit trail your auditors can sign.
The mode that decides whether an AI action runs is set OUTSIDE the AI's reach. A compromised model, a prompt-injected agent, or a runaway script cannot escalate itself out of LOCKDOWN. The mode authority is a separate process with a separate trust boundary.
An AI agent gains a new capability the same way a junior engineer gains a new permission: by a pull-request to a reviewed YAML manifest. Adding a capability is never a runtime toggle. The audit log records the merge SHA next to every action that capability authorizes.
Every audit row is signed with a per-tenant key chain. A row cannot be removed without breaking the chain. Auditors can reconstruct the exact sequence of actions on any tenant in any time window — and verify the sequence was not tampered with.
If the Vertirite broker becomes unreachable, every protected system fails CLOSED — automated callers cannot act. The AI does not get to keep going on stale state during an incident. This is the opposite of every consumer AI tool's default.
On Enterprise (self-host), customer data never leaves customer infrastructure. On hosted tiers, encryption-at-rest uses your KMS keys; we hold the data path, you hold the key path. Revocation is one API call away.
Every posture above marked 'in-flight' or 'roadmap' is plainly labeled — not buried in fine print. We will not claim a control we have not implemented. If a buyer needs something not on this list, we'll tell you in the demo, not after the contract.
What's operational today. What's in flight. What's roadmap. We will not claim a control we have not implemented.
A protected system runs surge-agentd, a small daemon that proxies every privileged action through Vertirite. The daemon authenticates with mTLS to the broker; the broker checks the action against the capability registry, the mode authority, and any active approval rules. Approved actions execute. Denied actions return a structured error with the audit row id. Every step appends to the audit log. The AI agent invoking the action has no access to the audit log, the capability registry, or the mode authority — those are out-of-band. The customer’s mode authority lives in their own process; we hold the policy contract, they hold the kill switch.
For a deeper architecture walkthrough, request the technical docs. For a 30-minute demo on your screen, see Theatre.
Email [email protected] with your company + tier interest. We respond within one business day during US business hours.
Email [email protected]