Pyyan / Compare / Not Diamond vs OpenRouter vs LiteLLM vs Portkey
Not Diamond vs OpenRouter vs LiteLLM vs Portkey
4 of 5Routers & Gateways · verified 13 Aug 2026
×OpenRouterOpenRoutercurrent
| Specification | Not Diamond | OpenRouter | LiteLLM | Portkey |
|---|---|---|---|---|
| Summary | Picks the model per request, not per config. | Biggest catalogue, simplest start. | The self-hosted standard. | Routing plus guardrails and compliance. |
| Added latency | Low | 40–55ms | Self-hosted | 8–20ms |
| Hosting | Managed | Managed | Self | Both |
| Caching | — | — | Redis | Semantic |
| Category | Routers & Gateways | Routers & Gateways | Routers & Gateways | Routers & Gateways |
| Official | Not Diamond ↗ | OpenRouter ↗ | BerriAI ↗ | Portkey ↗ |
Highlighted rows are where these differ.
Not Diamond
- Routes by predicted quality and cost
- No manual model selection
Best for cost/quality tuning.
OpenRouter
- Consolidated billing across every provider
- 40–55ms overhead — 5× the alternatives
Best for prototyping.
LiteLLM
- Budget controls and Redis caching
- Zero marginal cost, you run it
Best for production.
Portkey
- Best caching implementation
- Prompt management and audit trail
Best for regulated teams.