Enterprise alternative to Portkey

Companies look for an enterprise alternative to Portkey when they want the gateway and the models in one place. Portkey is a control layer over provider keys you bring yourself, and SSO, SCIM, audit logs and budgets with rate limits sit on its custom-priced Enterprise plan. Portkey is now Prisma AIRS AI Gateway from Palo Alto Networks.

Standard Compute is one gateway to frontier and open-source models that sends each step to the cheapest model and provider that can serve it, under one contract. SSO, a Europe rule, zero data retention, budgets, allow-lists and audit are set self-serve in the dashboard.

Create a company workspaceor write to contact@standardcompute.com

Why companies look for an alternative to Portkey

From Portkey’s own pricing and documentation, checked 7 November 2026:

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.

Portkey routes the requests you configure and then you pay each provider's list price. Standard Compute does the model choice for you: routine agent steps go to a model priced for that work, the hard step goes to a frontier model, and each request is served by the cheapest provider that meets the latency and tokens-per-second bar. 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 dashboard, Claude Microsoft sign-in setup: step 2 of 4, connecting Microsoft Entra provisioning with a tenant URL and a provisioning credential.
Setting up Claude sign-in with Microsoft work accounts in the Standard Compute dashboard. The company shown is example data.

Standard Compute and Portkey compared

Standard Compute compared with Portkey
Standard ComputePortkey
PricingFlat monthly plan per person or app with no per-token surprises; Stripe invoices with your company name and VAT numberFree developer tier; Production $49 a month for 100k recorded logs; Enterprise custom; model usage billed by each provider
Cost routingEach step goes to the cheapest model that can do it and the cheapest provider fast enough to serve itConditional routing, fallbacks and load balancing you configure
ModelsClaude, GPT, Gemini and open models (GLM, DeepSeek, MiniMax, Kimi) through one APIThe providers you connect with your own keys
Processing in EuropeEurope rule per company, team or key; retries and fallbacks stay on approved European endpoints; refused before sending if none qualifiesEU-hosted SaaS region not published; hybrid data plane in your VPC on Enterprise
Zero data retentionPer company, team or key; lower levels cannot switch it offDepends on each provider contract you bring
Training on your dataNever trains on prompts or outputsDepends on each provider contract you bring
Single sign-onSAML SSO, Microsoft Entra ID included; Claude Desktop and Claude Code sign-in with a Microsoft work account, SCIM from EntraSSO (OIDC, SAML 2.0) and SCIM on Enterprise
Teams and keysTeams, roles, a key per person and per appWorkspaces; role-based access on Pro and Enterprise
Spend limitsFixed monthly budget per key; requests are refused once it is used; caps per key and per companyBudgets and rate limits on Enterprise
Provider and model allow-listsProvider allow-list per company, team or key; new providers need an admin; models chosen per keyModel allow-lists at org and workspace level; tier not published
Audit logAdmin log with before and after values; request export with model, provider and region rule, kept 12 monthsAudit logs on Enterprise
DPASigned in the dashboardNot published
Portkey column from Portkey's own public pages, checked 7 November 2026. "Not published" means we found no public statement.

When Portkey fits

Portkey fits a team that already holds its own provider contracts and wants an observability and guardrail layer on top, inside the Palo Alto Networks security stack.

Moving from Portkey to Standard Compute

Standard Compute’s API runs on stdcmpt.com. https://eu.stdcmpt.com is our EU gateway in Finland.

  1. 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.
  2. Recreate each Portkey workspace as a team, and each Portkey API key as a Standard Compute key with its own monthly budget.
  3. Change the base URL from https://api.portkey.ai/v1 to https://eu.stdcmpt.com/v1 and drop the x-portkey-* headers. Provider choice moves from headers and configs into the provider allow-list.
  4. Point Claude Code at https://eu.stdcmpt.com and remove ANTHROPIC_CUSTOM_HEADERS.
  5. 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.
Request: before and after
# Before
curl https://api.portkey.ai/v1/chat/completions \
  -H "x-portkey-api-key: $PORTKEY_API_KEY" \
  -H "x-portkey-provider: @openai-prod" \
  -H "Content-Type: application/json" \
  -d '{"model": "YOUR_MODEL", "messages": [...]}'

# After: Standard Compute EU gateway
curl https://eu.stdcmpt.com/v1/chat/completions \
  -H "Authorization: Bearer $STANDARD_COMPUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "standardcompute", "messages": [...]}'
Claude Code
# Claude Code adds /v1/messages itself
export ANTHROPIC_BASE_URL=https://eu.stdcmpt.com
export ANTHROPIC_AUTH_TOKEN=YOUR_STANDARD_COMPUTE_KEY
claude

Questions

What is a good enterprise alternative to Portkey now that it is part of Palo Alto Networks?

Standard Compute is a gateway that includes the models: Claude, GPT, Gemini and open models through one API, routed to the cheapest capable model and provider, with a Europe rule, zero data retention, Entra SSO, per-key budgets, provider allow-lists and an audit log set self-serve.

Portkey vs LiteLLM vs Kong AI Gateway: which suits a regulated company?

All three govern provider keys you bring yourself. Standard Compute is the option that also supplies the models under one DPA, with a Europe rule that keeps retries and fallbacks on approved European endpoints and refuses a request before sending if none qualifies.

Do we need our own OpenAI and Anthropic contracts with Standard Compute?

No. One Standard Compute account gives you Claude, GPT, Gemini and open models through one API, under one DPA you sign in the dashboard.

How do we migrate from Portkey?

Create a company workspace and set your rules, then change the base URL from https://api.portkey.ai/v1 to https://eu.stdcmpt.com/v1, use a Standard Compute key and remove the x-portkey headers.

Does Standard Compute have SSO and SCIM?

Connect Microsoft Entra ID or any SAML identity provider so your people sign in with their work accounts, and Claude Desktop and Claude Code access follows your Entra groups through SCIM provisioning.

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 7 November 2026)

  1. Portkey pricingportkey.ai
  2. Plan feature comparisonportkey.ai
  3. Model Catalogportkey.ai
  4. Audit logsportkey.ai
  5. Budget policiesportkey.ai
  6. SSOportkey.ai
  7. Hybrid deployment architectureportkey.ai
  8. Inference API headersportkey.ai
  9. Claude Code with Portkeyportkey.ai