Skip to main content
PortkeyProduct page

Portkey Signals

What teams building AI features on Portkey report, with every finding tied to its evidence.

Read the findings

What the evidence says

Whose sources count

Practitioner sentiment, all practitioners

0 Mixed from 50 sources that take a side

How this figure is made

Mixed overall signal, net 0 points

From 47 authors in 50 discussions. 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.

Analyzed
62 total sources
Top praise
One API with Fallbacks (16 of 17 sources) See praise evidence
Top concern
Provider Translation Bugs (14 of 15 sources) See concern evidence

Jul 2025 to Oct 2026.

56 sources from practitioners, by month and sentiment.

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.

Positive, mixed and negative sources

The score counts them as 18 positive, 11 mixed and 18 negative votes, one per author. See How the numbers work.

See the evidence

Below: 2 praise themes and 3 concerns.

Findings

Counted for All practitioners, from 56 sources. Change group

What practitioners praise

Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.

  1. One API with Fallbacks16 of 17 sources on it praise itOne OpenAI-compatible API reaches many providers, with fallbacks, load balancing, and retries set in configuration.

    Counted for All practitioners.

    Positive, 16

    1. Positive

      Jaraxxxx, owner of an OpenMontage fork

      feat(video): Portkey gateway video generation (omni-flash + Veo 3.1)GitHub pull request

      Adds video generation through a single Portkey API key with no per-vendor credentials, covering Gemini and Veo 3.1 behind one gateway.

      Published Oct 24, 2026self-described: OpenMontage video generation through one Portkey API key

    2. Positive

      DEENUU1, vstorm-co team member

      feat: add an OpenAI-compatible provider for any gateway or serverGitHub pull request

      Replaces gateway-specific providers with one OpenAI-compatible provider that reaches LiteLLM, Requesty, OrcaRouter and Portkey by base URL.

      Published Oct 6, 2026self-described: vstorm's full-stack AI agent template

    3. Positive

      Tim, founder building RevenueFlow

      Every "AI SDR" on the market is a wrapper around the same 60 tools.X post

      Lists Portkey beside OpenRouter and LiteLLM as model routing in the 19 tools RevenueFlow runs in production.

      "…the 19 we run in production: THE BRAIN 1. Models: @AnthropicAI, @OpenAI, Google Gemini 2. Model routing: @OpenRouter, @LiteLLM, Portkey…"
      Excerpt, Tim

      Published Sep 11, 2026self-described: RevenueFlow's production stack

    4. Positive

      AllenGrahamHart, collaborator on terminal-bench-science

      ci: inject the model-gateway host into agent-phase allowlistsGitHub pull request

      Terminal-bench-science's CI can send agent traffic through Portkey as one of four model gateways, adding api.portkey.ai to network allowlists.

      Published Aug 22, 2026self-described: terminal-bench-science CI, which can run agents through Portkey among four model gateways

    5. Positive

      lchoquel, Pipelex team member

      Per-request Gateway API keys: survey, Temporal design, and pipelex-server handoff (docs only)GitHub pull request

      Pipelex designs a separate Portkey gateway key for each hosted run, bound per request under its Temporal workflows, to replace the single key cached in its SDK client.

      Published Aug 18, 2026self-described: Pipelex, which routes hosted runs through a Portkey gateway

    6. Mixed

      sharon-wang, Posit Positron team member

      Assistant: Portkey gateway provider auth supportGitHub issue

      Posit Assistant added an experimental Portkey provider covering hosted Portkey and the self-hosted gateway, while Positron's direct path still lacks a sign-in for it.

      Published Aug 12, 2026self-described: Positron Assistant's experimental Portkey gateway provider

    7. Positive

      sharon-wang, Posit ai-lib team member

      Custom provider: support Anthropic Messages API for Claude modelsGitHub issue

      Posit's ai-lib already sends Claude requests to Portkey in Anthropic's Messages format and other models in OpenAI's, and plans the same split for generic gateways.

      Published Jul 30, 2026self-described: Posit's ai-lib provider bridge

    8. Positive

      Akashkhurana Hirana, Senior Software Engineer 2 at Porch

      Centralized AI gateway has streamlined model routing, costs tracking, and data protectionReview, PeerSpot

      Porch's team calls Gemini, OpenAI, Claude and its own fine-tuned models through Portkey, with provider keys held in its vault and guardrails that block personal data, and calls the documentation thin and the dashboard hard to learn.

      Published Jun 27, 2026self-described: Porch, which calls Gemini, OpenAI, Claude and fine-tuned models through Portkey

    9. Positive

      Shravan Revanna, Software Engineer at Clydo (klydo.in)

      Centralized AI control has standardized our workflows and delivers faster, more reliable featuresReview, PeerSpot

      At Clydo every user query from the internal assistant goes through Portkey, which handles authentication and routing, and the team swaps models by updating routing config and skips code changes across services; it asks for richer historical analytics and finer role-based access.

      Published Jun 26, 2026self-described: Clydo, which routes internal copilots, catalog intelligence and support assistants through Portkey

    10. Positive

      xinguaws, GitHub user running a LibreChat deployment

      [Enhancement]: custom endpoint implementation with openai responses api not compatible with anthropic native web searchGitHub issue

      Runs LibreChat against Claude on Vertex AI through a Portkey gateway, with each user's email passed as Portkey metadata.

      "…it's using claude models via google's vertex ai through portkey gateway…"
      Excerpt, xinguaws

      Published Jun 23, 2026self-described: A LibreChat deployment at ai.drwcloud.com calling Claude on Vertex AI through Portkey

    11. Positive

      sseshachala, owner of the ConductAI repository

      feat: Portkey gateway integration for enterprise routingGitHub issue

      An enterprise prospect asked ConductAI to route through its existing Portkey setup, which it treats as the organization's central AI governance layer, so ConductAI plans a Portkey integration.

      Published Jun 9, 2026self-described: ConductAI, asked by an enterprise prospect to route through its existing Portkey setup

    12. Positive

      sseshachala, owner of the ConductAI repository

      docs(sales): Portkey onboarding friction notes for demoGitHub issue

      Finds getting a Portkey key very low friction and the one setup step an admin adding provider keys as virtual keys in about 5 minutes, after which developers never see the raw keys.

      Published Jun 9, 2026self-described: Notes from a sales follow-up on the Portkey integration

    13. Positive

      SinghAman, Generative AI Engineer at an outsourcing company with 10, 001+ employees

      Unified ai gateway has standardized observability and routing for multiple llm applicationsReview, PeerSpot

      After two years as the gateway and observability layer, Portkey has been reliable about 99% of the time, with endpoints down once or twice in six months; onboarding needs more guided templates.

      Published Jun 5, 2026self-described: Two years of Portkey as the gateway and observability layer for LLM applications with US and EU endpoints

    14. Positive

      evalstate, owner of the fast-agent repository

      OpenAI Providers custom HTTP HeadersGitHub pull request

      Adds configurable HTTP headers to fast-agent's providers so agents can route through Portkey configs and other gateways that need custom headers.

      Published Dec 6, 2025self-described: fast-agent's OpenAI-compatible providers

    15. Positive

      clayroach, developer of an open-source observability platform

      Removing 11,005 Lines: Why We Replaced Our Custom LLM Manager with PortkeyEngineering blog post, DEV Community

      Replacing the team's own LLM manager with Portkey's gateway removed more than 11,000 lines of code while keeping routing and adding functionality.

      "Today I want to share how replacing our custom LLM manager with Portkey's gateway removed over 11,000 lines of code from our observability platform while actually improving functionality."
      Excerpt, clayroach

      Published Sep 16, 2025self-described: An observability platform that replaced its own LLM manager with Portkey's gateway

    16. Positive

      chandureddyvari, Hacker News commenter

      Comment on: HN Slop: AI startup ideas generated from Hacker NewsHacker News comment

      Recommends a gateway such as OpenRouter or Portkey to manage fallbacks after an app hit provider rate limits.

      "You should use something like openrouter or portkey or similar for managing fallbacks…"
      Excerpt, chandureddyvari

      Published Jul 1, 2025self-described: An app hitting provider rate limits

    Mixed or negative, 1

    1. Negative

      sakshamyadav090, GitHub user

      Streaming: when the upstream closes the stream mid-answer, the gateway ends its own response cleanlyGitHub issue

      When a provider drops a stream mid-answer, the gateway returns HTTP 200 with no error event and never tries the configured fallback, so the client shows a short answer as complete.

      "The configured fallback target is never tried."
      Excerpt, sakshamyadav090

      Published Sep 9, 2026self-described: Streaming with a configured fallback

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Portkey's pricing page lists a universal API with fallbacks, load balancing, and retries on every plan, including the free Developer plan. Pricing

    Checked Oct 28, 2026.Portkey's Claude Code integration routes Claude Code through Anthropic, Bedrock, or Vertex AI with workspaces, budgets, and rate limits per team. Claude Code integration

    Checked Oct 28, 2026.Portkey documents a LangChain (Python) integration that sends LangChain calls and agents through the gateway. LangChain (Python) integration

    Checked Oct 28, 2026.Portkey's AWS Bedrock integration calls Bedrock models on your own AWS credentials through the gateway. AWS Bedrock integration

    Open them in the record
  2. Request Logs & Cost DataAll 8 sources on it praise itEach request is logged with its cost, latency, and metadata such as the user who made it.

    Counted for All practitioners.

    1. Mixed

      kwisatzh, GitHub user comparing four gateways

      OpenAI-format usage for Anthropic cache reads: cached_tokens exceeds prompt_tokensGitHub issue

      Running the same requests through four gateways, Portkey 1.15.2 matched provider usage on ordinary requests and kept every Anthropic cache field on the Messages path, with one cache-token translation error on the OpenAI-format path.

      "Portkey v1.15.2 did well: ordinary requests matched the provider, and the native Messages path kept every Anthropic cache field."
      Excerpt, kwisatzh

      Published Oct 5, 2026self-described: Usage accounting across four open-source gateways

    2. Positive

      Ezekiel Oluyale, AI/ML engineer

      You can't fix what you can't see.X post

      Tracks cost, latency, and time to first token per request with Portkey.

      "I track cost, latency, TTFT per request with Portkey. Now I can see: → Cost per 1k tokens → Time to first token (TTFT) → Total latency…"
      Excerpt, Ezekiel Oluyale

      Published Sep 7, 2026self-described: Personal LLM app monitoring

    3. Positive

      lchoquel, Pipelex team member

      Per-request Gateway API keys: survey, Temporal design, and pipelex-server handoff (docs only)GitHub pull request

      Pipelex designs a separate Portkey gateway key for each hosted run, bound per request under its Temporal workflows, to replace the single key cached in its SDK client.

      Published Aug 18, 2026self-described: Pipelex, which routes hosted runs through a Portkey gateway

    4. Positive

      Akashkhurana Hirana, Senior Software Engineer 2 at Porch

      Centralized AI gateway has streamlined model routing, costs tracking, and data protectionReview, PeerSpot

      Porch's team calls Gemini, OpenAI, Claude and its own fine-tuned models through Portkey, with provider keys held in its vault and guardrails that block personal data, and calls the documentation thin and the dashboard hard to learn.

      Published Jun 27, 2026self-described: Porch, which calls Gemini, OpenAI, Claude and fine-tuned models through Portkey

    5. Positive

      Shravan Revanna, Software Engineer at Clydo (klydo.in)

      Centralized AI control has standardized our workflows and delivers faster, more reliable featuresReview, PeerSpot

      At Clydo every user query from the internal assistant goes through Portkey, which handles authentication and routing, and the team swaps models by updating routing config and skips code changes across services; it asks for richer historical analytics and finer role-based access.

      Published Jun 26, 2026self-described: Clydo, which routes internal copilots, catalog intelligence and support assistants through Portkey

    6. Positive

      xinguaws, GitHub user running a LibreChat deployment

      [Enhancement]: custom endpoint implementation with openai responses api not compatible with anthropic native web searchGitHub issue

      Runs LibreChat against Claude on Vertex AI through a Portkey gateway, with each user's email passed as Portkey metadata.

      "…it's using claude models via google's vertex ai through portkey gateway…"
      Excerpt, xinguaws

      Published Jun 23, 2026self-described: A LibreChat deployment at ai.drwcloud.com calling Claude on Vertex AI through Portkey

    7. Positive

      SinghAman, Generative AI Engineer at an outsourcing company with 10, 001+ employees

      Unified ai gateway has standardized observability and routing for multiple llm applicationsReview, PeerSpot

      After two years as the gateway and observability layer, Portkey has been reliable about 99% of the time, with endpoints down once or twice in six months; onboarding needs more guided templates.

      Published Jun 5, 2026self-described: Two years of Portkey as the gateway and observability layer for LLM applications with US and EU endpoints

    8. Positive

      jychp, Cartography collaborator

      feat(portkey): add intel moduleGitHub pull request

      Adds a Cartography module that inventories Portkey organizations, workspaces, API keys, virtual keys, guardrails and MCP servers for security review.

      Published May 6, 2026self-described: Cartography's security inventory of Portkey organizations

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Developer keeps logs 3 days and metrics 30 days; Production keeps logs 30 days and metrics 90 days; Enterprise sets custom retention periods. Pricing

    Open them in the record

What concerns them

Every concern practitioners raise, most raised first.

  1. Provider Translation Bugs14 of 15 sources on it raise it as a concernRequests translated between provider formats lose fields, roles, cache settings, or tool calls, or fail outright.

    Counted for All practitioners.

    Raised as a concern, 14

    1. Negative

      dr-goo, GitHub user

      Google / Vertex AI streaming drops functionCall after thought or text partGitHub issue

      Streaming responses from Gemini and Vertex AI drop tool calls that follow a thought or text part and report the wrong finish reason.

      Published Oct 26, 2026self-described: Streaming tool calls on Gemini and Vertex AI

    2. Negative

      sheredega303, GitHub user calling Amazon Titan embeddings through Portkey

      [BUG] embed(array) returns one vector for many texts with Bedrock Titan behind an OpenAI-compatible gatewayGitHub issue

      With Portkey in front of Amazon Titan embeddings, a batch request returned one embedding for the first text and silently dropped the rest.

      "We hit this with Portkey in front of Amazon Titan, which takes one input per request. The gateway returns a single vector for the first text and drops the rest."
      Excerpt, sheredega303

      Published Oct 22, 2026self-described: RubyLLM embeddings on Amazon Titan through Portkey

    3. Negative

      xinliu0727-sudo, GitHub user

      POST /v1/messages with x-portkey-provider: openai or google returns HTTP 500GitHub issue

      Anthropic Messages requests to OpenAI or Google models fail with HTTP 500 on gateway 1.15.2 before reaching the provider.

      "…fails with HTTP 500 on Gateway `v1.15.2`…"
      Excerpt, xinliu0727-sudo

      Published Oct 15, 2026self-described: Anthropic-format requests to OpenAI and Google models

    4. Negative

      xinliu0727-sudo, GitHub user

      Google provider: system messages that are not the first message are dropped from contentsGitHub issue

      System messages after the first one, and assistant text before tool calls, disappear without an error when requests are routed to Gemini.

      "…every `system` message is skipped while building `contents`…"
      Excerpt, xinliu0727-sudo

      Published Oct 7, 2026self-described: OpenAI-format requests routed to Gemini

    5. Mixed

      kwisatzh, GitHub user comparing four gateways

      OpenAI-format usage for Anthropic cache reads: cached_tokens exceeds prompt_tokensGitHub issue

      Running the same requests through four gateways, Portkey 1.15.2 matched provider usage on ordinary requests and kept every Anthropic cache field on the Messages path, with one cache-token translation error on the OpenAI-format path.

      "Portkey v1.15.2 did well: ordinary requests matched the provider, and the native Messages path kept every Anthropic cache field."
      Excerpt, kwisatzh

      Published Oct 5, 2026self-described: Usage accounting across four open-source gateways

    6. Negative

      chrikrah, GitHub user

      Bedrock /v1/messages streaming drops exception eventsGitHub issue

      Bedrock stream exceptions never reach the client on the Messages route, which sees an empty HTTP 200 or a stream that stops without an error.

      "Bedrock /v1/messages streaming drops exception events: HTTP 200 with an empty body, or a stream that stops with no error event ### What Happened? On `/v1/messages` with a Bedrock model, an exception event in the ConverseStream response never reaches the client. `BedrockConverseMessagesStreamChunkTransform` (`src/providers/bedrock/messages.ts:546`) has no branch for its `{"message": ...}` payload and returns `undefined`. On `669825c`, with synthesized event-stream frames: ``` $ npx tsx repro.ts normal: HTTP 200, 859 bytes, events [message_start, content_block_start, content_block_delta, content_block_stop, message_delta, message_stop] exception only: HTTP 200, 0 bytes, events [] exception after a delta: HTTP 200, 580 bytes, events [message_start, content_block_start, content_block_delta] ``` Both exception cases lose the message from the provider, and the second stream just stops. This is the `/v1/messages` sibl…"
      Excerpt, chrikrah

      Published Oct 3, 2026self-described: Bedrock models on the Messages route

    7. Mixed

      joelp22-maker, maintainer of a model retirement dataset

      Optional lifecycle field on src/data/models.json: 95 listed models are already retired at their providerGitHub issue

      Of 126 catalog entries matched against provider retirement dates, 95 are models their provider has retired, and the 1,928-model catalog carries no lifecycle field.

      Published Sep 20, 2026self-described: The gateway's bundled model catalog

    8. Negative

      arohou, GitHub user

      Bedrock: tool-result cachePoint nested where the AWS schema forbids itGitHub issue

      Three defects in the Bedrock translation shorten prompt-cache lifetimes, and one makes a valid request with a one-hour cache fail outright.

      "Three related defects in the Bedrock provider's Converse translation, all around prompt-cache checkpoints."
      Excerpt, arohou

      Published Aug 11, 2026self-described: Prompt caching on Bedrock through the gateway

    9. Negative

      TCK0423, GitHub user

      Gemini function calling: role function not transformed to role MODELGitHub issue

      Routing Hermes Agent and Gemini through Portkey fails on function calls because Portkey passes the OpenAI function role to Gemini unchanged.

      "When routing Hermes Agent + Google Gemini through Portkey Gateway, function calling fails with:…"
      Excerpt, TCK0423

      Published Aug 9, 2026self-described: Hermes Agent with Google Gemini through Portkey's hosted API

    10. Negative

      sophiaashi, GitHub user

      moonshot provider model list is four generations staleGitHub issue

      The gateway's model list names only three pre-Kimi K Moonshot models and none of the four generations since, so the integration looks abandoned.

      "…lists exactly three models under the `moonshot` provider…"
      Excerpt, sophiaashi

      Published Jul 28, 2026self-described: The gateway's bundled model catalog

    11. Negative

      davidwhite-spec, GitHub user

      azure-ai-inference: no Responses API support, requests silently fall back to chatComplete with data lossGitHub issue

      Responses API requests to the Azure AI Inference provider return no error and are silently translated to chat completions, dropping fields on the way.

      "The `azure-ai-inference` provider has no Responses API support."
      Excerpt, davidwhite-spec

      Published May 30, 2026self-described: Responses API calls to an Azure AI Inference key

    12. Mixed

      thisisnic, ellmer collaborator

      Fix chat_portkey() error when PORTKEY_VIRTUAL_KEY is not setGitHub pull request

      After Portkey's virtual key deprecation, ellmer's Portkey provider required a virtual key for any model outside the @provider/model format, which broke custom gateways passing Bedrock ARNs.

      Published May 26, 2026self-described: ellmer's chat_portkey() provider for R

    13. Mixed

      harsh-m-patil, Pi user

      Claude Opus 4.7 fails on Bedrock via custom provider with reasoning enabled (wrong thinking format)GitHub issue

      Claude Opus 4.7 on Bedrock fails with a 400 thinking-format error when Pi calls it through Portkey with reasoning enabled.

      Published Apr 17, 2026self-described: Pi coding agent calling Claude on Bedrock through Portkey

    14. Negative

      Nilesh Darji, Founding Engineer at Heizen (his own site)

      Tool calls and file inputs fail with Responses API via Portkey for OpenAI, Azure OpenAI, and BedrockGitHub issue

      Tool calls failed on the Responses API through Portkey and worked against the provider directly. Bedrock returned errors for empty message content and for more tool results than tool calls, Azure OpenAI returned ModelNotFound for a model that exists, and file inputs failed on both.

      Published Mar 28, 2026self-described: LangChain's ChatOpenAI on the Responses API, through Portkey's hosted API to Azure OpenAI and Bedrock

    Discussed without concern, 1

    1. Mixed

      mldangelo, Promptfoo team member

      fix(providers): align Portkey credentials with request routingGitHub pull request

      Fixes how Promptfoo's Portkey provider picks credentials, since Portkey separates its gateway key from upstream keys, virtual keys and catalog slugs and each route needs the right one.

      Published Sep 9, 2026self-described: Promptfoo's Portkey provider

    Open them in the record
  2. Reliability & Streaming Bugs8 of 9 sources on it raise it as a concernStreams that end early or silently, connection errors, fallbacks that never fire, and outages.

    Counted for All practitioners.

    Raised as a concern, 8

    1. Mixed

      shafiktanbir, GitHub user

      Live logs middleware hardcodes the port and shows an undefined endpointGitHub issue

      The self-hosted gateway's live log view shows an undefined endpoint whenever it runs on a custom port or behind a reverse proxy.

      "…in the Endpoint column instead of the request path…"
      Excerpt, shafiktanbir

      Published Oct 26, 2026self-described: Self-hosted gateway on a custom port

    2. Mixed

      dan-petty, owner of the devops-cli repository

      fix(k8s): the portkey gateway reads its routing config in the documented way, or the unused config goesGitHub issue

      Self-hosts gateway 1.15.0 in Kubernetes and found the mounted routing config file is never read by the gateway image, so its routes had no effect on live traffic.

      Published Oct 24, 2026self-described: devops-cli, which runs the Portkey gateway in its own Kubernetes cluster

    3. Negative

      chrikrah, GitHub user

      Bedrock /v1/messages streaming drops exception eventsGitHub issue

      Bedrock stream exceptions never reach the client on the Messages route, which sees an empty HTTP 200 or a stream that stops without an error.

      "Bedrock /v1/messages streaming drops exception events: HTTP 200 with an empty body, or a stream that stops with no error event ### What Happened? On `/v1/messages` with a Bedrock model, an exception event in the ConverseStream response never reaches the client. `BedrockConverseMessagesStreamChunkTransform` (`src/providers/bedrock/messages.ts:546`) has no branch for its `{"message": ...}` payload and returns `undefined`. On `669825c`, with synthesized event-stream frames: ``` $ npx tsx repro.ts normal: HTTP 200, 859 bytes, events [message_start, content_block_start, content_block_delta, content_block_stop, message_delta, message_stop] exception only: HTTP 200, 0 bytes, events [] exception after a delta: HTTP 200, 580 bytes, events [message_start, content_block_start, content_block_delta] ``` Both exception cases lose the message from the provider, and the second stream just stops. This is the `/v1/messages` sibl…"
      Excerpt, chrikrah

      Published Oct 3, 2026self-described: Bedrock models on the Messages route

    4. Negative

      sakshamyadav090, GitHub user

      Streaming: when the upstream closes the stream mid-answer, the gateway ends its own response cleanlyGitHub issue

      When a provider drops a stream mid-answer, the gateway returns HTTP 200 with no error event and never tries the configured fallback, so the client shows a short answer as complete.

      "The configured fallback target is never tried."
      Excerpt, sakshamyadav090

      Published Sep 9, 2026self-described: Streaming with a configured fallback

    5. Negative

      meitalbensinai, GitHub user

      Streamed responses fail under concurrent load with "Response object has been garbage collected"GitHub issue

      Under concurrent streaming load the gateway ends streams with garbage-collection errors, and downstream clients see terminated responses.

      "Under concurrent streaming load, gateway logs show:…"
      Excerpt, meitalbensinai

      Published May 19, 2026self-described: Self-hosted gateway under concurrent streaming load

    6. Negative

      Yupei Chen, Wise Rock (GitHub profile)

      Intermittent auth failures with Claude Code OAuth passthrough (mid-session)GitHub issue

      Mid-session, Claude Code behind Portkey's hosted API returned auth errors while still showing the user signed in, and only unsetting the Portkey base URL fixed it. After reading the gateway source, the author concluded that OAuth tokens are never forwarded correctly.

      Published Apr 10, 2026self-described: Claude Code signed in through Anthropic OAuth on a Team plan, pointed at Portkey's hosted API as Portkey's OAuth docs describe

    7. Negative

      ianbbqzy, GitHub user running the gateway in production

      Connection errors in productionGitHub issue

      Occasionally sees errors likely related to connection health in production traffic, with OpenAI, Anthropic, and Mistral, that do not reproduce locally even under a load test of more than 40 concurrent requests.

      "I'm occasionally running into several errors likely related to connection health in my production traffic."
      Excerpt, ianbbqzy

      Published Sep 24, 2025self-described: Production traffic through the gateway, with errors seen on OpenAI, Anthropic, and Mistral

    8. Negative

      Leonardo Marciano, CTO by his own GitHub profile

      Bug Report: Simple Cache Incorrectly Converted to Semantic Cache Causing Platform OutageGitHub issue

      A Portkey change turned the author's platform's simple cache into a semantic cache with a hit rate near 100%, which caused a platform-wide outage for all its customers on Portkey cloud; Portkey acknowledged the bug and reverted it the same day.

      "This caused a complete platform failure while all customers were actively using the system."
      Excerpt, Leonardo Marciano

      Published Jul 23, 2025self-described: A platform on Portkey's hosted cloud

    Discussed without concern, 1

    1. Positive

      SinghAman, Generative AI Engineer at an outsourcing company with 10, 001+ employees

      Unified ai gateway has standardized observability and routing for multiple llm applicationsReview, PeerSpot

      After two years as the gateway and observability layer, Portkey has been reliable about 99% of the time, with endpoints down once or twice in six months; onboarding needs more guided templates.

      Published Jun 5, 2026self-described: Two years of Portkey as the gateway and observability layer for LLM applications with US and EU endpoints

    Open them in the record
  3. Open-Source MaintenanceAll 5 sources on it raise it as a concernWhether the open-source gateway still receives fixes, releases, and support after the acquisition.

    Counted for All practitioners.

    1. Negative

      mrSingh007, GitHub user

      Email address mentioned under contact us not workingGitHub issue

      The support address linked from the self-hosted gateway bounced as nonexistent.

      "Getting error `The email account that you tried to reach does not exist`."
      Excerpt, mrSingh007

      Published Sep 15, 2026self-described: Seeking support for the self-hosted gateway

    2. Negative

      pritamsoni-hsr, GitHub user

      is this going to be maintained?GitHub issue

      Asks after the Palo Alto Networks acquisition whether the open-source gateway will be maintained, pointing to a fork.

      Published Aug 5, 2026self-described: A self-hosted gateway user after the acquisition

    3. Negative

      sophiaashi, GitHub user

      moonshot provider model list is four generations staleGitHub issue

      The gateway's model list names only three pre-Kimi K Moonshot models and none of the four generations since, so the integration looks abandoned.

      "…lists exactly three models under the `moonshot` provider…"
      Excerpt, sophiaashi

      Published Jul 28, 2026self-described: The gateway's bundled model catalog

    4. Negative

      geo-chen, security researcher

      SSRF allowlist bypass and credential theft via /v1/proxy/* route, @portkey-ai/gateway 1.15.2 and earlierGitHub issue

      Discloses that the deprecated /v1/proxy/* route skips the allowlist check behind the v1.14.0 fix for CVE-2025-66405, allowing SSRF and credential theft, after an email report on June 1, 2026 got no response.

      "Sending any POST request to /v1/proxy/* bypasses all allowlist checks…"
      Excerpt, geo-chen

      Published Jul 3, 2026self-described: Security review of the open-source gateway

    5. Negative

      damray, GitHub user

      Build fails on 2.0.0: akto plugin committed to plugins/akto/ instead of src/plugins/akto/GitHub issue

      A clean checkout of the gateway's 2.0.0 branch does not build because a guardrail plugin was committed to the wrong directory.

      Published May 30, 2026self-described: Building the gateway's 2.0.0 branch

    GILD's fact checks, which don't count as sources

    Checked Oct 28, 2026.Palo Alto Networks announced general availability of Prisma AIRS AI Gateway, built on Portkey, on July 16, 2026. Palo Alto Networks: General availability of Prisma AIRS AI Gateway

    Open them in the record

Where the evidence agrees

Statements this group's sources agree on, then the ones close to agreement.

For all practitioners, no statement reaches 5 sources from 3 authors.

Where it disagrees

Questions the sources split on, with the count on each side.

For all practitioners, no question reaches 5 sources from 3 authors, with 2 on each side.

    The evidence

    Whose experience this is

    The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.

    Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Teams and leaders have 18 accounts; GILD prints their sentiment from 20.

    • Teams and technical leaders

      24 sources. Product teams and technical leaders describe running Portkey in production, forking it, or building their own gateway instead.

    • Individual builders

      32 sources. Developers describe the open-source gateway and the hosted API in their own projects, mostly through GitHub issues.

    • All practitioners

      56 sources. Together, these accounts combine a few production teams with developers filing issues against the open-source gateway.

    56 sources from practitioners, by the context they work in. Filled rows count for this group.

    1. Individual builderDevelopers building on the platform on their own32 sources, counted here

      Emphasizes Provider translation bugs and the open-source gateway's maintenance

    2. Small product team2 to 10 engineers, or an unnamed startup team5 sources, counted here

      Emphasizes Replacing in-house LLM code, and teams that built their own gateway

    3. Product or platform team11 to 50 engineers, or a named company's team18 sources, counted here

      Emphasizes Production use on Portkey cloud, an outage, and Glama's fork

    4. Technical leadershipLeaders setting model and platform choices across teams1 sources, counted here

      Emphasizes What Palo Alto Networks' ownership means for the gateway

    5. Organization-wideEnterprise or company-wide AI platformNo sources from this setting yet

    What changes with scale. Individual developers file bugs against the open-source gateway, most about translating requests between providers. Teams that run Portkey value one API with fallbacks and request-level cost data, and those that left forked it or built their own over maintenance and enterprise-gated features.

    Where the sources come from

    Where this group's sources were published.

    Counted for All practitioners, from 56 sources. Change group

    62 sources for this group, 6 of them documentation

    • Developer Communities51, 82% of 62 sources
    • Product Documentation6, 10% of 62 sources
    • Engineering Blogs & Reviews5, 8% of 62 sources

    Earlier evidence remains when it still applies. Records tied to fixed bugs carry Still applicable only where the account still informs a buyer.

    See sources by origin

    The record

    Who each source is, how it knows, whether it still applies and what it counts toward.

    About this read

    What changed, and how we count

    What changed

    • Oct 30, 2026: adds two Reddit accounts, a three-person team whose Portkey bill passed its hosting bill as a law firm client asked about transcript retention, and a user who saw concurrency trouble when several teams spiked at once; both count toward no figure until their authors' ties are checked. 26 records now show the passage GILD quotes from each source's stored copy, and the Operator Insights add TU Vienna and Glama.
    • Oct 28, 2026: first edition, built from the GitHub, Hacker News, X, and blog accounts GILD's research missions stored on October 28, 2026.
    • Every account links to its public source and names its author and publication date.
    • A finding shows only when at least 5 sources from 3 different authors discuss it. A disagreement also requires at least 2 sources on each side.
    • Counts practitioners who describe their own use or evaluation of Portkey; competitor benchmarks and news reports of the acquisition are excluded.
    • Checks the plan, budget, audit log, and hosting findings against Portkey's pricing page and documentation on the review date.

    Method

    A running review of what teams building AI features on Portkey report, from individual builders to technical leaders. Each finding links to its sources, and each conflict shows both sides.

    Counts cover only the sources GILD reviewed.

    Who counts

    Teams and technical leaders
    Small product team, Product or platform team, Technical leadership, Organization-wide
    Individual builders
    Individual builder
    All practitioners
    Everyone in the teams and leaders and individual builders groups

    Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.

    How the numbers work

    • Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among technical leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
    • Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +4 mixed (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
    • Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +6 Mixed; with one vote per author it reads +4 Mixed. No evidence changed.
    • Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
    • Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
    • Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
    • Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
    • Disagreements. The count on each side. GILD names no winner and gives no share of all users.
    • Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.

    Labels on a source

    A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.

    Documented
    Stated in official documentation.
    Reported
    A practitioner's account of their own use.
    Measured
    Backed by the source's own measurements, such as a comparative test or tracked team metrics.
    GILD analysis
    GILD's check of a claim against official documentation.
    Current
    Describes the product as it is now.
    Still applicable
    Older, and the behavior or lesson still holds.
    Needs a recheck
    May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
    Out of date
    No longer accurate. Kept in the record; counts toward nothing current.

    Flagged for a recheck, of the sources that take a side: teams and leaders 0 of 18, individual builders 0 of 32, all practitioners 0 of 50.

    Limits

    • These figures describe reviewed sources; they do not represent all Portkey customers. GitHub issues and pull requests supply 38 of the 53 sources, and bug reports tilt toward problems, so a bug report counts as negative unless its author also states what works. Four PeerSpot reviews by named engineers are counted; PeerSpot can invite reviews, which tilts that channel positive. Portkey's own case studies and testimonials, and comparison posts by competing gateway vendors, are kept out of the count. GILD found no first-hand account from a customer of Prisma AIRS AI Gateway since the acquisition. Two Reddit accounts count toward no figure until their authors' ties to Portkey are checked.
    • Sources cover the hosted service and the open-source gateway from July 2025 to October 2026, across Palo Alto Networks' purchase on May 29, 2026 and the Prisma AIRS AI Gateway launch on July 16, 2026. Most gateway issues name version 1.15.2, the last release, from January 12, 2026.

    Every count, and the sources behind it

    13 findings for 3 groups

    Each row opens its sources for the group you are reading.

    FindingTeams and technical leadersIndividual buildersAll practitionersSources
    Current readCurrent sentiment11 positive, 4 mixed, 3 negative9 positive, 7 mixed, 16 negative20 positive, 11 mixed, 19 negativeSources
    PraiseOne API with Fallbacks10 of 10 positive6 of 7 positive16 of 17 positiveSources
    PraiseRequest Logs & Cost Data6 of 6 positive2 of 2 positive (under the minimum)8 of 8 positiveSources
    PraiseOpen-Source Gateway2 of 2 positive (under the minimum)2 of 2 positive (under the minimum)4 of 4 positive (under the minimum)Sources
    PraiseGateway Speed0 of 0 positive (under the minimum)1 of 1 positive (under the minimum)1 of 1 positive (under the minimum)Sources
    ConcernProvider Translation Bugs1 of 2 raise it (under the minimum)13 of 13 raise it14 of 15 raise itSources
    ConcernReliability & Streaming Bugs2 of 3 raise it (under the minimum)6 of 6 raise it8 of 9 raise itSources
    ConcernOpen-Source Maintenance0 of 0 raise it (under the minimum)5 of 5 raise it5 of 5 raise itSources
    ConcernSecurity Flaws0 of 0 raise it (under the minimum)1 of 1 raise it (under the minimum)1 of 1 raise it (under the minimum)Sources
    ConcernOwnership & Direction1 of 1 raise it (under the minimum)1 of 1 raise it (under the minimum)2 of 2 raise it (under the minimum)Sources
    ConcernEnterprise-Gated Features0 of 0 raise it (under the minimum)0 of 0 raise it (under the minimum)0 of 0 raise it (under the minimum)Sources
    DisagreementWhen practitioners weigh Portkey against another gateway or their own code, which do they keep?Chose or kept Portkey 3, Forked it or built their own 0 (under the minimum)Chose or kept Portkey 1, Forked it or built their own 1 (under the minimum)Chose or kept Portkey 4, Forked it or built their own 1 (under the minimum)Sources
    Current readEvidence mix30 sources38 sources62 sourcesSources

    Fact checks

    GILD's checks of claims against official documentation, kept apart from the source counts.