Esc to close · ⌘K / Ctrl-K opens search anywhere
Enterprise
A personal API key is fine for a weekend project. A company needs identity from its own IdP, budgets that are enforced, not suggested, and data-residency it can prove per request. BharatRouter ships all three at the gateway — with INR billing and GST invoices your finance team will actually accept.
Three pillars
SAML 2.0 SSO handled in the gateway — no third-party identity broker in your data path — with SCIM provisioning, verified company domains, and auto-join so colleagues land in your org, not in personal accounts.
Roles, model and provider allowlists, org-wide system instructions injected at the gateway, an append-only audit log — and hard budget caps at five scopes where thetightest cap wins.
data_policy: india_only routing enforced per request, zero-retention inference by default under DPDP, and per-provider transit disclosure so you can show your DPO exactly where data goes.
Personal → Team → Enterprise
The same per-token price at every tier. Members are always unlimited and free — you’re billed for what you use, never per seat. Each tier adds capability, not a headcount tax.
One person, self-serve
A company — no seat limits
Everything before, plus:
Governed, IdP-driven
Everything before, plus:
Getting your company on
Sign in and create an organization — you’re the owner, teammates get roles.
Add up to 20 company domains and prove each with a DNS TXT record.
Point your SAML IdP at the gateway; members provision just-in-time — or push them via SCIM. Flip on require-SSO when ready.
Anyone signing in with a company email lands in your org — existing accounts included.
Step-by-step guides: SSO (SAML) · Teams, domains & workspaces · API keys & limits
Budgets · tightest cap wins
Set a hard cap at any of five scopes. Every request is checked against all of them at the gateway and the tightest cap wins — a runaway agent hits its key’s ceiling long before it dents the org’s.
One hard cap on everything the organization spends — the number your CFO signs off on.
Give the ML platform team and the support-bot team separate envelopes.
Keep production spend fenced off from staging and experiments — with per-provider and per-model caps inside a workspace.
A developer’s experiments stop at their own cap, not the company’s.
The tightest fence — cap a single API key powering a single integration.
Pair caps with the usage & activity export (CSV / JSON API) for month-end reconciliation.
Shipped, not promised
SAML 2.0 is handled inside the gateway itself — no third-party identity broker sits in your data path. Configure your own IdP per org, provision members just-in-time on first sign-in, and turn on require-SSO so every member must come through it.
Drive membership from your directory: joiners are provisioned automatically, and the moment IT removes a leaver they are deprovisioned here too — no orphaned accounts still holding keys.
Add up to 20 company domains and prove ownership with a DNS TXT record. Colleagues on a verified domain auto-join your org — and anyone who isn’t provisioned yet lands on a self-service “request access” page (routed to your admins by their work-email domain) instead of a dead-end. Approve or deny from a queue in the console.
Owner → Org-Admin → Workspace-Admin → Developer → Member, so you delegate a single workspace’s budget and keys to its lead without making them an org-admin. Layer on composable functions — Finance, Auditor, Analyst — to grant cost, usage or audit visibility à la carte, without handing over management. Consumption is universal; roles govern management, not who may use the product.
Inject org-wide system instructions at the gateway so policy rides every request; allowlist or denylist exactly which models and providers your traffic may reach; and review an append-only audit log of who changed what, and when — all enforced at the gateway, not in a client library.
Hard caps at org, team, workspace, member and key level — the tightest wins, enforced at the gateway, with per-provider and per-model caps inside a workspace. Choose hard-stop or metered overage, and read one reconciled statement — included, consumed, remaining, over — per person and per team.
Create keys with a bounded expiry, set an org-wide max-tenure ceiling so new keys can’t outlive policy, and get expiry reminders before a key lapses. Existing keys are grandfathered — nothing is retroactively expired.
Every request is attributed — by member, key, workspace, model and provider — and available as CSV, a grouped Cost API, or a plain-English question: “which workspace spent the most last month?” Conversational FinOps over your own gateway bill, gated to Finance.
Send data_policy: india_only and requests route only to India-resident endpoints — enforced per request. Inference is zero-retention by default (DPDP), with per-provider transit disclosure so you can see where bytes travel.
An INR-canonical prepaid wallet, GST tax invoices, and payments via Razorpay. Your finance team gets rupee numbers and Indian paperwork, not a foreign card statement.
Your agents authenticate with short-lived, verifiable identities instead of long-lived API keys — revocable centrally, attributed and budgeted per agent, and bounded by an agent-tenure ceiling so a dormant identity can’t linger. Billed to the right org.
Compliance posture, privacy policy and DPDP notes live on the legal page.
Everything on this page is live in the product today. What we don’t have yet is a paid SLA tier — so while we’re in beta, enterprise evaluations are handled directly by the team. Tell us what you’re building and we’ll get your org, domains and IdP set up with you.