Skip to main content

Palo Alto NetworksAI Gateway

Portkey

Portkey's gateway puts one OpenAI-compatible API, fallbacks, load balancing, request logs, and guardrails in front of a team's own model API keys, as a hosted service, a hybrid data plane in your VPC, or an MIT-licensed open-source gateway. Palo Alto Networks completed its purchase on May 29, 2026 and sells it as Prisma AIRS AI Gateway.

The 30-Second Take

Pick Portkey if security wants every model call logged, filtered and audited without running a logging stack.

It puts one API, fallbacks, request logs and guardrails in front of your own model keys. Palo Alto Networks bought it in May 2026 and sells it as Prisma AIRS AI Gateway, while the portkey.ai plans stay on sale.

Best fit
Platform teams that call model makers on their own keys and want hosted request logs, guardrails, and audit logs.
Main constraint
Budgets, SSO, and audit logs need Enterprise, and the open-source gateway has shipped no release since January 12, 2026.
First move
Run a Production workspace on Portkey cloud against the routes you use, and ask Palo Alto Networks for Enterprise terms in writing.

Why

Watch the gaps: budgets, SSO and audit logs need Enterprise, and a cache change on Portkey's cloud took a production platform down in 2025. Avoid self-hosting the open-source gateway while a July 2026 SSRF bypass stays open.

Practitioner sentiment, all practitioners0 Mixed

47 practitioners, 62 sources reviewed, Updated Oct 30, 2026How this is measured

Read the GILD Review
Save a product your organization uses.Keep up with Portkey without adding it to your stack.Visit Website
Operating stack
AI Application Platform

Comparisons

How does Portkey compare with the alternatives?

  1. Portkey vs OpenRouter

    • AI Gateways

    Pick Portkey for recorded request logs, audit logs, and a data plane in your VPC on your own model keys, and canary its cache changes: one took a production platform down in 2025. Pick OpenRouter to buy 500+ models through one balance with a fee on credit purchases.

  2. Portkey vs LiteLLM

    • AI Gateways

    Pick Portkey, now Palo Alto Networks' Prisma AIRS AI Gateway, for hosted observability priced by recorded logs. Pick LiteLLM for free key budgets in a gateway you run yourself.

Operator Insights

What are teams learning from building on Portkey and running it in production?

See all 8 operator accounts

Buying and deployment

What a team building on it should verify before production traffic grows.

Sourced from Portkey documentation

How you buy it

US$49 a month

Production includes 100,000 recorded logs; Developer is free for prototypes and Enterprise is custom.

Source 1, Portkey, Portkey pricing: Portkey pricingSource 5, portkey.ai, AI Gateway: AI GatewaySource 6, Portkey, Model Catalog: Model CatalogSource 7, portkey.ai, Virtual Keys: Virtual Keys

Details

Portkey.ai plans stay on sale. Developer is free with 10,000 recorded logs a month for prototyping, and Portkey calls it unsuitable for production workloads. Production costs US$49 per month with 100,000 recorded logs. Enterprise is custom, with 10 million or more recorded logs a month. Through its AI gateway, Portkey connects to 1600+ LLMs and providers. Each model maker bills its tokens on your own API keys, which you add in Portkey's Model Catalog. Portkey's docs mark the older virtual keys as deprecated.

Cost drivers

US$9 per 100,000

Production overage on recorded requests up to 3 million a month; logs kept 30 days.

Source 1, Portkey, Portkey pricing: Portkey pricing

Details

Recorded logs drive the bill. Production adds US$9 per additional 100,000 requests up to 3 million a month. Developer allows no overage: requests past its 10,000-log limit still run but are not recorded. Logs are kept 3 days on Developer and 30 days on Production, with custom retention on Enterprise.

Where it runs

Cloud or your VPC

Hybrid Enterprise keeps the data plane in your VPC; the open-source gateway runs on your servers.

Source 4, Portkey, Hybrid deployment: Hybrid deploymentSource 1, Portkey, Portkey pricing: Portkey pricing

Details

Portkey cloud by default. A hybrid Enterprise setup runs the data plane in your VPC, keeping LLM traffic in your environment, while Portkey's control plane handles administration, configs, and analytics. Enterprise also offers private cloud and VPC hosting. The open-source gateway runs on your own servers.

What to verify

Enterprise controls

SSO, key budgets, custom retention, and audit logs of admin actions need the Enterprise plan.

Source 2, Portkey, Enterprise offering: Enterprise offeringSource 3, Portkey, Audit logs: Audit logsSource 1, Portkey, Portkey pricing: Portkey pricing

Details

SSO with Okta and Microsoft, budget and rate limits on API keys, and custom retention are Enterprise features. Audit logs record who did what to which resource, and when, on the Enterprise plan. Portkey states SOC 2, ISO 27001, GDPR, and HIPAA compliance, with custom BAAs on Enterprise.

Signals

What is the current evidence saying about Portkey?

A current read of what teams and individual developers report publicly about running model traffic through Portkey, hosted or self-hosted, with each finding linked to its sources.

Whose sources count

Practitioner sentiment, all practitioners

0 Mixed net

of 50 sources that take a side, each author counted once.

How this figure is made

Teams and leaders have 18 accounts; GILD prints their sentiment from 20.

Current sentiment

Positive, mixed and negative sources

The score counts them as 18 positive, 11 mixed and 18 negative votes, one per author.

Across 50 counted sources the read is mixed: 20 positive, 11 mixed, and 19 negative. One API with fallbacks draws praise in 16 sources, while provider translation problems are raised in 14, reliability bugs in 8, and doubts about the open-source gateway's maintenance in 5.

Run a pilot on one service's model traffic to measure added latency, failed fallbacks and how closely its spend records match each provider's bill.

Evidence field. All 62 sources, one mark each.

Arrange by

Each mark is one source: positive, mixed, negative, no opinion stated, or documentation (not counted).

By sentiment, All practitioners. Every source GILD read, grouped as the field draws it.
GroupSourcesPositiveMixedNegativeNo opinion stated and not counted in the scoreDocumentation, checked and not counted
Positive20200000
Mixed11011000
Negative19001900
Not counted600060
Documentation600006
Every source GILD read, by the quarter it was published, as the field's time axis counts it. Documentation is dated by the day it was checked.
QuarterSources
Q3 20256
Q4 20251
Q1 20262
Q2 202615
Q3 202618
Q4 202614
Documentation, checked6

By sentiment

6 documentation pages check facts and are not counted.

Hover a mark for a quick look, click it or press Enter to open its source.Tap a mark to open its source, then step to its neighbors with Previous and Next.

What practitioners praise

Top praise of 2. Each mark is a source on it; filled marks praise it.

  1. One API with Fallbacks16 of 17 sources on it praise it

Most common concerns

Top concern of 3. Each mark is a source on it; filled marks raise it.

  1. Provider Translation Bugs14 of 15 sources on it raise it as a concern
All 62 sources behind these findings
  1. PricingPortkey (Official), Product documentation, checked Oct 28, 2026
  2. Enterprise offeringPortkey (Official), Product documentation, checked Oct 28, 2026
  3. Audit logsPortkey (Official), Product documentation, checked Oct 28, 2026
  4. Model CatalogPortkey (Official), Product documentation, checked Oct 28, 2026
  5. Enforce budget and rate limitsPortkey (Official), Product documentation, checked Oct 28, 2026
  6. Hybrid deployment architecturePortkey (Official), Product documentation, checked Oct 28, 2026
  7. Live logs middleware hardcodes the port and shows an undefined endpointshafiktanbir, GitHub user (self-described: Self-hosted gateway on a custom port), GitHub issue, published Oct 26, 2026
  8. Google / Vertex AI streaming drops functionCall after thought or text partdr-goo, GitHub user (self-described: Streaming tool calls on Gemini and Vertex AI), GitHub issue, published Oct 26, 2026
  9. fix(k8s): the portkey gateway reads its routing config in the documented way, or the unused config goesdan-petty, owner of the devops-cli repository (self-described: devops-cli, which runs the Portkey gateway in its own Kubernetes cluster), GitHub issue, published Oct 24, 2026
  10. feat(video): Portkey gateway video generation (omni-flash + Veo 3.1)Jaraxxxx, owner of an OpenMontage fork (self-described: OpenMontage video generation through one Portkey API key), GitHub pull request, published Oct 24, 2026
  11. [BUG] embed(array) returns one vector for many texts with Bedrock Titan behind an OpenAI-compatible gatewaysheredega303, GitHub user calling Amazon Titan embeddings through Portkey (self-described: RubyLLM embeddings on Amazon Titan through Portkey), GitHub issue, published Oct 22, 2026
  12. fix: move myceli.ai services onto pollinations.aivoodoohop, Pollinations team member (self-described: Pollinations, whose generation service calls its own Portkey deployment), GitHub pull request, published Oct 16, 2026
  13. POST /v1/messages with x-portkey-provider: openai or google returns HTTP 500xinliu0727-sudo, GitHub user (self-described: Anthropic-format requests to OpenAI and Google models), GitHub issue, published Oct 15, 2026
  14. One door or forty doors.Yves Mulkers, publisher of the ins7ghts.com AI and data newsletter (self-described: Commentary on the acquisition), X post, published Oct 12, 2026
  15. Did anyone running an agent shop actually save money after moving off Portkey?Eastern-Novel-7884, Reddit (r/AI_Agents) (self-described: A three-person team building intake and scheduling tools for clinics and law offices, with clients running intake around the clock), Reddit post, r/AI_Agents, published Oct 9, 2026
  16. Google provider: system messages that are not the first message are dropped from contentsxinliu0727-sudo, GitHub user (self-described: OpenAI-format requests routed to Gemini), GitHub issue, published Oct 7, 2026
  17. feat: add an OpenAI-compatible provider for any gateway or serverDEENUU1, vstorm-co team member (self-described: vstorm's full-stack AI agent template), GitHub pull request, published Oct 6, 2026
  18. OpenAI-format usage for Anthropic cache reads: cached_tokens exceeds prompt_tokenskwisatzh, GitHub user comparing four gateways (self-described: Usage accounting across four open-source gateways), GitHub issue, published Oct 5, 2026
  19. Bedrock /v1/messages streaming drops exception eventschrikrah, GitHub user (self-described: Bedrock models on the Messages route), GitHub issue, published Oct 3, 2026
  20. Replace Portkey gateway with harness-core and handle providers directly in ozwellai-apiRajkumar (rajkumargaramie), Medical Informatics Engineering (GitHub profile) (self-described: Medical Informatics Engineering's Ozwell API reference server, which used Portkey for routing to OpenAI, Anthropic and self-hosted Ollama and for normalizing provider formats), GitHub issue comment, published Oct 2, 2026
  21. Adopt a mature LLM gateway (LiteLLM) for optional model-access enforcement (AI Gateway #2274)Brad-Edwards, owner of the bigrae repository (self-described: bigrae, choosing a gateway for optional model-access enforcement), GitHub issue, published Sep 30, 2026
  22. Optional lifecycle field on src/data/models.json: 95 listed models are already retired at their providerjoelp22-maker, maintainer of a model retirement dataset (self-described: The gateway's bundled model catalog), GitHub issue, published Sep 20, 2026
  23. Email address mentioned under contact us not workingmrSingh007, GitHub user (self-described: Seeking support for the self-hosted gateway), GitHub issue, published Sep 15, 2026
  24. Every "AI SDR" on the market is a wrapper around the same 60 tools.Tim, founder building RevenueFlow (self-described: RevenueFlow's production stack), X post, published Sep 11, 2026
  25. Streaming: when the upstream closes the stream mid-answer, the gateway ends its own response cleanlysakshamyadav090, GitHub user (self-described: Streaming with a configured fallback), GitHub issue, published Sep 9, 2026
  26. fix(providers): align Portkey credentials with request routingmldangelo, Promptfoo team member (self-described: Promptfoo's Portkey provider), GitHub pull request, published Sep 9, 2026
  27. Reply on LiteLLM alternatives for per-team limits, r/mlopsCorrect_Scratch8942, Reddit (r/mlops) (self-described: Portkey in front of several teams' model traffic), Reddit comment, r/mlops, published Sep 9, 2026
  28. You can't fix what you can't see.Ezekiel Oluyale, AI/ML engineer (self-described: Personal LLM app monitoring), X post, published Sep 7, 2026
  29. ci: inject the model-gateway host into agent-phase allowlistsAllenGrahamHart, collaborator on terminal-bench-science (self-described: terminal-bench-science CI, which can run agents through Portkey among four model gateways), GitHub pull request, published Aug 22, 2026
  30. Per-request Gateway API keys: survey, Temporal design, and pipelex-server handoff (docs only)lchoquel, Pipelex team member (self-described: Pipelex, which routes hosted runs through a Portkey gateway), GitHub pull request, published Aug 18, 2026
  31. Assistant: Portkey gateway provider auth supportsharon-wang, Posit Positron team member (self-described: Positron Assistant's experimental Portkey gateway provider), GitHub issue, published Aug 12, 2026
  32. Bedrock: tool-result cachePoint nested where the AWS schema forbids itarohou, GitHub user (self-described: Prompt caching on Bedrock through the gateway), GitHub issue, published Aug 11, 2026
  33. Gemini function calling: role function not transformed to role MODELTCK0423, GitHub user (self-described: Hermes Agent with Google Gemini through Portkey's hosted API), GitHub issue, published Aug 9, 2026
  34. is this going to be maintained?pritamsoni-hsr, GitHub user (self-described: A self-hosted gateway user after the acquisition), GitHub issue, published Aug 5, 2026
  35. Custom provider: support Anthropic Messages API for Claude modelssharon-wang, Posit ai-lib team member (self-described: Posit's ai-lib provider bridge), GitHub issue, published Jul 30, 2026
  36. moonshot provider model list is four generations stalesophiaashi, GitHub user (self-described: The gateway's bundled model catalog), GitHub issue, published Jul 28, 2026
  37. Actively maintained fork of Portkeypunkpeye, founder of Glama and maintainer of the Lightport fork (self-described: Glama, whose AI gateway runs on Lightport, a fork of Portkey's gateway), GitHub issue, published Jul 18, 2026
  38. SSRF allowlist bypass and credential theft via /v1/proxy/* route, @portkey-ai/gateway 1.15.2 and earliergeo-chen, security researcher (self-described: Security review of the open-source gateway), GitHub issue, published Jul 3, 2026
  39. Centralized AI gateway has streamlined model routing, costs tracking, and data protectionAkashkhurana Hirana, Senior Software Engineer 2 at Porch (self-described: Porch, which calls Gemini, OpenAI, Claude and fine-tuned models through Portkey), Review, PeerSpot, published Jun 27, 2026
  40. Centralized AI control has standardized our workflows and delivers faster, more reliable featuresShravan Revanna, Software Engineer at Clydo (klydo.in) (self-described: Clydo, which routes internal copilots, catalog intelligence and support assistants through Portkey), Review, PeerSpot, published Jun 26, 2026
  41. [Enhancement]: custom endpoint implementation with openai responses api not compatible with anthropic native web searchxinguaws, GitHub user running a LibreChat deployment (self-described: A LibreChat deployment at ai.drwcloud.com calling Claude on Vertex AI through Portkey), GitHub issue, published Jun 23, 2026
  42. feat: Portkey gateway integration for enterprise routingsseshachala, owner of the ConductAI repository (self-described: ConductAI, asked by an enterprise prospect to route through its existing Portkey setup), GitHub issue, published Jun 9, 2026
  43. docs(sales): Portkey onboarding friction notes for demosseshachala, owner of the ConductAI repository (self-described: Notes from a sales follow-up on the Portkey integration), GitHub issue, published Jun 9, 2026
  44. Unified ai gateway has standardized observability and routing for multiple llm applicationsSinghAman, Generative AI Engineer at an outsourcing company with 10, 001+ employees (self-described: Two years of Portkey as the gateway and observability layer for LLM applications with US and EU endpoints), Review, PeerSpot, published Jun 5, 2026
  45. Prompt testing has become structured and flexible but trial access still needs improvementSupport Pan, project manager and delivery owner (self-described: A team trying Portkey as a LiteLLM alternative for prompt template testing), Review, PeerSpot, published May 31, 2026
  46. azure-ai-inference: no Responses API support, requests silently fall back to chatComplete with data lossdavidwhite-spec, GitHub user (self-described: Responses API calls to an Azure AI Inference key), GitHub issue, published May 30, 2026
  47. Build fails on 2.0.0: akto plugin committed to plugins/akto/ instead of src/plugins/akto/damray, GitHub user (self-described: Building the gateway's 2.0.0 branch), GitHub issue, published May 30, 2026
  48. Fix chat_portkey() error when PORTKEY_VIRTUAL_KEY is not setthisisnic, ellmer collaborator (self-described: ellmer's chat_portkey() provider for R), GitHub pull request, published May 26, 2026
  49. Streamed responses fail under concurrent load with "Response object has been garbage collected"meitalbensinai, GitHub user (self-described: Self-hosted gateway under concurrent streaming load), GitHub issue, published May 19, 2026
  50. feat(portkey): add intel modulejychp, Cartography collaborator (self-described: Cartography's security inventory of Portkey organizations), GitHub pull request, published May 6, 2026
  51. Show HN: Lightport, open-source AI gatewaystatements, founder of Glama (self-described: Glama, whose AI gateway Lightport began as a fork of Portkey), Hacker News post, published Apr 28, 2026
  52. Claude Opus 4.7 fails on Bedrock via custom provider with reasoning enabled (wrong thinking format)harsh-m-patil, Pi user (self-described: Pi coding agent calling Claude on Bedrock through Portkey), GitHub issue, published Apr 17, 2026
  53. Intermittent auth failures with Claude Code OAuth passthrough (mid-session)Yupei Chen, Wise Rock (GitHub profile) (self-described: Claude Code signed in through Anthropic OAuth on a Team plan, pointed at Portkey's hosted API as Portkey's OAuth docs describe), GitHub issue, published Apr 10, 2026
  54. Tool calls and file inputs fail with Responses API via Portkey for OpenAI, Azure OpenAI, and BedrockNilesh Darji, Founding Engineer at Heizen (his own site) (self-described: LangChain's ChatOpenAI on the Responses API, through Portkey's hosted API to Azure OpenAI and Bedrock), GitHub issue, published Mar 28, 2026
  55. Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedtreefarmer, Hacker News commenter (self-described: Personal and side-project model access on Portkey's free plan), Hacker News comment, published Mar 24, 2026
  56. OpenAI Providers custom HTTP Headersevalstate, owner of the fast-agent repository (self-described: fast-agent's OpenAI-compatible providers), GitHub pull request, published Dec 6, 2025
  57. Connection errors in productionianbbqzy, GitHub user running the gateway in production (self-described: Production traffic through the gateway, with errors seen on OpenAI, Anthropic, and Mistral), GitHub issue, published Sep 24, 2025
  58. Removing 11,005 Lines: Why We Replaced Our Custom LLM Manager with Portkeyclayroach, developer of an open-source observability platform (self-described: An observability platform that replaced its own LLM manager with Portkey's gateway), Engineering blog post, DEV Community, published Sep 16, 2025
  59. Bug Report: Simple Cache Incorrectly Converted to Semantic Cache Causing Platform OutageLeonardo Marciano, CTO by his own GitHub profile (self-described: A platform on Portkey's hosted cloud), GitHub issue, published Jul 23, 2025
  60. Comment on: Show HN: Any-LLM, Lightweight router to access any LLM Providerswyx, Hacker News commenter (self-described: Comparing model routers), Hacker News comment, published Jul 22, 2025
  61. Show HN: Aqueduct AI Gateway, A Self-Hostable AI Gateway Without the Taxesmeffmadd, member of a small team at TU Vienna and author of Aqueduct (self-described: TU Vienna, which built its own gateway after evaluating LiteLLM, Portkey, and Kong), Hacker News post, published Jul 1, 2025
  62. Comment on: HN Slop: AI startup ideas generated from Hacker Newschandureddyvari, Hacker News commenter (self-described: An app hitting provider rate limits), Hacker News comment, published Jul 1, 2025

Jul 2025 to Oct 2026.

56 sources from practitioners, by month and sentiment.

The full readExplore all Portkey Signals4 praise themes, 6 concerns, 0 points of agreement and 1 disagreement across all three groups, with all 62 sources open to inspect.

Where It Fits

Where does Portkey belong in the stack?

Open Where It Fits: the Stack Field and the full map

Portkey is Core across Model, supports Operate, and touches Build, Data, and Evaluate.

Business area
Product & Engineering
Function
Software Development
Operating stack
AI Application Platform
Primary role
Governed AI Gateway & Request Logs
Portkey beside the rest of its stackThe Stack Field, every product on every layer
FootprintPortkey across the AI Application Platform stack. Bar height is its role on each layer.

  1. Model

    1. Model APIs: Touches

      Model APIs, touches. Portkey sells no model access: admins add their own provider keys to the Model Catalog, and each model maker bills its tokens.

    2. Model gateway: Core

      Model gateway, core. This is Portkey's primary role: one universal API with fallbacks, load balancing, retries, and caching on every plan, with budgets and rate limits on API keys on Enterprise and for select Pro customers.

  2. Build

    1. Orchestration: Touches

      Orchestration, touches. Integration guides cover LangChain agents and coding tools such as Claude Code through the gateway. A framework such as LangGraph controls the agent's steps.

    2. Tool use: Touches

      Tool use, touches. Portkey documents integrations for agent libraries and coding tools that call models through it. The tools an agent calls run elsewhere.

  3. Data

    1. Retrieval: Touches

      Retrieval, touches. Portkey routes embedding calls to the model makers on your keys and stores no search index; retrieval stays with a vector database or search product.

  4. Evaluate

    1. Evaluation: Touches

      Evaluation, touches. Feedback on logged requests is on every plan and advanced evaluation templates are on Enterprise, while datasets and scoring at scale stay with an evaluation tool.

  5. Operate

    1. Observability: Supports

      Observability, supports. Logs, traces, feedback, metadata, and filters on every plan, with alerts from Production, keep 3 days of logs on Developer and 30 on Production. Agent-step evaluation and long-term analysis stay with an observability tool.

    2. Cloud deployment: Touches

      Cloud deployment, touches. A hybrid Enterprise setup runs the data plane in your VPC with Portkey's control plane, and the open-source gateway runs on your servers; model capacity and quotas come from each model maker.

    3. Guardrails: Supports

      Guardrails, supports. Portkey Guardrails run deterministic and LLM based checks on requests and responses, including prompt injection scanning and moderation. Guardrail actions block or route failed calls.

Market mapThe layers Portkey covers, and who else owns each one.

  1. Model gateways & routing

    CoreModel

  2. Observability & tracing

    SupportsOperate

  3. Guardrails & AI security

    SupportsOperate

    • Prisma AIRS
    • NeMo Guardrails

  4. Model APIs

    TouchesModel

  5. Orchestration & agent frameworks

    TouchesBuild

4 more layers on the full map. Core, Supports and Touches describe coverage. They say nothing about quality.

Models

Which models run in Portkey?

The current releases GILD tracks that public sources record running in Portkey. Each model's page charts its public benchmark scores.

  1. GPT-5.4OpenAI's GPT-5.4 model for coding and professional work, with text and image input. API model gpt-5.4 (snapshot gpt-5.4-2026-03-05) at US$2.50 per million input tokens and US$15 per million output tokens, with a 1,050,000-token context window; prompts over 272K input tokens cost more. Also in Cursor; GitHub Copilot dropped it on October 19, 2026.GPT-5Benchmarks

More on Portkey

  1. GILD ReviewGILD's evaluation, with the buying facts
  2. Research1 piece
  3. Guides1 guide
  4. Operator Insights8 operator accounts
  5. Where It FitsOn the AI Application Platform stack
  6. Related Products6 products