LiteLLM vs OpenRouter
Both are alternatives to Portkey. Here's how they stack up — verified facts, no spin.
Also searched as OpenRouter vs LiteLLM — same comparison, one verdict.
LiteLLM is open source (MIT (core); enterprise/ directory under a separate commercial licence) 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.
LiteLLM
TOP PICKOne OpenAI-compatible API in front of 100+ providers, running on your own box.
LiteLLM is the de facto open gateway for this layer: a proxy that exposes an OpenAI-compatible endpoint in front of 100+ providers, with virtual keys, per-team budgets, rate limits, fallbacks and logging. You run it, so prompts never leave your infrastructure and there is zero markup on token spend — you pay the model providers directly. At 55k GitHub stars with commits landing daily it is the most widely adopted option here. Licensing is worth reading precisely: the core is MIT, while everything under the repository's enterprise/ directory carries a separate commercial licence.
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
10 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.
| LiteLLM | OpenRouter | |
|---|---|---|
| Sovereignty ScoreOur transparent 0–100 composite for data ownership and exit cost. | 90 | 32 |
| Open source | Yes | No |
| Self-hostable | Yes | No |
| Local-first data | Yes | No |
| License | MIT (core); enterprise/ directory under a separate commercial licence | Proprietary (hosted service) |
| Pricing | Free and self-hosted — you pay the model providers directly with no markup, plus hosting for a small VM (roughly $20–50/month). A paid enterprise tier exists for SSO, audit logs and support. | No subscription — pay-as-you-go per token at provider rates plus a small margin. Some free models are available. |
| RAM to run it wellThe figure that actually matters, not the vendor's minimum. | 2 GB | — |
| Realistic running costWhat the box costs each month if you run it yourself. | $12–24/mo, against LLM gateway products charging per request | — |
| Setup timeHonest first-install estimate, not the marketing quickstart. | 1 hour | — |
| Ongoing maintenanceThe part nobody budgets for. | Low, but it is now in the path of every model call you make. | — |
LiteLLM is Macrostack's recommended Portkey alternative, so it's our pick here.
LiteLLM
Strengths
- +Zero markup — provider tokens are billed to you at cost
- +Prompts and completions never leave your infrastructure
- +Virtual keys, per-team budgets and rate limits built in
- +100+ providers behind one OpenAI-compatible endpoint; 55k stars, daily commits
Trade-offs
- −You run it: deployment, upgrades, monitoring and uptime are yours
- −Observability is basic out of the box — expect to pair it with a tracing tool
- −The MIT core stops at the enterprise/ directory; SSO and audit logging sit behind a commercial licence
- −A proxy you operate is another production dependency to keep healthy
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 LiteLLM
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 run it: deployment, upgrades, monitoring and uptime are yours, 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.
What it takes to run these yourself
Real requirements and honest running costs, not the vendor quickstart.
LiteLLM vs OpenRouter — common questions
Is LiteLLM a better fit than OpenRouter for llm gateways & routing?
It depends on what you are optimising for, and the honest split is this: LiteLLM scores 90 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?
LiteLLM 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 LiteLLM?
LiteLLM can be self-hosted; OpenRouter cannot, so it stays on the vendor's infrastructure whatever you do.
Are LiteLLM 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.