OmniRoute 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.
OmniRoute
LLM gateway routing one OpenAI-compatible endpoint across 372 providers
new-api
Gateway that unifies LLM providers behind OpenAI, Anthropic and Gemini APIs
Verdict
OmniRoute ranks higher, 87 to 82. Of the 5 score parts we measure for both, OmniRoute leads on 2, new-api on none and 3 are even.
- AdoptionOmniRoute leads by 12 points, 96 to 84.
- FreshnessEven at 100.
- MaintenanceOmniRoute leads by 13 points, 99 to 86.
- Easy to runEven at 67.
- Agent-readyEven at 70.
Pick OmniRoute if you are
Developers pooling free and paid LLM providers for coding tools
- Single /v1 endpoint covers 372 providers with automatic fallback to healthy targets
- Dashboard tracks free-tier pools and quota use at /dashboard/free-tiers
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 | OmniRoute | new-api |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 96, widely used | 84, widely used |
| Freshness | 100, active | 100, active |
| Maintenance | 99, healthy | 86, healthy |
| Easy to run | 67, easy | 67, easy |
| Agent-ready | 70, partly | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 77.4k | 50.1k |
| License | MIT (permissive) | AGPL-3.0 (copyleft) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | Sep 2026 | Oct 2026 |
| Language | TypeScript | Go |
| Docker | Yes | Yes |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Mentioned | Mentioned |
OmniRoute
OmniRoute is a TypeScript gateway that exposes one endpoint at localhost:20128/v1 and routes requests to 372 providers, including many free tiers, with automatic fallback between them. It accepts OpenAI, Claude, Gemini and Responses API formats, and a dashboard handles keys and free-tier quota tracking. Users bring their own provider accounts; the README's free-token figures are estimates, not a grant.
Who it is for: Developers pooling free and paid LLM providers for coding tools
Strengths
- Single /v1 endpoint covers 372 providers with automatic fallback to healthy targets
- Dashboard tracks free-tier pools and quota use at /dashboard/free-tiers
- Works with coding CLIs such as Claude Code, Codex, Cline and Cursor via one config
- Installable via npm, Docker or Electron; MIT licensed; includes MCP and A2A support
Weaknesses
- Free-token headline is an estimate; provider limits and terms change and can lower it
- Providers flagged tos: avoid are excluded from automatic routing by default
- Fresh install may have no eligible route until you connect a provider account
- Large surface (372 providers, 19 routing strategies) makes setup and review heavy
- no GPU
- Docker + Compose
- Needs Provider accounts or API keys, Node.js (npm) or Docker
- Models: OpenAI API, Claude API, Gemini API, Responses API
- port 20128
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.