PROVABLE AI GOVERNANCE
Source code, customer records, production credentials — leaving every day through browsers and coding agents.
no account needed to verify · no deck on the call
BUILT FOR SECURITY AND PLATFORM TEAMS
why nothing has caught this yet
The gateway inspects on the device, before encryption; the extension reads the prompt in the page and has Vloex check it before it is sent.
what it governs
Sends prompts to Vloex to be checked before they reach ChatGPT, Claude, Gemini or Perplexity. Redact, warn or block, with the reason shown to the person typing. If the check is late or fails, the prompt goes through.
A gateway between Claude Code, Cursor and the MCP servers they launch; Codex hooks are built but not yet run against a live Codex. One command routes the clients already configured on the machine through it. A blocked call returns a readable reason, not a silent failure.
Read-only OAuth into Google Workspace or Microsoft 365 lists the AI apps Vloex recognises among those your staff authorized, with nothing installed anywhere. It is the place to start.


and when someone asks what happened
The coding-agent gateway signs every event it can on the device; the browser extension does not sign yet, so its events are recorded as unsigned rather than counted as proven. Signatures fold into one root per day, each sealed to the day before, published as a signed checkpoint whose key resolves from a public JWKS. Your auditor re-derives all of it offline.
eight signed events shown · alter any one and every hash above it changes
Click any row to change what it says, the way a vendor could.
Every row folds into the fingerprint beneath it. Change one and the seal breaks — the same check an auditor runs, computed here in your browser with nothing leaving the page.
Altering a record from six weeks ago means re-signing every day since — and the day after that, and the day after that.


Want to see this running against your own AI traffic?
By default, deterministic patterns are the only thing allowed to stand between an engineer and their work. The PII model and risk-over-time scoring rank and explain; they never stop a request.


A signed record proves what we saw. It says nothing about the laptop that routed around us. So each machine running the gateway from PyPI signs which agents it had hooked and which servers it wrapped, checked against the key registered to that device and folded into the same daily root. A gap stops being an assumption and becomes evidence.


A signed root is only as good as your ability to prove we did not re-sign it later. So publish it outside our blast radius: an S3 bucket with Object Lock, or a witness repository that commits each day’s root on a schedule you control. The bundle ships the witness config; nothing about this needs our cooperation after setup.
On a hosted deployment the log-signing key is ours — so this, not key custody, is what makes the record independent of us.
what a security review will ask
Prompt and response text AES-256-GCM encrypted at rest on the server, TLS 1.2+ in transit. Pre-SOC 2.
questions people actually ask
Those tools were built for files and web traffic, not prompts. Without TLS inspection, network CASB and DLP tools see only an encrypted session to an AI provider. The gateway reads calls on your machine before they are encrypted; the extension sends prompts to Vloex to be checked before they go out (a late or failed check lets them through) and coaches the person typing.
On the gateway from PyPI, scanning and policy run on your machine, so a blocked call never reaches the tool. What we receive, blocked or not, is event metadata, its signature, and the text of the call — the tool arguments up to 50,000 characters and, if the call proceeds, the result up to 200,000, which are the backend’s per-field limits — stored encrypted. Anything past those limits is cut, and the event records that it was cut rather than letting the shortfall pass for a complete record. This is the full payload, not a preview: the ledger is re-scanned from the text it receives, so text that never arrives is text nothing ever checked. The browser extension sends the prompt to be scanned before the request goes out, and what we keep is governed by your coverage level — up to 50,000 characters each of prompt and response at full trace, none of either at metadata-only. If that is still too much, the entire platform can run self-hosted inside your environment.
No. Connect Google Workspace or Microsoft 365 with read-only OAuth and you will see the AI apps Vloex recognises among those your team has authorized. The extension and the gateway are how you move from seeing to stopping, and you can add them later.
In the browser a prompt waits at most 250ms for the check, and if the server errors or has not answered within 150ms the prompt is sent anyway. Blocked agent calls return a readable reason instead of a failure, so the agent can correct itself and continue. By default only deterministic patterns block; the PII model and risk scoring advise and prioritize review rather than stopping work.
Thirty minutes, no deck. We connect your workspace live, look at what turns up, and if it is not a fit we will say so on the call rather than send you a sequence of follow-up emails.
design partners
A small number of design partners this quarter. The full platform at no cost, an hour of setup with the people who built it, and a weekly loop where what you say changes what gets built. In exchange we ask for real usage and permission to name you later.