The control plane, built in the open.
Seven controls, one gateway. Here’s what’s shipped, what’s building, and what’s still research — and we’re honest about the difference. We don’t move a lane up until the code does.
Now
In research · private betaWhere we're starting: cost visibility that reconciles estimates to the real invoice. In research — nothing shipped yet.
The plan: read-only connectors that unify spend by team, project, and model, with a forecast and sized recommendations measured against your own baseline. No traffic routed — just the numbers.
Next
Building the gatewayThe request path everything else depends on — and the operational controls that come with it.
One OpenAI-compatible endpoint your agent traffic flows through. Everything below needs it.
Every request traced — tokens, latency, errors, cost — per key, team, and model.
Per-key, per-team, and per-model ceilings and quotas, enforced in the path.
Enforce what agents may say and do; redact PII in flight.
Later
ResearchThe harder, differentiated controls — enforced and proven from the same event stream.
Detect and block prompt injection and jailbreaks before they reach the model.
An audit trail, policy evidence, and data residency, drawn from the request stream.
Prove your agents and model choices hold up — on your own traffic, not a public benchmark.
How to read this
- A lane moves to Shipped only when it’s real in the product — the same rule that fails our build if a claim on this site drifts from the code.
- Building and Next are honest about order: the gateway comes first because everything downstream needs the request path.
- Research means we have a point of view and no shipped code yet. We say so.