OmniRoute / Security and data control

Controls you can read the source of.

Guardrails on the request path, network and identity controls, encrypted local credentials, and what stays auditable afterwards.

Review the controls Try Cheaper Inference Back to overview

Controls

What the gateway checks, and where.

Every control below runs in the process you host. None of it depends on a Cheaper Inference account.

On the request path

Checks that run before a prompt leaves the machine and before a response reaches the caller.

Prompt-injection guard on every routed request
Opt-in credential masking that redacts leaked keys in both directions
Opt-in PII redaction
Normalized safety filters that do not depend on one provider's policy
Vision guardrails for image inputs

Network and identity

Controls over how requests leave the host and what they look like on the wire.

Proxy scopes: global, per provider, per connection
SOCKS5 and HTTP(S) proxies
JA3/JA4-capable TLS transport with provider-specific client profiles
IPv4 and IPv6 egress selection
SSRF guard that blocks private address ranges on outbound fetch
IP allowlists and blocklists on the dashboard

Credentials and local data

Keys, history and usage stay on the host you run, in a database you own.

AES-256-GCM encrypted credentials in local SQLite
Scoped API keys with model and provider restrictions
Per-key USD spend limits and token budgets
OAuth account email masking, on by default
No OmniRoute account required to run the gateway

Operations and audit

What you can reconstruct after the fact, and who was allowed to do it.

Administrative audit log filtered by action, actor and target
Request logs filtered by provider, model, account and key
Optional OIDC login gate, with password login always available
Adaptive admission that queues heavy requests instead of failing them
Database export and import for backup and migration

Network reach

Network routing and local data controls.

Proxy scopes control network routing while local-first storage keeps operational data on your machine.

Three proxy scopes

Route globally, per provider or per individual connection.

Global · per-provider · per-connection
SOCKS5 and HTTP(S) proxies
Proxy marketplace integration

TLS and client fingerprint controls

Match supported provider clients down to selected transport characteristics.

JA3/JA4-capable transport via wreq-js
Provider-specific client profiles
IPv4 and IPv6 egress controls

Private and local-first

Keys, usage and history stay on the host you control.

SQLite on disk with AES-256-GCM encrypted credentials
No OmniRoute account required
Self-host on infrastructure you choose

RussiaChinaIranCubaTürkiye

Failure isolation

Isolate provider, connection and model failures.

A bad key should not kill a provider. A limited model should not kill a connection.

model ⊂ connection ⊂ provider

Provider circuit breakerWhen a provider is unhealthy, combo routing skips it until a half-open probe succeeds.

Connection cooldownCool down one key or account while sibling connections keep serving.

Model lockoutLock one rate-limited or unavailable model while other models on the connection remain available.