Comparison · OpenRouter vs Portkey

OpenRouter vs Portkey: routing and governance

OpenRouter is a model marketplace that routes one request across many providers. Portkey is an AI gateway that puts policy, observability and key management around models you already use. The choice is catalogue convenience versus control.

Short answer. Choose OpenRouter when you want the widest catalogue, fast experimentation and one bill across providers. Choose Portkey when you need guardrails, per-team governance, deep traces and a gateway that can front your existing cloud contracts. OpenRouter charges a 5.5% fee on Standard credit purchases and includes 600+ models; Portkey's managed gateway has historically offered a free tier for small volumes, with enterprise pricing above it.

Side by side

DimensionOpenRouterPortkey
CategoryModel marketplace and routerAI gateway and control plane
Catalogue600+ models, 80+ providers1,600+ models per Portkey docs
BillingProvider list price + 5.5% credit fee (8% Business)Gateway subscription + provider usage; open-source gateway free
BYOK$25K/month list-price inference free, then 5%Provider keys stored in gateway; BYOK supported
RoutingAuto-routing, provider pinning, fallbacksConditional routing, fallbacks, load balancing, canary
GuardrailsModeration, data-policy and ZDR routing, budgetsPII redaction, content filters, custom checks, RBAC
ObservabilityActivity logs and usage exportTraces, latency, cost attribution, audit logs
Self-hostingNoYes, open-source gateway
Best forFast model access and price comparisonGoverned production traffic across teams

Sources: OpenRouter pricing and docs, Portkey docs and pricing page, checked 20 November 2026. Fees and plan features change; confirm before signing.

Catalogue and model access

OpenRouter's advantage is breadth. A single key reaches 600+ models from 80+ providers, including free variants of some models. You can compare price and latency per model, pin a provider, or let OpenRouter route to whichever endpoint is available. That is useful when a product needs a fallback model for capacity reasons, or when a team wants to test several models without opening accounts with each vendor.

Portkey also advertises a large catalogue, but its centre of gravity is the gateway layer. You connect the providers you already pay for, keep those contracts, and route through Portkey for policy, retries and tracing. If your procurement team has already approved two model vendors, Portkey lets you keep those relationships instead of moving spend to a marketplace balance.

BYOK and pricing

OpenRouter's Standard plan adds a 5.5% fee when you buy credits; Business raises that to 8% and adds admin features. Inference itself is billed at the provider's list price. BYOK is generous on paper: the first $25,000 per month of list-price inference runs without an OpenRouter fee, then a 5% fee applies. Enterprise fees are negotiated.

Portkey's open-source gateway is free to run. The managed product has historically included a free tier of 10,000 requests per month, with paid plans for higher volume and enterprise features. Portkey's public site now presents the product as Prisma AIRS AI Gateway under Palo Alto Networks, and the current commercial page is sales-led rather than a public rate card. Treat the old per-request tiers as historical and confirm the current contract.

Compare the whole bill, not the 5.5% fee: provider tokens, platform fee or subscription, observability retention, support and the engineering time to run a gateway. A percentage fee can be cheaper at low volume; a platform contract often wins at high volume.

Routing and reliability

OpenRouter routes by model and provider, supports automatic fallbacks, and does not charge for failed attempts. Its Zero Completion Insurance covers empty responses with no finish reason. Business and Enterprise plans add EU and US in-region routing, and Enterprise adds private endpoints. Those are meaningful controls if data location is part of your review.

Portkey's routing is more explicit: conditional routes based on request metadata, weighted load balancing, canary releases, retries and fallbacks. Teams use it to send 5% of traffic to a new model, compare quality, then shift the weight. It can also cache identical requests, which changes both latency and cost.

Both add a network hop. Portkey documents roughly 20–40 ms of edge latency; OpenRouter's overhead varies by provider and region. Measure p50 and p95 yourself: a router that improves availability can still hurt a latency-sensitive endpoint.

Guardrails and governance

This is where the products diverge most. OpenRouter gives you moderation, provider data policies, zero-data-retention routing and spend controls. It is not a policy engine for redacting a customer's national ID before the model sees it.

Portkey puts guardrails in the request path: PII detection and redaction, content filters, custom webhook checks, allow/deny rules and role-based access. It also records traces and cost by team, which is what finance and security usually ask for after the first invoice. SSO, audit logs and private deployment are enterprise features, so verify which tier includes them.

If your requirement is "one key, many models, low friction", OpenRouter is sufficient. If it is "every prompt is inspected, every key is scoped, and every team gets a budget and a trace", Portkey is built for that job. Neither replaces your application's own authorization checks.

Migration

Both are OpenAI-compatible, so the SDK usually stays. Change the base URL, key and model ID, then run a replay of production prompts before cutting over.

from openai import OpenAI

# OpenRouter
openrouter = OpenAI(
    api_key="OPENROUTER_KEY",
    base_url="https://openrouter.ai/api/v1",
)

# Portkey: the provider key stays with the gateway; the Portkey key authenticates the call.
portkey = OpenAI(
    api_key="PROVIDER_KEY",
    base_url="https://api.portkey.ai/v1",
    default_headers={
        "x-portkey-api-key": "PORTKEY_KEY",
        "x-portkey-provider": "openai",
    },
)

# Same request shape. Pin a model when you need reproducibility.
resp = openrouter.chat.completions.create(
    model="openai/gpt-4o-mini",
    messages=[{"role": "user", "content": "Return the word ready."}],
)
print(resp.choices[0].message.content)

Migration checks: tool calling, JSON mode, streaming, image inputs, token accounting and error codes. Keep the old route available for one billing cycle so you can compare cost and quality on real traffic.

Which one to choose

  • OpenRouter for a small team that wants one account, many models, and a predictable percentage fee.
  • Portkey for a platform team that must enforce policy, attribute cost and keep existing provider contracts.
  • Both is possible but usually redundant: put Portkey in front of the providers you approve, and use OpenRouter only for experiments.
  • Neither if you need a flat monthly bill and a single OpenAI-compatible endpoint; compare Plugsky's plans.

FAQ

Is OpenRouter cheaper than Portkey?

They charge differently. OpenRouter bills provider list price plus a 5.5% fee on Standard credit purchases, or 8% on Business. Portkey charges for its gateway and observability product, with a free tier for small volumes. Compare the all-in bill at your request volume, not the headline fee.

Does OpenRouter have guardrails?

OpenRouter offers moderation, data-policy routing, zero-data-retention routing and spend controls, but it is not a full guardrail platform. Portkey provides PII redaction, content filters, custom checks and policy enforcement in the request path.

Can I bring my own provider keys?

Yes on both. OpenRouter includes $25,000 per month of list-price inference through BYOK with no OpenRouter fee, then charges 5%. Portkey stores provider keys in the gateway and supports BYOK on managed and self-hosted deployments.

Which one is easier to migrate to?

Both expose OpenAI-compatible endpoints, so the SDK usually stays and the base URL, key and model ID change. Portkey can also sit in front of an existing provider without moving your model traffic to a marketplace.

Is Portkey still available as an independent product?

Portkey's documentation now identifies the product as Prisma AIRS AI Gateway, following its move into Palo Alto Networks. The open-source gateway remains available, but commercial packaging and pricing are enterprise-led. Confirm current terms with the vendor.

Reviewed 20 November 2026. OpenRouter fees, limits and features were checked against OpenRouter pricing and OpenRouter docs; Portkey features were checked against Portkey docs and its current product page. Portkey's commercial packaging is changing, so verify pricing and data terms directly. This page is editorial and is not paid placement.