SSO and SAML
SAML 2.0 and OIDC with any identity provider, plus SCIM 2.0 for automatic provisioning and deprovisioning.
- Role-based access down to the project
- IdP group to project-role mapping
- Deprovisioning revokes the user's keys
The controls your platform, security, and compliance teams ask for — available from day one, not on a roadmap.
SAML 2.0 and OIDC with any identity provider, plus SCIM 2.0 for automatic provisioning and deprovisioning.
Controls mapped to SOC 2 Type II, with an annual penetration test and evidence export available under NDA.
Run the gateway and router in your VPC, or in a single-tenant region we operate for you.
Pin inference and storage to the US, EU, or UK. Requests that would leave the region fail closed.
A shared channel with the engineers who operate the platform, with contractual response times.
Per-team budgets, hard spend caps, and alerts that fire before the invoice does.
Security reviews stall on missing documents. Ours are ready before you ask, and our team answers questionnaires directly rather than routing them through sales.
Most reviews close in two to four weeks. We keep a current security package — SOC 2 report, penetration test summary, architecture diagrams, subprocessor list, and a completed CAIQ — so the first exchange is usually the last one that needs us.
Yes. The gateway and router ship as containers that run in your VPC. Model traffic egresses only to providers you allow, and traces stay in storage you control. The API is identical.
Prompts and completions are never written to disk. Only metadata — token counts, latency, route taken, cost — is retained, which is what the dashboard and your invoice are built on.
Yes. Attach your provider keys and Vantafold routes through them. You keep your committed-spend agreements and pay us only the platform fee.
Severity 1 is 15 minutes, 24/7, in a shared channel with the engineers who operate the platform. Severity 2 is two business hours. Both are contractual, not aspirational.
Inference and trace storage are pinned to the region you choose at the project level. Requests that would leave the region fail closed rather than silently routing elsewhere.
A solutions engineer replies within one business day. The first call is technical — bring your architecture, your compliance requirements, and your awkward questions.