A guardrail that runs on a sample is not a guardrail. Here is how nRouter applies PII redaction, prompt-injection detection and keyword blocklists inline on every call, with key-over-team-over-org precedence, on every plan.
Bring-your-own-key sounds customer-friendly and mostly relocates work to you. nRouter issues one key and credits and manages every provider account — here is the reasoning, the blast-radius math, what the choice costs you, and who should pick a BYOK gateway instead.
"Who rotated that key, and from where?" should be a filter, not an archaeology project. Here is the audit-trail contract we hold ourselves to on an LLM gateway: complete actor attribution, one shared client-IP path, append-only entries, and reads that are role-scoped and tenant-isolated.
A criterion-by-criterion checklist for putting an LLM gateway through SOC 2 — access control, audit attribution, retention, encryption, tenant isolation and availability — with the honest current state of each control on nRouter.
A flat organization works until the second team arrives, and then every key, budget and policy is visible to everyone. Here is how nRouter nests org, team and key, which control attaches where, and why the team a request is billed to is read from the key rather than the request body.
A management credential and an inference credential are different tools with different blast radii. Here is how to issue one virtual key per environment-and-service pair, narrow it with the four scope fields, cap it, and rotate it without downtime.
