LiteLLM vs OpenRouter
Two gateway (many providers, one API) options for LLM API. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- You want that routing and spend control but self-hosted, with keys and logs on your servers
Use it whenYou want keys and request data to stay on your infrastructure.
Trade-offYou deploy, monitor and upgrade it yourself; SSO and audit logs are in the paid enterprise tier.
- You want to try or mix many models with one key and one bill, and fall back when a provider is down
Use it whenYou want to compare models quickly or offer users a model picker.
Trade-offA fee on top of provider prices, and your traffic and data pass through a third party.
At a glance
| Used by | 21 makers' products · 97 open-source projects | 61 makers' products · 31 open-source projects |
|---|---|---|
| Downloads | 148.1M/wk | 2.1M/wk4.8× vs npm |
| Pricing | Free and open source to self-host; paid enterprise tier adds SSO, audit logs and support. · paid from Contact sales | Pay per token at provider prices plus a 5.5% fee on credits; 25+ free models with daily rate limits. · paid from Pay per token + 5.5% fee on credits |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | No |
What makers say
Makers on using it for LLM API, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
We use LiteLLM mainly so we’re not tied to a single model provider. Makes it super easy to switch models or add fallbacks when running AI services for clients.
LiteLLM is amazing and makes managing LLM clients incredibly easy. highly recommended for teams integrating multiple LLM providers in their system.
LiteLLM is amazing and makes managing LLM clients incredibly easy. highly recommended for teams integrating multiple LLM providers in their system.
Talespinner uses OpenRouter to allow for switching between different language models. They make it super easy to do this, because they offer one API format for all language models.
OpenRouter made it seamless to integrate multiple LLMs with unified APIs. It played a key role in enabling flexible model orchestration and reliable responses in Codentis.
Big thanks to OpenRouter — it lets us route every AI generation to the right model effortlessly, which is what makes our AI email builder feel instant and smart.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- One OpenAI-compatible API across providers lets teams switch or add models without rewriting application code. PHHN
- Fallbacks, routing and model aliases let a single endpoint swap backends, including local models with cloud fallback. PHPH 2HNHN 2
- Per-customer token spend and cost tracking is built in and is a main reason teams deploy it. PHHNHN 2
- The codebase and dependency tree are heavy, and the proxy can use gigabytes of memory. HNHN 2HN 3HN 4
- The proxy adds noticeable latency compared with lighter Go or Rust gateways. HNHN 2HN 3HN 4
- A supply-chain compromise of published LiteLLM versions exposed credentials in many CI pipelines. HNHN 2HN 3HN 4

