Portkey
An AI gateway pairing fast model routing with built-in observability, caching, and guardrails.
Portkey is an AI gateway with an open-source core and a hosted option. It routes across providers with fallbacks and load balancing, and folds in observability, caching, and guardrails, so the control plane and the visibility plane are one thing.
For teams that would otherwise wire a gateway and a separate monitoring tool together, that consolidation is the appeal.
Where it fits
A good fit when you want routing and observability from one layer rather than integrating a gateway and a monitoring tool separately.
Where it does not fit
More surface than needed if you only want bare routing and already run your own observability stack.
Alternatives to Portkey
The closest options on the map, and where each fits instead.
-
LiteLLM LLM gateway
The right layer when a system uses several model providers and you want routing, keys, and spend controlled in one place.
Unlike Portkey No hosted APIMaturity: established
-
Cloudflare AI Gateway Edge AI gateway
A fit for teams already on Cloudflare who want caching, limits, and analytics on model traffic with minimal setup.
Unlike Portkey ProprietaryNot self-hostable
-
Bifrost LLM gateway
A fit when you self-host a gateway under heavy traffic and per-request overhead has to stay minimal.
Unlike Portkey No hosted API
-
Requesty Hosted model router
A fit when controlling and forecasting model spend across providers is a priority and a hosted router is acceptable.
Unlike Portkey ProprietaryNot self-hostable
Pairs with
Commonly used alongside it.
