LiteLLM vs new-api
Two of the top projects in Gateways, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.
LiteLLM
OpenAI-format gateway and Python SDK for calling 100+ LLM providers
new-api
Gateway that unifies LLM providers behind OpenAI, Anthropic and Gemini APIs
Verdict
LiteLLM ranks higher, 89 to 82. Of the 5 score parts we measure for both, LiteLLM leads on 2, new-api on 2 and 1 is even.
- AdoptionLiteLLM leads by 6 points, 90 to 84.
- FreshnessEven at 100.
- Maintenancenew-api leads by 3 points, 86 to 83: close to even.
- Easy to runLiteLLM leads by 33 points, 100 to 67: a wide gap.
- Agent-readynew-api leads by 40 points, 70 to 30: a wide gap.
Pick LiteLLM if you are
Teams routing many LLM providers through one OpenAI-compatible endpoint
- Covers chat, responses, embeddings, images, audio, batches and rerank endpoints across many providers
- Works as an in-process Python SDK or a standalone proxy server
Pick new-api if you are
Teams and operators sharing and metering access to multiple LLM providers
- Converts between OpenAI, Anthropic Messages and Gemini request formats via RelayKit
- Channel priorities, weights, retries and multiple upstream keys per channel
| What we compare | LiteLLM | new-api |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 90, widely used | 84, widely used |
| Freshness | 100, active | 100, active |
| Maintenance | 83, healthy | 86, healthy |
| Easy to run | 100, very easy | 67, easy |
| Agent-ready | 30, minimal | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 61.4k | 50.1k |
| License | custom license (read the license) | AGPL-3.0 (copyleft) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Oct 2026 | Oct 2026 |
| Language | Python | Go |
| Docker | Yes | Yes |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Mentioned | Mentioned |
LiteLLM
LiteLLM translates requests in the OpenAI format to more than 100 LLM providers, and runs either as a Python SDK or as a proxy server. The proxy adds virtual keys, spend tracking, guardrails, load balancing and an admin dashboard. It also fronts A2A agents and MCP servers, and the README cites 8ms P95 latency at 1k RPS.
Who it is for: Teams routing many LLM providers through one OpenAI-compatible endpoint
Strengths
- Covers chat, responses, embeddings, images, audio, batches and rerank endpoints across many providers
- Works as an in-process Python SDK or a standalone proxy server
- Proxy includes virtual keys, spend tracking, guardrails and load balancing
- Also fronts MCP servers and A2A agents through the same gateway
Weaknesses
- Endpoint support varies per provider; the README table shows many gaps
- License is detected as NOASSERTION; check the repo's license files before use
- An Enterprise tier exists; the README excerpt does not say which features are paid
- Two SDK packages (litellm, litellm-core) overlap and cannot be installed together
- no GPU
- Docker + Compose
- Compose runs PostgreSQL
- Models: OpenAI, Anthropic, Gemini, AWS Bedrock, Azure
- port 4000
new-api
New API is a Go and Gin gateway that connects upstream providers such as OpenAI, Anthropic, Gemini, Azure OpenAI, AWS Bedrock, Vertex AI, DeepSeek and Qwen. It exposes them through OpenAI Chat/Responses, Anthropic Messages and Gemini endpoints. A web console handles channel routing, users, quotas, pricing and usage logs. It runs on SQLite by default, or on MySQL or PostgreSQL with optional Redis.
Who it is for: Teams and operators sharing and metering access to multiple LLM providers
Strengths
- Converts between OpenAI, Anthropic Messages and Gemini request formats via RelayKit
- Channel priorities, weights, retries and multiple upstream keys per channel
- Per-user quotas, subscriptions, usage logs and expression-based pricing
- Starts on SQLite with one container; Compose file adds PostgreSQL and Redis
Weaknesses
- AGPL-3.0 with extra terms requiring attribution and a visible project link in modified UIs
- Protocol conversion is not exact; tools and fields may not map across protocols
- Multi-node setups need shared database, secrets and Redis, or rate limits count per node
- Public or resale use brings filing and compliance duties the README leaves to the operator
- no GPU
- Docker + Compose
- Needs SQLite, MySQL >= 5.7.8 or PostgreSQL >= 9.6, Redis (optional), ClickHouse (optional, log database)
- Models: OpenAI, Anthropic, Google Gemini, Azure OpenAI, AWS Bedrock
- port 3000
More in Gateways
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.