LiteLLM vs OpenRouter
Of the 987 makers' products we know the LLM API of, 65 chose OpenRouter (7%) and 21 LiteLLM (2%); 1 uses both. Among the 281 launched in 2026, LiteLLM is in 2% and OpenRouter in 10%, against 1% and 3% of those launched in 2024 or earlier.
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 · 139 open-source projects | 65 makers' products · 41 open-source projects |
|---|---|---|
| Downloads | 20.9M/wk | 2.8M/wk5.1× 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 |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for LLM API.
| Framework | |||
|---|---|---|---|
| 3 | 17 | All 301 Next.js products' picks → | |
| 1 | 2 | All 38 React products' picks → | |
| 1 | 2 | All 27 Astro products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the LLM API decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2022 or earlier | 2% 1 | 5% 3 | 66 |
| 2023 | 3% 1 | 5% 2 | 37 |
| 2024 | 1% 2 | 2% 5 | 222 |
| 2025 | 3% 7 | 6% 16 | 273 |
| 2026 | 2% 7 | 10% 27 | 281 |
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.
It simplified the AI implementation and enabled support for 100+ LLMs without dealing with multiple provider APIs.
Big fan of liteLLM: one API for OpenAI/Anthropic/Groq/etc. Makes multi-model stacks painless
We needed a simple way to access and switch between different AI models while building Shape's agent. OpenRouter made that much easier during development.
One API, every model. We route each email task — triage, drafting, summarizing — to the right model per tier without juggling providers or keys. Fallbacks and cost control out of the box. It's the backbone of our agent.
As I'm using multiple models from multiple providers, unifying an API key was very important, which Open Router made very easy.
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
Who uses each
What makers pair each with
Neither quite right?
See the whole LLM API decision →Questions
LiteLLM or OpenRouter: which do makers choose?
Of the 987 makers' products we know the LLM API of, 65 chose OpenRouter (7%) and 21 LiteLLM (2%); 1 uses both. Among the 281 launched in 2026, LiteLLM is in 2% and OpenRouter in 10%, against 1% and 3% of those launched in 2024 or earlier. Choose LiteLLM if you want that routing and spend control but self-hosted, with keys and logs on your servers; choose OpenRouter if you want to try or mix many models with one key and one bill, and fall back when a provider is down.
When should I pick LiteLLM over OpenRouter?
Pick LiteLLM if: You want that routing and spend control but self-hosted, with keys and logs on your servers.
When should I pick OpenRouter over LiteLLM?
Pick OpenRouter if: You want to try or mix many models with one key and one bill, and fall back when a provider is down.

