Portkey Gateway (self-hosted) vs OpenRouter
Both are alternatives to Portkey. Here's how they stack up — verified facts, no spin.
Also searched as OpenRouter vs Portkey Gateway (self-hosted) — same comparison, one verdict.
Portkey Gateway (self-hosted) is open source (MIT) and OpenRouter is not (Proprietary (hosted service)) — so the real question is whether you want to own the llm gateways & routing stack or rent it.
Portkey Gateway (self-hosted)
Portkey's own routing engine, MIT-licensed and running on your hardware.
Worth knowing before you buy the platform: Portkey publishes its gateway as open source under the MIT licence, so the routing engine — 250+ models, failover, load balancing, caching — can be self-hosted at no cost. What the subscription adds is the hosted control plane: dashboards, prompt management, guardrails, analytics and support. If your requirement is the routing and not the console, this is the same engine without the bill or the third-party data path.
OpenRouter
One key, hundreds of models, nothing to run — the honest hosted pick.
OpenRouter is a hosted router: a single API key and one OpenAI-compatible endpoint in front of hundreds of models across providers, with automatic fallback and a unified bill. There is nothing to deploy and no subscription — you pay per token with a small margin on top of provider rates. If what you actually wanted was to stop juggling five provider accounts, this solves it in an afternoon and is frequently the right answer even for teams who could self-host.
Side by side
6 points of comparison, every one read from a verified field. Green marks the side that wins a row outright. A dash means we do not hold that fact — never that it is zero.
| Portkey Gateway (self-hosted) | OpenRouter | |
|---|---|---|
| Sovereignty ScoreOur transparent 0–100 composite for data ownership and exit cost. | 86 | 32 |
| Open source | Yes | No |
| Self-hostable | Yes | No |
| Local-first data | Yes | No |
| License | MIT | Proprietary (hosted service) |
| Pricing | Free — the gateway is MIT-licensed. You pay only your model providers and your own hosting. | No subscription — pay-as-you-go per token at provider rates plus a small margin. Some free models are available. |
Portkey Gateway (self-hosted) edges it on the Sovereignty Score, but the right pick depends on the trade-offs below.
Portkey Gateway (self-hosted)
Strengths
- +MIT licence on the full routing engine
- +Same 250+ model coverage as the hosted product
- +The lowest-friction exit from Portkey's paid tier — same engine, same config shape
- +No third party in the request path when self-hosted
Trade-offs
- −You lose the dashboards, prompt management and guardrails that justify the subscription
- −Development cadence is slower than LiteLLM's
- −Smaller self-hosting community, so fewer worked examples when something breaks
- −You are self-hosting a vendor's open core — feature direction still follows their commercial product
OpenRouter
Strengths
- +Zero operations: one key, one endpoint, hundreds of models
- +No monthly fee — you pay only for tokens used
- +Unified billing across providers, with automatic fallback
- +The fastest way to test many models without opening accounts everywhere
Trade-offs
- −Hosted and proprietary: every prompt transits OpenRouter
- −A margin on token spend rather than provider cost
- −No self-hosting path at all
- −Score of 32 reflects a closed hosted service — a transparency lens, not a judgement on quality
Which one fits you
The trade-offs above, turned into a decision. Find the line that describes your team.
Choose Portkey Gateway (self-hosted)
if you want the source and the option to fork it, and you would rather run it on your own hardware, and your data should stay on machines you control.
Choose OpenRouter
if zero operations: one key, one endpoint, hundreds of models.
Neither, yet
if both carry a real cost you should weigh first — you lose the dashboards, prompt management and guardrails that justify the subscription, and hosted and proprietary: every prompt transits OpenRouter. If either of those is a dealbreaker for your team, the shortlist is wrong rather than the choice.
Portkey Gateway (self-hosted) vs OpenRouter — common questions
Is Portkey Gateway (self-hosted) a better fit than OpenRouter for llm gateways & routing?
It depends on what you are optimising for, and the honest split is this: Portkey Gateway (self-hosted) scores 86 to OpenRouter's 32 on data ownership and exit cost, so it is the safer choice if you care about being able to leave. OpenRouter earns its place on a different axis — zero operations: one key, one endpoint, hundreds of models. Neither is a wrong answer for every team; the table above is the actual comparison.
What happens if we want to switch later?
Portkey Gateway (self-hosted) keeps its data local or in open formats, so leaving is an export rather than a negotiation. OpenRouter keeps your data on its own infrastructure, which is the part to plan for: confirm the export path before you commit, not when you are already trying to leave.
Can I self-host Portkey Gateway (self-hosted)?
Portkey Gateway (self-hosted) can be self-hosted; OpenRouter cannot, so it stays on the vendor's infrastructure whatever you do.
Are Portkey Gateway (self-hosted) and OpenRouter both alternatives to Portkey?
Yes — both appear in our Portkey comparison, which is why they are worth putting side by side. People usually arrive here already having decided to move off Portkey and now choosing between the two replacements, which is a narrower and much easier question.
Related alternative guides
Facts verified 2026-07-30. Licenses and pricing change — spotted something out of date? That's a correction we want.