Build on many models. Govern every rupee and every request.
Whatever you're solving for — velocity, cost, governance or data sovereignty — it runs on the same OpenAI-compatible gateway, billed in rupees and built for India.
Build on many models, not one contract
Ship features against the best model for each job and switch freely as the frontier moves — without re-integrating, re-contracting or re-billing.
- One OpenAI-compatible API — Keep your SDK and use catalog model IDs through the compatible API surfaces currently available.
- Route smartly — Name a model, or use unoblox/auto, pareto or free to let the gateway pick the best healthy endpoint per request.
- Automatic failover — A provider outage becomes a retry on the next endpoint — not an incident for your on-call.
What you get
Control cost at scale, in rupees
Track eligible usage, balances, holds and hard limits in INR; confirm funding and tax documents in the authoritative payment flow.
- Shared balance controls — Where funding is enabled, workspaces can use a shared INR balance with explicit budgets and holds.
- Budgets & spend limits — Cap spend per workspace and per key, so a runaway job or a leaked key can't blow the month.
- Top up on your terms — Razorpay top-ups and auto-top-up keep services running without manual wire transfers or foreign-currency paperwork.
What you get
Govern every team and every request
Put identity, isolation and policy around AI usage across your organisation — with the audit trail your security and compliance teams expect.
- SSO & SCIM — SAML single sign-on and SCIM provisioning wire unoblox into your identity provider and joiner-mover-leaver flows.
- Workspaces & guardrails — Isolate teams with their own keys, budgets and allow/block policy; screen traffic with moderation.
- Audit & maker-checker — An immutable audit trail records every change; sensitive platform actions require a second approver.
What you get
Keep India's data India-first
Meet Indian data-protection expectations without giving up global models — with data-residency intent, DPDP-aligned handling and retention you control.
- Data-residency intent — An India-first posture across billing, identity and data handling, built for the DPDP era rather than retrofitted to it.
- Zero-data-retention routing — Route sensitive workloads to endpoints that retain nothing; log metadata only — token counts and cost, never content.
- Private AI — Dedicated GPUs run for your organisation. Talk to the team.
What you get
Let's map unoblox to your stack
Tell us what you're building and where it needs to run. We'll help you choose models, routing and governance that fit.