Enterprise
One contract for every model your teams want to use
Procurement approves one vendor. Security reviews one data path. Engineering keeps the freedom to pick whichever model is best for each job, and finance sees a single invoice with per-project attribution.
- 99.98%
- gateway availability
- Net-30
- invoiced billing
- US / EU
- pinned regions
- SOC 2
- controls in progress
Controls your security review will actually ask about
Every item below is enforced by the gateway on each request, not configured once and hoped for. A policy that cannot be satisfied fails the request rather than falling back to something out of policy.
SAML and SCIM
Okta, Entra ID, and Google Workspace. Directory-synced roles, enforced sign-in, and automatic deprovisioning when someone leaves.
Regional routing
Pin a project to US-only or EU-only endpoints. Requests that cannot be served in-region fail rather than silently leaving it.
Retention policy
Zero-retention by default, with providers that train on inputs excluded at the org level. Enable logging per project when you need it.
Budgets and limits
RPM, TPM, concurrency, and daily or monthly spend ceilings per key, per project, and per organization.
Audit logs
Every key, member, policy, and routing-configuration change, with actor and timestamp, exportable to your SIEM.
Invoicing
Net-30 terms, purchase orders, committed-volume discounts, and a single monthly invoice covering every provider you route through.
Bring us your security questionnaire
We will answer it, and show you the routing policy that enforces each answer.
Talk to sales
