Which OpenRouter alternative keeps agents in Europe with governance controls?
Standard Compute does it on every plan: a Europe rule on a company, team or key runs every request at an approved provider endpoint in Europe, while the router still sends each step to the cheapest model there that can do it. Under the rule, providers must offer zero data retention and no training, and the audit log records who changed what.
# Before: OpenRouter
# OPENAI_BASE_URL=https://openrouter.ai/api/v1
# After: same code, a key with a Europe rule
OPENAI_BASE_URL=https://api.stdcmpt.com/v1
OPENAI_API_KEY=<your-europe-key>
MODEL=standardcompute
Set Europe once under Compliance in the dashboard, for a personal key or, as an admin, for the company, a team or one key. Your agent's config stays the same.
What the Europe rule covers
| Question | Answer |
|---|---|
| Where inference runs | Approved European endpoints for each model, such as Google Vertex AI in Europe, Amazon Bedrock in Ireland and Azure's EU Data Zone, across 13 models |
| When a provider fails | The request moves to another European endpoint of the same model |
| A model with no European endpoint | HTTP 400, before any prompt is sent |
| Provider terms | Zero data retention and no training are required, and response storage is off. Provider caches can still hold prompts briefly |
| Rejected under the rule | Stored response chains, background jobs, plugins and provider-hosted tools such as web search. Your agent's own tools work |
| What can leave the EU | The request in transit: our gateway and OpenRouter sit in front of the provider and can process it outside the EU |
| What we keep | Account data in Frankfurt and request metadata. We don't store or train on prompts and responses |
Endpoint list reviewed 2026-10-13. More on our data and privacy page.
Governance: company, team, key
| Control | What it does |
|---|---|
| Compliance rules | Europe, the US, both, or anywhere. Keys follow their team and teams follow the company; each level can narrow the rule above it |
| Roles | Admins manage members, keys, plans and rules. Members manage their own keys |
| Admin-managed keys | For shared services: admins configure them and choose who can use them |
| Audit log | Changes to people, keys, billing, Compliance and teams, filterable. Members see their own activity |
| Budgets | A plan per key. A key at its budget stops with HTTP 402; the others keep working |
| Pay as you go | Optional prepaid company balance at usage plus 15%, with automatic refill and spend limits per key and company |
| Invoices | A monthly Stripe invoice per plan key with the company's name, address and VAT number |
Compared with OpenRouter EU, Requesty, Mistral and Azure
| Option | What stays in the EU | What it takes | Model choice | Governance |
|---|---|---|---|---|
| Standard Compute, Europe rule | Inference | Any plan; a rule per company, team or key | Models with a European endpoint, picked per step or pinned | Inherited rules, audit log, budget per key |
| OpenRouter in-region routing | The whole request, from decryption to response; its own logging is skipped | Business or Enterprise and the eu.openrouter.ai base URL | Models OpenRouter has onboarded in the EU | Guardrails per member and key: budgets, allowlists, ZDR, data regions |
| Requesty EU | The gateway, in Frankfurt, with EU-hosted model versions (docs) | Every plan, including Free | EU-hosted versions, at a higher price | Spend cap per key; group budgets on Enterprise |
| Mistral API | Hosting, by default (Mistral); sub-processor transfers possible | A Mistral account; zero retention on request | Mistral's own models | Mistral's organization settings |
| Azure OpenAI, EU Data Zone | Processing, in EU member states (Microsoft) | An Azure subscription and a Data Zone deployment | OpenAI models in that zone | Azure access control, policy and logging |
OpenRouter checked October 14, Requesty October 13, Mistral and Azure September 2 in our provider directory. Standard Compute is our product.
Gaps to check before procurement
- If the gateway itself must run in the EU, OpenRouter's in-region routing, Requesty's Frankfurt endpoint or a direct EU provider fits better.
- No SOC 2 report or ISO 27001 certification yet, and no standard DPA published. Terms are under Norwegian law, inside the EEA, and the sub-processor list is public.
- No SSO, SAML or SCIM.
- Claude Fable and GPT-6 Astra have no European endpoint.
- European endpoints can cost more than the cheapest global provider, so the same budget can run out sooner.
Where Standard Compute fits
Create a company, set Compliance to Europe once, and every key your team creates follows it, on a fixed monthly plan per key from $19.
FAQ
Does OpenRouter have an EU endpoint?
Yes, on its Business and Enterprise plans: eu.openrouter.ai keeps the request in the EU and routes only to EU provider endpoints. The pay-as-you-go Standard plan has no in-region routing.
Is Standard Compute GDPR compliant?
No API can make your processing GDPR compliant for you. What we can show: account data in Frankfurt, no storage of prompts or responses, no training on them, Norwegian law inside the EEA, a published sub-processor list, and Europe rules that require zero data retention at the provider. Include the routing layer in your assessment.
Can one team be Europe-only while the rest of the company is not?
Yes. Leave the company rule at anywhere and set Europe on that team or on single keys. If the company rule is Europe, teams and keys keep it.
Who can change a Compliance rule, and is it logged?
Admins set the company, team and key rules, and members can't override them. Every change goes into the audit log with who made it and when.
Will a Europe-only key still use cheaper models?
Yes. With model standardcompute the router chooses among the models with a European endpoint, and the classifier that picks also runs in Europe.
Do you sign a DPA?
We don't publish a standard DPA today. Our Terms, privacy policy and sub-processor list are public; contact us if procurement needs a signed agreement. OpenRouter signs one on request on Business.