OpenRouter vs LiteLLM: the honest comparison
The short answer
Edition v2026.Q3 · pricing and status verified 2026-08-06.
Choose OpenRouter for any team that wants every model behind one key and one invoice today, with zero infrastructure to run. Choose LiteLLM for teams that need the router inside their own VPC — keys, logs, and spend controls that never leave your infrastructure.
On the elems table, OpenRouter holds seat #1 of the Model Router element and LiteLLM holds #2 — this is the closest call in the category, and the honest answer depends on which trade-off you can live with.
The case for each
1OpenRouterOpenRouter, Inc.
Pass-through token pricing (0% markup) · 5.5% fee on credit purchases ($0.80 min; 5% via crypto) · BYOK free to 1M req/mo, then 5%Best for Any team that wants every model behind one key and one invoice today, with zero infrastructure to run.
Watch That 5.5% compounds painfully at volume — heavy spenders graduate to direct provider contracts or BYOK (which itself costs 5% past 1M req/mo). Fully managed only: your entire model traffic transits a single startup, and critics argue frontier-lab consolidation erodes the aggregator's reason to exist.
2LiteLLMBerriAI (YC W23; MIT OSS)
Open source free forever (self-host) · Enterprise custom annual, sized to request capacity — never per-token · 30-day trialBest for Teams that need the router inside their own VPC — keys, logs, and spend controls that never leave your infrastructure.
Watch You run it — upgrades, scaling, and a famously sprawling codebase (2.5k open PRs) are your problem. Performance numbers are vendor-published; rivals (Bifrost) built entire marketing campaigns on LiteLLM's Python-era overhead. Enterprise pricing is quote-only and opaque.
OpenRouter vs LiteLLM: side by side
Edition v2026.Q3 · verified 2026-08-06.
| OpenRouter | LiteLLM | |
|---|---|---|
| Take rate / fees | 0% markup · 5.5% credit fee · BYOK 5% >1M req | Free · enterprise custom (not per-token) |
| Hosting | Managed edge | Self-host (+ cloud) |
| Open source | No | Yes (MIT) |
| Catalog | 400+ models · 60+ providers | 140+ providers · ~1,900 models (claimed) |
| Added latency | ~25 ms | 0.66 ms p99 (vendor) |
| Routing depth | Fallbacks · price/throughput sorts · ZDR routing | Fallbacks · load-balance · budgets · caching |
| Enterprise | Workspaces · spend mgmt · ZDR | SSO · SCIM · audit · air-gap |
What each side won't tell you
OpenRouter: That 5.5% compounds painfully at volume — heavy spenders graduate to direct provider contracts or BYOK (which itself costs 5% past 1M req/mo). Fully managed only: your entire model traffic transits a single startup, and critics argue frontier-lab consolidation erodes the aggregator's reason to exist.
LiteLLM: You run it — upgrades, scaling, and a famously sprawling codebase (2.5k open PRs) are your problem. Performance numbers are vendor-published; rivals (Bifrost) built entire marketing campaigns on LiteLLM's Python-era overhead. Enterprise pricing is quote-only and opaque.
If it's neither
The rest of the top five: Vercel AI Gateway (zero-markup managed gateway) · Cloudflare AI Gateway (free edge control plane) · Portkey (governance gateway, now panw). The complete field — 20 more tools including the graveyard — is on the element page.
This analysis is drawn from the Model Router element dossier — the ranked top 5, the comparison matrix, and the complete field of 20 more tools live there, with every source. Data: rt.json (CC BY 4.0).
Every claim above is dated and sourced from the elems dossiers — 1,421 tools tracked across 58 categories, verified 2026-08-06, including the 276 we found dead, renamed, acquired, or sunsetting. Rankings are editorial, never paid — the charter.
Build your stack in 5 questions →