Why companies look for an alternative to Orq.ai
From Orq.ai’s own pricing and documentation, checked 9 November 2026:
- A platform fee on credits: routing on Orq credits carries a 4.5% fee on top-ups, and platform usage is billed in spans, data and agent runs.
- SSO behind paid tiers: Orq's SSO documentation places SSO on the Enterprise plan, and the pricing page lists it in the 300 euro a month Teams add-on.
- Audit logs on Enterprise: audit logs are an Enterprise plan feature.
- Data kept 30 days on pay-as-you-go: Orq's data compliance page sets 30-day retention on pay-as-you-go, with custom retention on Enterprise.
- Model calls go where you route them: Orq hosts the platform on Google Cloud in the EU and sends each model call to the provider you choose.
What Standard Compute does differently
A single API gives you frontier and open-source models, and it routes each step to the cheapest model that can do it and the cheapest provider fast enough to serve it.
There is no fee on credits and no span or seat metering. Routine agent steps go to a model priced for that work and the hard step goes to a frontier model. You pay a flat monthly plan per person or app.
Control is set once for the company:
Processing in Europe
Set a Europe rule for your company, a team or a single key, and every request, including retries and fallbacks, is served only by approved European inference endpoints. If no European endpoint can serve it, the request is refused before your prompt is sent. Our EU gateway terminates TLS and runs in Finland, and your account data is stored in Frankfurt.
Zero data retention
Turn on zero data retention for your company, a team or a key, and every request is routed only to inference endpoints that commit to keeping no copy of your data. Teams and keys inherit the requirement and can never switch it off underneath you.
No training
Standard Compute never trains on your prompts or outputs. With a region rule or zero retention turned on, every request goes only to providers that commit not to train on it.
Single sign-on
Connect Microsoft Entra ID or any SAML identity provider so your people sign in with their work accounts. Employees sign in to Claude Desktop and Claude Code with their Microsoft work account through our EU gateway, and access follows your Entra groups through SCIM provisioning.
Teams and keys
Organize your company into teams, invite colleagues by email, and give every person and every app its own key, all under one company account.
Budgets
Every person and app gets a fixed monthly budget that never overruns, and you can set spending caps per key and for the whole company. Optional top-off from a prepaid company balance keeps critical agents running.
Allow-lists
Choose exactly which inference providers may handle your data, for the whole company, a team or a single key. New providers are never added without an admin's approval, and fallbacks can never route around your list. Decide which models each key can use.
Audit
Every admin change is recorded with before and after values, and you can export a record of every request showing the model, the provider that served it and the region rule in force, kept for 12 months.
Contract
Sign our Data Processing Agreement in the dashboard. It commits us to no training on your data, no retention of your content, and breach notification within 72 hours. We publish every sub-processor and give you 14 days' notice before adding a new one.

Standard Compute and Orq.ai compared
| Standard Compute | Orq.ai | |
|---|---|---|
| Pricing | Flat monthly plan per person or app with no per-token surprises; Stripe invoices with your company name and VAT number | Free tier, then usage in spans, data and agent runs; extra seats 35 EUR; Teams add-on 300 EUR a month; 4.5% fee on credit top-ups |
| Cost routing | Each step goes to the cheapest model that can do it | Smart Router with a cost mode; fallbacks, retries, caching and load balancing |
| Models | Claude, GPT, Gemini and open models (GLM, DeepSeek, MiniMax, Kimi) through one API | 500+ models from 30+ providers |
| Processing in Europe | Europe rule per company, team or key; retries and fallbacks stay on approved European endpoints; refused before sending if none qualifies | Platform on Google Cloud in the EU; model calls can be restricted to EU endpoints |
| Zero data retention | Per company, team or key; lower levels cannot switch it off | ZDR provider filter; data kept 30 days on pay-as-you-go |
| Training on your data | Never trains on prompts or outputs | Not used to train or fine-tune models |
| Single sign-on | SAML SSO, Microsoft Entra ID included; Claude Desktop and Claude Code sign-in with a Microsoft work account, SCIM from Entra | SAML or OIDC with SCIM; Enterprise or Teams add-on |
| Teams and keys | Teams, roles, a key per person and per app | Workspaces and projects; Admin, Developer and Researcher roles |
| Spend limits | Fixed monthly budget per key; requests are refused once it is used; caps per key and per company | Budgets and alerts with hard caps |
| Provider and model allow-lists | Provider allow-list per company, team or key; new providers need an admin; models chosen per key | Routing restricted to approved or EU endpoints; guardrails |
| Audit log | Admin log with before and after values; request export with model, provider and region rule, kept 12 months | Enterprise |
| What you operate | Managed service; nothing to host | Managed EU service; VPC and on-prem on Enterprise |
When Orq.ai fits
Orq.ai fits a product team that wants one platform for prompts, evaluations, agents and tracing alongside the gateway, with on-prem deployment on Enterprise.
Moving from Orq.ai to Standard Compute
Standard Compute’s API runs on stdcmpt.com. https://eu.stdcmpt.com is our EU gateway in Finland.
- Create a company workspace and set the rules once for the company: a Europe rule, zero data retention, and the providers and models you approve. Teams and keys inherit them.
- Create a key for each person and each application, each with its own monthly budget.
- Change the base URL from
https://my.orq.ai/v3/routertohttps://eu.stdcmpt.com/v1and swapORQ_API_KEYfor a Standard Compute key. Model IDs keep thevendor/modelform. - Point Claude Code at
https://eu.stdcmpt.comin place ofhttps://my.orq.ai/v3/anthropic. - Connect Microsoft Entra ID or your SAML identity provider so your people sign in with their work accounts, and set up Claude Desktop and Claude Code sign-in with Microsoft work accounts.
# Before
OPENAI_BASE_URL=https://my.orq.ai/v3/router
OPENAI_API_KEY=$ORQ_API_KEY
# After: Standard Compute EU gateway
OPENAI_BASE_URL=https://eu.stdcmpt.com/v1
OPENAI_API_KEY=YOUR_STANDARD_COMPUTE_KEYfrom openai import OpenAI
client = OpenAI(
base_url="https://eu.stdcmpt.com/v1",
api_key=os.environ["STANDARD_COMPUTE_API_KEY"],
)
# "standardcompute" sends each step to the cheapest
# model that can do it. Or pin a model:
# model="anthropic/claude-sonnet-5.5"
client.chat.completions.create(
model="standardcompute",
messages=messages,
)# Claude Code adds /v1/messages itself
export ANTHROPIC_BASE_URL=https://eu.stdcmpt.com
export ANTHROPIC_AUTH_TOKEN=YOUR_STANDARD_COMPUTE_KEY
claudeQuestions
Is there an Orq.ai alternative that is just the AI gateway?
Standard Compute is one gateway to frontier and open-source models with company controls: a Europe rule, zero data retention, Microsoft Entra SSO, teams, a budget per key, provider and model allow-lists and an audit log.
Is SSO available without an Enterprise plan?
SSO is set up self-serve in the dashboard, and Enterprise features can be bought one at a time or together. Connect Microsoft Entra ID or any SAML identity provider, and anyone on your verified domain joins your company automatically.
Are prompts stored?
We process your prompts in memory to serve each request and never write them to storage or logs. Request records hold metadata only: model, provider, tokens, cost and status.
Does the Europe rule cover inference?
Yes. With a Europe rule, every request, including retries and fallbacks, is served only by approved European inference endpoints. If no European endpoint can serve it, the request is refused before your prompt is sent.
How do we migrate from Orq.ai?
Create a company workspace and set your rules, then change the base URL from https://my.orq.ai/v3/router to https://eu.stdcmpt.com/v1 and swap the key. OpenAI-compatible client code stays the same.
Set up your company
Create a company workspace, invite your team and set your rules from the dashboard. Security questionnaires and procurement questions go to contact@standardcompute.com.
Create a company workspaceor write to contact@standardcompute.com
Sources (checked 9 November 2026)
- Orq.ai homewww.orq.ai
- Pricingwww.orq.ai
- EU regions FAQdocs.orq.ai
- Deployment optionsdocs.orq.ai
- Data compliancedocs.orq.ai
- SSOdocs.orq.ai
- Audit logsdocs.orq.ai
- Smart Routerdocs.orq.ai
- OpenAI-compatible APIdocs.orq.ai
- Claude Codedocs.orq.ai