Migrate to BharatRouter

BharatRouter speaks the OpenAI wire format, so migrating is almost always a one-line change: point your base URL at us and use a br-… key. Your SDK, request shapes and response shapes stay the same — you just gain enforceableIndia data-residency, INR billing, and routing with automatic failover. Pick your current platform:

Bring your own keys (keep your accounts & rates)

Whichever platform you come from, you don't have to abandon the provider deals you already have. Save a provider key once — encrypted, never shown again — and requests ride youraccount and negotiated rates, with our routing and failover on top. Free during beta. SeeBYOK; 50 providers are supported today.

Keep your reliability setup

If you relied on a fallback list, recreate it as a versioned, shareableCollection — an ordered chain of {model, provider}steps with automatic circuit-breaker failover. You can also register your own deployment as a ₹0 fallback step with BYOE.

Config adapters — coming with the configurable error policy

A drop-in translation layer for competitor configs — Portkey's on_status_codesand LiteLLM's context_window_fallbacks / content_policy_fallbacks — is planned alongside the configurable error-routing policy, so you'll be able to paste your existing config and have it normalized automatically. Until then, the one-line swap plus saved fallback chains cover the same ground. (Roadmap — not yet live.)

Don't see your platform? If it's OpenAI-compatible, the swap above already works — email [email protected]and we'll add a guide.