One managed gateway,
tuned to your industry’s rules.
Every team ships on the same gateway: smart routing, built-in guardrails, real-time cost & usage tracking, audit logs. What changes by industry is which controls matter most. Pick yours.
No BYOK · one bill · every control on every plan
- 151Models liveAlibaba US, OpenAI, AWS Bedrock, Azure Foundry, Google Vertex AI & Anthropic
- 8Residency regionsUS + EU GA, more on request
- 99.9%Uptime SLASame SLA on every tier
- 0Features gatedEvery control on every plan
Six industries. One gateway. No invented claims.
Enterprise governance across every vertical.
| Requirement | Finance | Health | Legal | Retail | Gov | Edu |
|---|---|---|---|---|---|---|
| Inline PII/PHI Redaction | ||||||
| Zero-Content Data Policy | — | — | ||||
| Sovereign Data Residency (US/EU) | ||||||
| Per-Matter / Team Budget Caps | — | |||||
| SOC 2 CC7.2 Immutable Audit Logs | ||||||
| Dedicated Tenancy / VPC Link | — | — |
Smart routing + failover
One OpenAI-compatible endpoint; automatic retry on a backup model when a provider degrades.
Guardrails on every request
PII/PHI redaction, prompt-injection detection, and secret scanning, inline on every plan.
Budgets at three scopes
Hard and soft caps per org, team, and key. A tripped hard cap returns 402 — never a negative balance.
Audit + observability
Append-only audit trail with actor, IP, and diff; request logs export to Langfuse, Datadog, or S3.
Need the deployment, contract, and residency depth? See Enterprise — dedicated tenancy, VPC, SSO, and procurement-ready legal artifacts.
Industry solutions questions, answered
How does nRouter support regulated enterprise industries?
Every industry inherits the same audited gateway core: inline PII and PHI redaction, multi-tenant isolation enforced via database Row Level Security, append-only SOC 2 CC7.2 audit logs, and hardware encryption at rest and in transit. What changes by vertical is which policy toggles and residency constraints are applied.
Can we enforce data residency for EU, US, or specific sovereign regions?
Yes. Enterprise and Pro plans can pin data residency to US or EU regions, guaranteeing that prompt traffic, telemetry, and cached responses never transit outside approved sovereign jurisdictions.
How do guardrails prevent PII and PHI leakage across external model providers?
nRouter guardrails execute inline before any outbound request reaches OpenAI, Anthropic, or Google. Detectors scan for social security numbers, medical record identifiers, credit cards, and API secrets, redacting or rejecting violations before payloads leave our security boundary.
How does unified billing work across multiple AI providers?
You receive one consolidated monthly invoice from nRouter regardless of how many providers (Azure, Vertex AI, AWS Bedrock, OpenAI, Anthropic) your teams consume. Pre-funded credit reservations prevent surprise overdrafts, and per-key ceilings enforce hard caps.
Don’t see your exact use case? We will map it.
Tell us how your team uses LLMs and which rules you answer to. We will walk through the routing, guardrail, budget, and residency setup that fits — no over-promised timelines.
No invented certifications · no claims we cannot back