Portkey review

Portkey is a hosted AI gateway and SaaS control plane that sits between an application and model providers. Instead of connecting each app directly to separate model endpoints, teams use Portkey’s unified API to access 1,600+ LLMs. The platform adds routing options such as fallbacks, load balancing, retries and request timeouts.

It also brings operational features around that gateway: observability for logs, traces and usage; guardrails for requests and outputs; and prompt-template management and versioning. The MCP gateway centralizes authentication, access and observability for MCP servers. That makes Portkey an infrastructure layer, not a model or an application framework.

The homepage says Portkey is now PRISMA AIRS AI Gateway and generally available for enterprises. The Production plan is hosted; the Enterprise plan lists private cloud deployment. Teams choosing either route should check how deployment, data handling and their existing model-provider credentials fit their architecture.

The main integration surface named on the homepage is a unified API for accessing 1,600+ LLMs. The gateway supports routing rules, including fallbacks, load balancing, retries and request timeouts. Teams can also use the MCP gateway to centralize authentication, access and observability for MCP servers. These pieces can put a shared control point between application services and model infrastructure.

The homepage does not name programming languages, SDKs, a CLI, webhooks or plugins. Before selecting Portkey, check its developer docs for SDK availability, API compatibility, authentication steps and examples in your application’s language. Confirm how provider-specific parameters and model features pass through the unified API, and how you configure routing and retries.

The platform also includes logs, traces and usage review, plus prompt templates that can be managed and versioned. The developer-facing fit depends on whether those surfaces match your deployment and observability workflows; the feature list alone does not establish integration effort.

The Developer plan costs $0 per month and includes 10,000 recorded logs monthly, three-day log retention, 30-day metrics retention, three prompt templates and community support. It is a testing tier, not an unlimited production allowance. Production costs $49 per month and includes 100,000 recorded logs, 30-day log retention, 90-day metrics retention, unlimited prompt templates, role-based access control and service account API keys.

Production overages are listed at $9 per additional 100,000 requests; the detailed comparison says this applies up to 3 million requests. That is a different meter from the included recorded-log allowance, so confirm exactly how requests and logs count before estimating a bill. Enterprise is custom-priced and lists 10 million+ recorded logs, custom retention, SSO, granular budget and rate limits, private cloud deployment and dedicated onboarding. Enterprise overage pricing is custom. The pricing page lists monthly prices and does not state an annual billing option.

Portkey’s homepage does not publish its software licence or source availability, so teams should not assume the hosted service is an open-source gateway. The Enterprise plan lists private cloud deployment. Separately, a Reddit commenter reports running Portkey self-hosted on Cloudflare Workers and says the region can be chosen; treat that as a user report, not a current deployment guarantee.

The vendor does not publish a data-export path on the vendor's site; ask about exporting logs, traces, prompts and configuration before adoption. Portkey’s unified API can reduce direct provider-specific integrations, but moving away may still mean replacing the gateway endpoint, routing configuration, prompt workflows and observability pipeline. Confirm how much of your application depends on Portkey-specific behavior and what export formats are available.

Production checks should start with the plan limits: 100,000 recorded logs per month and 30-day log retention on Production, versus custom retention and 10 million+ logs on Enterprise. Production overage pricing is based on additional requests, so ask Portkey to clarify how request counts relate to recorded logs. Enterprise lists granular budget and rate limits; confirm the limits that apply to your plan and deployment.

For access control, Production includes role-based access control and service account API keys; Enterprise adds SSO. The homepage does not publish an uptime commitment, so ask for the applicable SLA and incident process. A Reddit commenter reports using Portkey in production for more than four million monthly active users and self-hosting on Cloudflare Workers. Another commenter says EU data residency on SaaS is pricey; verify current regional availability and costs with Portkey before putting regulated workloads on the service.