SecRouter documentation

SecRouter is a self-hosted, OpenAI-compatible AI gateway that sits in front of your LLMs and enforces governance and cost control on every request — chat, embeddings, and agentic MCP tool calls alike: SSO authentication, per-user policy and budgets, deny-by-default egress with a data-classification gate, and a hash-chained, metadata-only audit log.

It’s a drop-in endpoint — point any OpenAI-compatible client at SecRouter, change the base URL, and keep your code.

What it does

Govern — OIDC SSO + MFA, per-user/group allowlists for models and MCP tools, deny-by-default egress. Chat, embeddings, and tool calls all pass the same gates. Contain spend — per-user token & cost tracking, budgets, rate limits, smart routing. Stay up — a per-provider circuit breaker fails fast to the next authorized model; Prometheus /metrics + W3C trace propagation feed your SOC. Prove it — tamper-evident audit and one-click evidence export, mapped to NIST 800-171 R2 / CMMC L3 controls.

Get started

• Deploy
  • Prerequisites
  • Run the container
  • Production configuration
  • TLS & FIPS
  • Model providers (Bedrock ↔ Azure)
  • GovCloud & air-gap
  • systemd (non-container)
  • Fail-closed startup
  • Health & restart
• Usage
  • Authenticate
  • Make a request
  • Smart routing & overrides
  • Embeddings
  • MCP tool gateway
  • Endpoints
  • See your usage
  • Admin console
  • Add a local or on-prem endpoint
  • Client integration (OpenAI SDKs)
• Configuration
  • Shape
  • The security block
  • Reload without restart
• Control Validation
  • The fast path: one-click evidence bundle
  • Artifacts at a glance
  • Audit trail — AU 3.3.x
  • Access policy & identity — AC 3.1.x / IA 3.5.x
  • Egress / data-flow control — AC 3.1.3 / SC 3.13.6
  • Usage & accountability — AU 3.3.2
  • Configuration baseline & change control — CM 3.4.x
  • Crypto / FIPS posture — SC 3.13.8 / 3.13.11
  • Collect an assessment package
  • Shared responsibility
  • Control map

• Deploy — run the container in your boundary: production config, TLS/FIPS, GovCloud, air-gap, systemd.

• Usage — the API, authentication, the admin console, smart routing, adding endpoints.

• Configuration — providers, tiers, models, and the security block.

• Control Validation — retrieve the CMMC artifacts: audit, access policy, egress, FIPS posture, and a one-click evidence bundle.

The request pipeline

Every call flows through four gates, with usage metered and everything logged:

client ──▶ AuthN ──▶ AuthZ ──▶ route ──▶ egress gate ──▶ authorized model
          (OIDC)    (policy +   (cheapest   (deny-by-default
                     quota)     capable)     + data residency)

If any gate says no, the request never leaves your boundary.