Enterprise
Everything a security review asks about, in one place
Larger teams ask the same questions in the same order: who can use which models, who approves, what happens to the prompts, where they are processed, and what stops the bill running away. Here is how each one is answered.
Roles, approvals and an audit trail
Owners run billing and the roster; admins run keys and guardrails; members watch and request. A key request needs a second person to approve it, and every role change and decision lands in a trail written by the database rather than by application code.
Guardrails that run before the model
Injection detection that decodes base64, hex and letter-scrambling before matching; sensitive-data redaction where the provider receives the redacted prompt; model, provider and region access enforced per key.
Ceilings that act before the invoice
A monthly budget for the account, a rolling daily cap per key that can downgrade instead of refusing, and per-session stops for agent runs. Enforced at the gateway, counted with the same arithmetic the biller uses.
EU processing you can check
The platform runs in Frankfurt, every model's processing region is recorded with its source and the date we read it, and an EU-only guardrail routes a key exclusively to models whose recorded policy processes in the EU.
Attribution for chargeback
Label requests by app, end customer, session and tag, then read spend split along each. The log exports exactly the filtered view as CSV, which is what reconciling against a provider invoice actually needs.
Keys provisioned programmatically
Issue, cap and revoke a key per customer or environment through the API, using a management credential that administers keys and cannot itself reach a provider or spend anything.
Requirements we should talk about
Every organisation arrives with a list - an identity provider to connect, a compliance framework to satisfy, a deployment model to fit. Send yours and you will get a straight answer on each item: what works today, what is scheduled, and what we would build for a customer who needed it.
Our security posture, data handling and the full detail behind every control above are in the trust centre, written for the person who has to sign off rather than the person who has to be sold to.
The commercial shape
There is no enterprise tier that unlocks features, because the governance controls above are not gated - they are how the product works. Pricing is the same published arithmetic at any size: tokens at each provider's list price with no markup, and a fee applied once when you buy credit rather than on every request. No seats, no subscription, no minimum.
What a larger account does want is usually invoicing, a data processing agreement, and somebody who answers quickly. All three are a conversation rather than a plan you pick.