Pyyan / Compare / LiteLLM vs OpenRouter vs Requesty vs Portkey vs Cloudflare AI Gateway
LiteLLM vs OpenRouter vs Requesty vs Portkey vs Cloudflare AI Gateway
5 of 5Routers & Gateways · verified 13 Aug 2026
| Specification | LiteLLM | OpenRouter | Requesty | Portkey | Cloudflare AI Gateway |
|---|---|---|---|---|---|
| Summary | The self-hosted standard. | Biggest catalogue, simplest start. | Lowest measured overhead. | Routing plus guardrails and compliance. | Edge gateway with free core features. |
| Added latency | Self-hosted | 40–55ms | 8ms P50 | 8–20ms | Edge |
| Hosting | Self | Managed | Managed | Both | Managed |
| Caching | Redis | — | — | Semantic | — |
| Category | Routers & Gateways | Routers & Gateways | Routers & Gateways | Routers & Gateways | Routers & Gateways |
| Official | BerriAI ↗ | OpenRouter ↗ | Requesty ↗ | Portkey ↗ | Cloudflare ↗ |
Highlighted rows are where these differ.
LiteLLM
- Budget controls and Redis caching
- Zero marginal cost, you run it
Best for production.
OpenRouter
- Consolidated billing across every provider
- 40–55ms overhead — 5× the alternatives
Best for prototyping.
Portkey
- Best caching implementation
- Prompt management and audit trail
Best for regulated teams.
Cloudflare AI Gateway
- Analytics and rate limiting free
- BYOK, dynamic routing, DLP
Best for Cloudflare stacks.