If you’re comparing OpenRouter and Portkey, the real question is whether you want something that routes requests for you, or something that governs the requests you already make.

OpenRouter is a managed routing network. You buy credits, call one OpenAI-compatible endpoint, and it routes across 70+ providers with automatic failover. You never hold a provider key. Portkey is an AI control plane, now part of Palo Alto Networks after a 2026 acquisition. It sits in front of the provider keys you already have and adds governance, prompt management, guardrails, and observability.

Pick OpenRouter when you want model access and failover with no infrastructure. Pick Portkey when you need a governance layer over the provider accounts you already run.

Route across providers, or govern your own keys

OpenRouter owns the path to the model. Your app calls https://openrouter.ai/api/v1, OpenRouter picks a provider, and forwards the request on credits you’ve already bought. There are no per-provider accounts to manage, and a request that fails on one provider falls over to another automatically.

Portkey owns the layer in front of your keys. You bring your own provider credentials (OpenAI, Anthropic, Azure, and the rest), store them as virtual keys, and Portkey routes, caches, and logs every call. Its open-source gateway has 12K+ GitHub stars and installs in 3 lines of code, and you can self-host it or run the managed version.

With OpenRouter you offload provider relationships entirely; with Portkey you keep them and wrap them in policy.

Count models, but count the right thing

Portkey advertises access to 1,600+ LLMs through its unified API. OpenRouter lists 300+ models across 70+ providers, including 20+ free models for evaluation. The raw numbers favor Portkey, but they measure different things.

Portkey’s count is breadth of models you can address once you’ve supplied the keys. OpenRouter’s count is models it actively routes to, with credits, load balancing, and cross-provider failover handled for you. Its Auto Router, powered by NotDiamond, can even pick a model per prompt, and provider routing lets you filter by price, throughput, latency, data policy, and quantization.

Count whichever number you like. The decision still rests on whether you want a network that routes for you or a unified front end over the provider accounts you run.

Match observability and governance to your team

Portkey centers on governance. It ships in-product logs, traces, and dashboards with tiered retention (3 days on the free Developer plan, 30 days on Production, custom on Enterprise), plus prompt templates with a playground, role-based access control, budget and rate limits, and guardrails that include PII redaction. For a platform team standardizing many internal apps, that control plane is the point.

OpenRouter takes a lighter approach to observability. Rather than store your logs long-term, Broadcast streams traces to the platforms you already run, including Datadog, Langfuse, LangSmith, Braintrust, OpenTelemetry, and S3. Workspaces add per-team organization and budgets for teams that want structure across many internal apps.

On compliance, both hold SOC 2 Type 2 and support GDPR. OpenRouter adds Zero Data Retention and EU in-region routing for enterprise accounts, with its report at trust.openrouter.ai. Portkey adds HIPAA and custom BAAs on Enterprise, along with VPC hosting and data isolation. Teams that want data residency without running infrastructure point to OpenRouter.

Pick a pricing model that matches your volume

The two price along different axes. OpenRouter passes provider pricing through at 0% markup, then charges a 5.5% platform fee on credit purchases with a $0.80 minimum. Bring Your Own Key drops that to 5%, and the first 1 million requests each month are waived. You pay for usage, nothing else.

Portkey prices on logs and features. Its Developer tier is free with 10K recorded logs a month, though Portkey marks it as unsuitable for production. Production is $49/month for 100K logs (plus $9 per additional 100K up to 3 million) and adds RBAC and guardrails. Enterprise is custom, with HIPAA, SSO, private deployment, and longer retention. The open-source gateway is free to self-host if you’d rather run it yourself.

Net cost depends on where your weight sits. Heavy model spend with provider keys already in hand often favors Portkey’s self-hosted gateway; usage you’d rather not meter or operate favors OpenRouter’s pay-as-you-go.

Use both, or start where the pain is

These aren’t mutually exclusive. You can point Portkey at OpenRouter as an upstream provider, putting Portkey’s governance and prompt management in front of OpenRouter’s routing network. OpenRouter also lists Portkey as an upcoming broadcast destination, so traces will flow the other direction too.

If you’re weighing more options, our LLM gateway comparison covers LiteLLM, Helicone, Cloudflare AI Gateway, and others.

Frequently asked questions

Is Portkey the same kind of tool as OpenRouter?

They overlap on a unified API but solve different problems. OpenRouter is a managed routing network: you buy credits and it routes across 70+ providers with automatic failover, no provider keys required. Portkey is a control plane that sits in front of the provider keys you already hold, adding governance, prompt management, and in-product observability.

Did Palo Alto Networks acquire Portkey?

Yes. Palo Alto Networks completed its acquisition of Portkey in 2026, folding it into the company’s AI security portfolio. Portkey continues to operate its gateway, including the open-source version.

How do OpenRouter and Portkey compare on compliance?

Both hold SOC 2 Type 2 and support GDPR. OpenRouter adds Zero Data Retention and EU in-region routing for enterprise accounts. Portkey offers HIPAA and custom BAAs on its Enterprise plan. For specific certification requirements, check each platform’s trust center.

Which one is cheaper?

It depends on volume. OpenRouter charges a 5.5% platform fee on credit purchases (5% with Bring Your Own Key, first 1 million requests each month waived) and 0% markup on provider prices. Portkey is free to self-host or on its Developer tier, then $49/month for Production. High-volume teams that already hold provider keys often run Portkey’s open-source gateway; teams that want managed routing without operating anything pick OpenRouter.

Can I use OpenRouter and Portkey together?

Yes. You can point Portkey at OpenRouter as one of its upstream providers, putting Portkey’s governance and observability in front of OpenRouter’s routing network. OpenRouter also lists Portkey as an upcoming broadcast destination for sending traces.