Enterprise capability

Provider Compliance Policies

Only route to providers you're allowed to use

Provider Compliance Policies turn a procurement requirement into an enforced guardrail. Pick the attributes you require and the gateway evaluates every provider against your policy on each request. Non-compliant providers are removed from automatic routing, and a request pinned to one (e.g. deepseek/deepseek-v3.2) is rejected with a 403 — before any prompt is sent upstream. Every requirement is fail-closed: a provider qualifies only if its published data policy explicitly satisfies it, so unknown attributes never slip through. The settings page previews exactly which providers are allowed and blocked under the current policy, and every block is recorded as a security event for review.

Why teams turn it on

Certification-based routing

Require SOC 2, ISO 27001 (or either), and GDPR. Providers without the certifications you mandate are never used.

Data-handling guarantees

Require providers that don't train on prompts and don't log them — enforced on every request, not just documented.

Fail-closed by default

A provider qualifies only if its data policy explicitly meets each requirement. Unknown attributes are treated as non-compliant.

Blocked, with a paper trail

Non-compliant requests return a clear 403 and are recorded as security events so admins can see what was rejected and why.

How it works

From decision to deployed in three short steps

  1. 01

    Enable a policy

    Under Settings → Compliance, turn on the policy and toggle the certifications and data policies you require.

  2. 02

    Preview the impact

    The settings page shows exactly which providers would be allowed and which blocked under the current policy.

  3. 03

    Enforced on every request

    The gateway filters providers per request and blocks anything non-compliant with a 403, logging a security event.

Real-world use cases

Why customers actually adopt this

01

Regulated industries

Insurance, healthcare, and finance teams that may only use providers holding specific certifications.

02

Data-residency and privacy mandates

Guarantee prompts never reach a provider that trains on or logs them.

03

Vendor allow-lists without manual policing

Encode your approved-vendor bar once; the gateway enforces it on every request across all projects.

Frequently asked

What happens to a request that can't meet the policy?
It's blocked with a 403 explaining the policy before any data is sent upstream, and recorded as a security event. This applies to both automatic routing and pinned providers.
How is provider compliance determined?
Each provider carries published data-policy metadata (SOC 2, ISO 27001, GDPR, prompt training, prompt logging). A provider qualifies only if that metadata explicitly satisfies every requirement you enable — unknown attributes fail closed.
Who can manage the policy?
Organization owners and admins on the Enterprise plan. See also Enterprise Audit Logs and Enterprise Guardrails.

See provider compliance policies on your real workloads

Bring a sample workload to a 30-minute call. We'll wire it up live and show you the actual experience your team will get.