Portkey is a commercial gateway that sits between an application and the LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. providers it calls, deployed as a hosted or hybrid service and integrated with a few lines of code so every request is logged, rate-limited, and routed through one place. It fetches provider credentials at runtime from vaults like AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault rather than storing keys itself, and it can block requests at the gateway that lack required metadata or fail a guardrail check, with partners like Zscaler AI Guard and Akto screening for policy violations and prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools.. It is built for teams running LLM applications in production who need spend and rate controls, audit logging, and provider-level access management in one layer. Launched in 2023, it ships releases roughly monthly and was last updated 34 days ago.
Where are my LLM provider keys actually stored, and can I keep them out of this layer entirely?
fetches credentials at request time from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault via a mapping, rather than holding the key value itself
Is a team about to blow through its weekly spend or hammer one endpoint too hard?
tracks usage against configurable weekly windows and lets chat completions, embeddings, and admin routes each carry their own limit, so one route maxing out doesn't starve the others
Is this prompt or response carrying an injection attempt or a policy violation before it reaches the user?
routes the input and output through partner checks like Zscaler AI Guard or Akto at the gateway's request and response hooks, blocking on a failed check
Can I get my gateway logs into Google Cloud Storage without handing out a long-lived GCP key?
delivers logs from an AWS-hosted gateway to GCS using workload identity federation, authenticating with a short-lived federated identity instead of a stored credential
Am I looking at the full picture when I pull up usage graphs, including workspaces that were archived?
lets an admin include archived workspaces in analytics filters and accepts workspace slugs alongside IDs, so a retired workspace's history doesn't silently disappear from the numbers
Built from Portkey's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+AI Gateway Routing and Provider Support7 capabilitiesPortkey acts as a central gateway that routes LLM requests to a growing set of providers and model types. It handles request forwarding, provider-specific translation, and surface-level protocol concerns so applications talk to one consistent interface.▸
+Model catalog APIshippedProvides an API endpoint that lists all models Portkey supports, regardless of which provider or config is active on the request.12 releases · 2 other sources · first seen Aug 2025▸
Also counts toward: REST API
release
12 total
Model Catalog GET provider details accepts include_configurations=true to retrieve system auth configs with masked secrets.
Backend 1.22.0 · Aug 2026
· source
· release history
Adds fetch_integrated_models config flag and x-portkey-models-endpoint request header to fetch the integrated catalog model list through the Gateway
Backend 1.18.0 · Jun 2026
· source
· release history
Adds the x-portkey-fetch-integrated-models HTTP header and fetch_integrated_models config field to force GET /v1/models to return gateway-configured models regardless of routing signals
Enterprise Gateway 2.11.2 · Jun 2026
· source
· release history
gpt5.1 models are now supported
Frontend 1.5.1 · Nov 2025
· source
· release history
Supports transcribe models under Azure and OpenAI providers
Frontend 1.4.9 · Nov 2025
· source
· release history
Added gpt-5-codex, gpt-5-pro, and several other OpenAI and Azure-OpenAI models
Frontend 1.4.6 · Oct 2025
· source
· release history
docs
- [Models](https://docs.portkey.ai/docs/api-reference/inference-api/models/models.md): Retrieve the list of models available in your…
docs update · seen Jul 2026
· source
### Fetch Integrated Models Applies to GET /v1/models only. When true, forces the endpoint to return Portkey's integrated (Model Catalog) models even when a provider or config is passed on the request. Without this header, any provider signal causes the endpoint to proxy to the upstream provider's /v1/models.
docs update · seen Jul 2026
· source
+DeepSeek enhanced model capabilitiesshippedExtends DeepSeek model support with tool calling, streaming options, and exposure of chain-of-thought reasoning content.13 releases · first seen Nov 2025▸
release
13 total
Adds tools, tool_choice, and stream_options for deepseek-chat; maps reasoning_effort to thinking mode and surfaces reasoning_content in streams for deepseek-reasoner.
updated · seen Aug 2026
· source
· release history
Adds stream_options support for DeepSeek deepseek-chat, and maps reasoning_effort to thinking mode for deepseek-reasoner, returning reasoning_content in streams.
updated · seen Aug 2026
· source
· release history
Extends DeepSeek support: deepseek-chat gains tools, tool_choice, and stream_options; deepseek-reasoner maps reasoning_effort to thinking mode and surfaces reasoning_content in streams.
updated · seen Jul 2026
· source
· release history
Adds DeepSeek deepseek-chat tool calling (tools, tool_choice, stream_options) and deepseek-reasoner reasoning effort mapping with reasoning_content in streams.
updated · seen Jul 2026
· source
· release history
Adds tool_choice, stream_options, and streaming usage reporting to DeepSeek deepseek-chat; maps reasoning_effort to thinking mode and surfaces reasoning_content in streams for deepseek-reasoner.
updated · seen Jul 2026
· source
· release history
DeepSeek deepseek-chat gains tools, tool_choice, and stream_options; deepseek-reasoner maps reasoning_effort to thinking mode and returns reasoning_content in streams.
updated · seen Jul 2026
· source
· release history
+Vertex AI enterprise web search groundingshippedEnables grounded web search on Vertex AI requests with cost attribution, metadata label mapping, and cross-cloud access via Workload Identity Federation.13 releases · first seen Mar 2026▸
release
13 total
Maps Portkey metadata to Vertex AI resource labels; adds enterprise search grounding via enterpriseWebSearch / enterprise_web_search; enables AWS workloads to reach Vertex AI using GCP_WIF_AUDIENCE and GCP_WIF_SERVICE_ACCOUNT_EMAIL.
updated · seen Aug 2026
· source
· release history
Adds Vertex AI enterprise search grounding via enterpriseWebSearch / enterprise_web_search (with separate cost attribution) and AWS-to-Vertex connectivity using GCP_WIF_AUDIENCE / GCP_WIF_SERVICE_ACCOUNT_EMAIL.
updated · seen Aug 2026
· source
· release history
Adds Vertex AI resource label support by mapping Portkey metadata to Vertex resource labels.
updated · seen Aug 2026
· source
· release history
Adds Vertex AI enterprise web search grounding via enterpriseWebSearch / enterprise_web_search with separate cost attribution, Portkey metadata mapping to Vertex resource labels, and AWS-to-Vertex access via GCP_WIF_AUDIENCE and GCP_WIF_SERVICE_ACCOUNT_EMAIL.
updated · seen Aug 2026
· source
· release history
Enables AWS workloads to reach Vertex AI through AWS–GCP Workload Identity Federation (GCP_WIF_AUDIENCE, GCP_WIF_SERVICE_ACCOUNT_EMAIL).
updated · seen Jul 2026
· source
· release history
Maps Portkey metadata to Vertex AI resource labels and adds enterprise web search grounding via enterpriseWebSearch/enterprise_web_search.
updated · seen Jul 2026
· source
· release history
+DeepInfra provider supportshippedAdds DeepInfra as a supported provider, covering text completions, embeddings, and tool calling.8 releases · first seen Oct 2024▸
release
8 total
Adds DeepInfra provider support with tool calling via tools, tool_choice, and parallel_tool_calls, plus completions and embeddings endpoints.
updated · seen Aug 2026
· source
· release history
Adds DeepInfra provider support with tool calling (tools, tool_choice, parallel_tool_calls), chat completions, and embeddings.
updated · seen Jul 2026
· source
· release history
Supports DeepInfra tool calling (tools, tool_choice, parallel_tool_calls) plus completions and embeddings endpoints.
updated · seen Jul 2026
· source
· release history
DeepInfra provider adds tool calling (tools, tool_choice, parallel_tool_calls) plus completions and embeddings endpoints.
updated · seen Jul 2026
· source
· release history
Adds DeepInfra provider support with tool calling (tools, tool_choice, parallel_tool_calls), completions, and embeddings endpoints.
updated · seen Jul 2026
· source
· release history
Adds tool_choice and parallel_tool_calls parameters to the DeepInfra integration for function calling workflows
Enterprise Gateway 2.4.0 · Mar 2026
· source
· release history
+Azure AI Foundry Cohere rerank supportshippedEnables reranking via Cohere models hosted on Azure AI Foundry, with automatic prefix handling before the request reaches the provider.7 releases · first seen Jan 2026▸
release
7 total
Adds Azure AI Foundry rerank support for Cohere rerank models (e.g. cohere.Cohere-rerank-v4.0-pro), with the gateway stripping the cohere. prefix for the provider.
updated · seen Jul 2026
· source
· release history
Adds Azure AI Foundry rerank support for Cohere rerank models (e.g., cohere.Cohere-rerank-v4.0-pro), with the gateway stripping the cohere. prefix for the provider.
updated · seen Jul 2026
· source
· release history
Azure AI Foundry gains Cohere rerank model support (e.g. cohere.Cohere-rerank-v4.0-pro); gateway strips the cohere. prefix for the provider.
updated · seen Jul 2026
· source
· release history
Supports Azure AI Foundry rerank with Cohere rerank models (e.g. cohere.Cohere-rerank-v4.0-pro), with the gateway stripping the cohere. prefix automatically.
updated · seen Jul 2026
· source
· release history
Supports Vertex AI Rerank on the unified /v1/rerank endpoint using semantic-ranker-default, semantic-ranker-fast, or semantic-ranker-512 models
Enterprise Gateway 2.7.0 · Apr 2026
· source
· release history
Azure AI Foundry now supports reranking via Cohere models (e.g., cohere.Cohere-rerank-v4.0-pro) with automatic stripping of the cohere. prefix
Enterprise Gateway 2.3.0 · Mar 2026
· source
· release history
+Bedrock batch inference for embeddingsshippedAllows embeddings jobs to be submitted to AWS Bedrock as batch inference tasks, alongside existing chat batch support.5 releases▸
release
Extends Bedrock batch inference to support embeddings jobs alongside existing chat completions batch patterns.
updated · seen Jul 2026
· source
· release history
Extends Bedrock batch inference to cover embeddings in addition to chat completions.
updated · seen Jul 2026
· source
· release history
Extends Bedrock batch inference to support embeddings in addition to chat completions.
updated · seen Jul 2026
· source
· release history
Bedrock batch inference now supports embeddings in addition to chat completions.
updated · seen Jul 2026
· source
· release history
Extends Bedrock batch inference to support embeddings jobs alongside existing chat completion batch patterns.
updated · seen Jul 2026
· source
· release history
+Header forwarding loop preventionshippedStrips a forwarding header from outbound requests to prevent the gateway from accidentally routing a request back into itself.1 release▸
release
The gateway no longer forwards the x-portkey-forward-headxers header, preventing header-forwarding loops — any setup relying on that header being passed through will stop working.
updated · seen Aug 2026
· source
· release history
+Policy Enforcement and Guardrails4 capabilitiesPortkey applies configurable guardrails at the gateway layer to inspect and block LLM traffic before it reaches a model or after it returns. These controls cover content policy, prompt injection, sensitive data, and structural request requirements.▸
+Zscaler AI Guard guardrail integrationshippedApplies Zscaler Detection Policies to both incoming prompts and model responses, blocking traffic that violates organisational rules at the gateway.20 releases · 7 other sources · first seen Jan 2025▸
release
20 total
The forwardHeaders parameter is removed from Portkey-managed PRO check schemas (portkey.moderateContent, portkey.language, portkey.pii, portkey.gibberish)
Backend 1.24.2 · Aug 2026
· source
· release history
The forwardHeaders parameter is removed from 22 local-only guardrail check schemas (regex, model allowlist, word count, etc.) where it had no effect
Backend 1.24.1 · Aug 2026
· source
· release history
Integrates Zscaler AI Guard as a guardrail partner via beforeRequestHook and afterRequestHook, requiring a policyId and supporting a configurable timeout (default 10000 ms).
updated · seen Aug 2026
· source
· release history
Adds Zscaler AI Guard guardrail integration applying Zscaler Detection Policies via beforeRequestHook / afterRequestHook, with required policyId and optional timeout (default 10 000 ms).
updated · seen Aug 2026
· source
· release history
Adds Zscaler AI Guard guardrail integration using beforeRequestHook and afterRequestHook hooks, requiring a policyId and supporting a configurable timeout (default 10000 ms) to apply Zscaler Detection Policies to LLM inputs and outputs.
updated · seen Aug 2026
· source
· release history
Adds GET /v1/workspace-exclusions/input-guardrails and /v1/workspace-exclusions/output-guardrails to exempt workspaces from org-level defaults.
Backend 1.22.0 · Aug 2026
· source
· release history
example
7 total
Apply Zscaler AI Guard detection policies to all LLM requests and responses with a custom evaluation timeout.$ { "guardrails": [ { "provider": "zscaler", "hooks": ["beforeRequestHook", "afterRequestHook"], "policyId": "your-zscaler-policy-id", "timeout": 8000 } ] }
updated · seen Aug 2026
· source
Apply Zscaler Detection Policies to all LLM traffic by wiring Zscaler AI Guard into your Portkey config as a guardrail hook.$ { "guardrails": [ { "type": "zscaler", "hooks": ["beforeRequestHook", "afterRequestHook"], "policyId": "<your-zscaler-policy-id>", "timeout": 10000 } ] }
updated · seen Jul 2026
· source
Apply Zscaler AI Guard detection policies to all LLM inputs and outputs by wiring in your existing policyId.$ { "guardrails": [ { "type": "zscaler", "hooks": ["beforeRequestHook", "afterRequestHook"], "policyId": "<your-zscaler-policy-id>", "timeout": 10000 } ] }
updated · seen Jul 2026
· source
Apply Zscaler Detection Policies to all LLM traffic through Portkey so your existing Zscaler policy class governs both inputs and outputs.$ Add Zscaler AI Guard as a guardrail with your policyId: { "guardrails": { "beforeRequestHook": { "provider": "zscaler", "policyId": "<your-zscaler-policy-id>", "timeout": 10000 }, "afterRequestHook":…
updated · seen Jul 2026
· source
Gate every agentic request through Zscaler AI Guard so your existing Zscaler Detection Policies apply to LLM inputs and outputs.$ In your Portkey config, add the Zscaler AI Guard guardrail with your policyId: { "guardrails": { "beforeRequestHook": { "provider": "zscaler", "policyId": "<your-zscaler-policy-id>", "timeout": 10000…
updated · seen Jul 2026
· source
Route Zscaler AI Guard policy checks across all LLM traffic to enforce your org's existing detection policies on inputs and outputs.$ { "guardrails": [ { "type": "zscaler", "beforeRequestHook": true, "afterRequestHook": true, "policyId": "<your-zscaler-policy-id>", "timeout": 10000 } ] }
updated · seen Jul 2026
· source
+Required metadata key–value guardrailsshippedBlocks any request that is missing required metadata fields or carries invalid values before it is forwarded to the model.16 releases · 1 other source · first seen Nov 2025▸
release
16 total
Portkey adds a new lifecycle stage to inspect traffic before it reaches a model.
changelog · Oct 2026
· source
· release history
Adds required metadata key–value guardrails that block requests missing or carrying invalid required metadata fields before they reach the model.
updated · seen Aug 2026
· source
· release history
Adds required metadata key–value guardrails that block requests at the gateway before they reach the model if required metadata fields are missing or invalid.
updated · seen Aug 2026
· source
· release history
Adds required metadata key–value guardrails that block requests missing specified metadata fields before they reach the model.
updated · seen Jul 2026
· source
· release history
Adds required metadata key–value guardrails that block requests missing specified fields before they reach the model.
updated · seen Jul 2026
· source
· release history
Adds required metadata key–value guardrails that block requests missing or carrying invalid metadata fields before they reach the model.
updated · seen Jul 2026
· source
· release history
example
Gate every request so it must carry a user_id metadata field — the gateway blocks the call before it hits the model if the field is absent.$ { "guardrails": [ { "type": "required_metadata", "required_keys": ["user_id", "session_id"] } ] }
updated · seen Jul 2026
· source
+Bedrock Guardrails custom host routingshippedRoutes Bedrock guardrail evaluation to private or regional endpoints instead of the default public Bedrock URLs.9 releases · 1 other source · first seen Jan 2025▸
Also counts toward: Plugin API support
release
9 total
Adds customHost configuration to the Bedrock guardrail plugin so evaluations can target private or regional Bedrock-compatible endpoints instead of the default public Bedrock URLs.
updated · seen Aug 2026
· source
· release history
Adds customHost to the Bedrock Guardrails plugin, routing guardrail evaluation to private or regional Bedrock-compatible endpoints.
updated · seen Jul 2026
· source
· release history
Adds customHost support for the Bedrock Guardrails plugin so evaluations route to private or regional Bedrock-compatible endpoints.
updated · seen Jul 2026
· source
· release history
Adds customHost support on the Bedrock Guardrails plugin so guardrail evaluation hits private or regional Bedrock-compatible endpoints instead of default public URLs.
updated · seen Jul 2026
· source
· release history
Bedrock Guardrails plugin now accepts a customHost field to route guardrail evaluation to private or regional Bedrock-compatible endpoints.
updated · seen Jul 2026
· source
· release history
Adds customHost on the Bedrock Guardrails plugin so guardrail evaluation can target private or regional Bedrock-compatible endpoints.
updated · seen Jul 2026
· source
· release history
example
Route Bedrock guardrail evaluation to a private regional endpoint instead of the default public Bedrock URL.$ In the Portkey console, open the Bedrock guardrail plugin configuration and set `customHost` to your private or regional Bedrock-compatible endpoint URL.
updated · seen Jul 2026
· source
+Akto Agentic Security guardrail integrationshippedScans LLM inputs and outputs for prompt injection attempts and sensitive data leakage, with configurable hooks suited to agentic traffic.9 releases · 1 other source · first seen Mar 2026▸
release
9 total
Adds Akto Agentic Security as a guardrails partner to scan LLM inputs and outputs for prompt injection and sensitive data leakage via hooks with a configurable timeout (default 5000 ms).
updated · seen Aug 2026
· source
· release history
Integrates Akto Agentic Security as a guardrail partner for scanning LLM inputs and outputs for prompt injection and sensitive data leakage.
updated · seen Jul 2026
· source
· release history
Integrates Akto Agentic Security as a guardrail partner to scan LLM traffic for prompt injection and sensitive data leakage.
updated · seen Jul 2026
· source
· release history
Integrates Akto Agentic Security as a guardrails partner to scan LLM traffic for prompt injection and sensitive data leakage via configurable hooks and timeout.
updated · seen Jul 2026
· source
· release history
New Akto Agentic Security guardrail scans LLM inputs and outputs for prompt injection and sensitive data leakage with configurable hook and timeout.
updated · seen Jul 2026
· source
· release history
Integrates Akto Agentic Security as a guardrail partner to scan for prompt injection and sensitive data leakage on agentic traffic.
updated · seen Jul 2026
· source
· release history
docs
* Scan Scope: Controls which messages are scanned (optional, defaults to last_message) * Strip Scaffolding: Removes known agent-harness wrappers before scanning (optional, defaults to false) | -------------------------- |…
docs update · seen Jul 2026
· source
+Credential and Secret Management3 capabilitiesPortkey retrieves LLM provider credentials from external vaults at request time rather than storing them in its own configuration. It also supports cross-cloud identity federation to avoid long-lived static keys in multi-cloud deployments.▸
+GCP Workload Identity Federation log deliveryshippedDelivers gateway logs from AWS-hosted instances to Google Cloud Storage using GCP Workload Identity Federation, removing the need for static cross-cloud service account keys.12 releases · 5 other sources · first seen Jan 2025▸
release
12 total
Adds GCP_WIF_AUDIENCE and GCP_WIF_SERVICE_ACCOUNT_EMAIL environment variables to authenticate GCS log writes through GCP Workload Identity Federation (gcs_assume flow) when the gateway runs in AWS, eliminating long-lived GCP keys in AWS config.
updated · seen Aug 2026
· source
· release history
Adds GCP_WIF_AUDIENCE and GCP_WIF_SERVICE_ACCOUNT_EMAIL environment variables to enable GCP Workload Identity Federation (gcs_assume style) for GCS log delivery when the gateway runs in AWS, eliminating static cross-cloud credentials.
updated · seen Aug 2026
· source
· release history
Enables GCP Workload Identity Federation log delivery from AWS-hosted gateways to GCS via GCP_WIF_AUDIENCE and GCP_WIF_SERVICE_ACCOUNT_EMAIL, eliminating long-lived cross-cloud keys.
updated · seen Jul 2026
· source
· release history
Enables GCS log storage from AWS-hosted gateways via GCP Workload Identity Federation (GCP_WIF_AUDIENCE, GCP_WIF_SERVICE_ACCOUNT_EMAIL), eliminating long-lived cross-cloud credentials.
updated · seen Jul 2026
· source
· release history
Enables GCP Workload Identity Federation log storage (gcs_assume) from AWS-hosted gateways via GCP_WIF_AUDIENCE and GCP_WIF_SERVICE_ACCOUNT_EMAIL, eliminating static GCP keys in AWS.
updated · seen Jul 2026
· source
· release history
Enables GCP Workload Identity Federation log delivery from AWS-hosted gateways to Google Cloud Storage via GCP_WIF_AUDIENCE and GCP_WIF_SERVICE_ACCOUNT_EMAIL, eliminating long-lived GCP keys in AWS.
updated · seen Jul 2026
· source
· release history
example
Ship GCS logs from an AWS-hosted gateway without storing long-lived GCP credentials — set both WIF env vars and use the gcs_assume log storage flow.$ GCP_WIF_AUDIENCE=//iam.googleapis.com/projects/123/locations/global/workloadIdentityPools/my-pool/providers/my-provider \…
updated · seen Aug 2026
· source
Route GCS log writes through GCP Workload Identity Federation when the Portkey gateway runs in AWS, avoiding static GCP service-account keys.$ GCP_WIF_AUDIENCE=//iam.googleapis.com/projects/123456/locations/global/workloadIdentityPools/my-pool/providers/my-provider \…
updated · seen Aug 2026
· source
Route GCS log writes through GCP Workload Identity Federation when the Portkey gateway runs in AWS, avoiding long-lived GCP credentials in your AWS environment.$ GCP_WIF_AUDIENCE=//iam.googleapis.com/projects/123456/locations/global/workloadIdentityPools/my-pool/providers/my-provider \…
updated · seen Aug 2026
· source
Route GCP Cloud Storage log writes from an AWS-hosted gateway through Workload Identity Federation to avoid storing long-lived GCP service account keys in AWS.$ Set these environment variables on your gateway deployment: GCP_WIF_AUDIENCE=<your-wif-audience> GCP_WIF_SERVICE_ACCOUNT_EMAIL=<your-sa>@<project>.iam.gserviceaccount.com
updated · seen Jul 2026
· source
Ship gateway logs from AWS to GCS using Workload Identity Federation — no long-lived GCP keys required.$ GCP_WIF_AUDIENCE=<your-wif-audience> GCP_WIF_SERVICE_ACCOUNT_EMAIL=<your-service-account>@<project>.iam.gserviceaccount.com # Set log storage mode to gcs_assume in your gateway config
updated · seen Jul 2026
· source
+Secret References (external vault credential fetching)shippedFetches provider API keys at runtime from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault, so credentials are never stored inside Portkey config.12 releases · 4 other sources · first seen Mar 2026▸
release
12 total
Adds Secret References so secret_mappings can point virtual keys and integrations at credentials stored in AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault — Portkey fetches values at runtime instead of storing keys directly.
updated · seen Aug 2026
· source
· release history
Adds Secret References so credentials stored in AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault are fetched at runtime via secret_mappings, keeping plaintext keys out of Portkey config.
updated · seen Aug 2026
· source
· release history
Adds Secret References so credentials stored in AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault can be mapped to integrations and virtual keys via secret_mappings, with Portkey fetching values at runtime instead of storing them directly.
updated · seen Aug 2026
· source
· release history
Adds Secret References to pull credentials from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault at runtime via secret_mappings, keeping secrets out of Portkey config.
updated · seen Jul 2026
· source
· release history
Adds Secret References so virtual keys and integrations can pull credentials at runtime from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault via secret_mappings, keeping secrets out of Portkey config.
updated · seen Jul 2026
· source
· release history
Adds Secret References so Portkey fetches credentials at runtime from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault via secret_mappings, keeping keys out of Portkey config entirely.
updated · seen Jul 2026
· source
· release history
example
Keep LLM provider credentials out of Portkey by pointing a virtual key at a secret already stored in AWS Secrets Manager.$ { "virtual_key": "my-openai-key", "secret_mappings": { "api_key": "arn:aws:secretsmanager:us-east-1:123456789012:secret:prod/openai-api-key" } }
updated · seen Aug 2026
· source
Pull API keys from your own vault at request time instead of storing them in Portkey — critical for orgs with strict secrets governance.$ In the Portkey console, go to your Virtual Key or Integration settings and add a `secret_mappings` block pointing to your AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault path.
updated · seen Jul 2026
· source
Pull LLM provider credentials from your existing vault at runtime instead of storing keys in Portkey directly.$ In the Portkey console, go to Settings > Integrations (or Virtual Keys) and add a secret_mappings entry pointing to your AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault secret ARN/path.
updated · seen Jul 2026
· source
Keep LLM provider keys out of Portkey by pointing a virtual key at a secret stored in AWS Secrets Manager — Portkey fetches the value at request time.$ { "virtual_key": "my-openai-key", "secret_mappings": { "api_key": "arn:aws:secretsmanager:us-east-1:123456789012:secret:openai-api-key-AbCdEf" } }
updated · seen Jul 2026
· source
+Hybrid deploymentshippedSupports a hybrid deployment model where the gateway runs in the customer's own infrastructure alongside cloud-hosted Portkey components.5 releases · 1 other source · first seen Feb 2025▸
release
Improves JWT authentication resilience in hybrid deployments by trying direct JWKS fetching before falling back to private link routing
Backend 1.24.2 · Aug 2026
· source
· release history
Added configurable MySQL reader with HADR mode using new env vars DB_READER_HOST, DB_READER_USER, DB_READER_PASS, DB_READER_PORT and MYSQL_WRITER_HADR_MODE=ON for writer failover
Backend 1.14.0 · Apr 2026
· source
· release history
Adds EKS Pod Identity integration with IRSA for EKS clusters
Enterprise Gateway 1.16.4 · Oct 2025
· source
· release history
Adds support for APAC cross region inference profiles in the AWS Bedrock provider configuration
Enterprise Gateway 1.15.3 · Sep 2025
· source
· release history
Implemented cluster mode Redis for queues.
Data Service 1.1.2 · Feb 2025
· source
· release history
+Usage Controls and Rate Limiting2 capabilitiesPortkey lets teams enforce spend caps and throughput limits at different granularities, from per-endpoint rules to weekly budget windows. These controls are applied at the gateway so they apply consistently across all callers.▸
+Flexible usage limits and rate limit policiesshippedAdds weekly budget and usage windows so spend caps can align with weekly planning cycles rather than only minute-by-minute or monthly limits.17 releases · 2 other sources · first seen Oct 2024▸
previously: Weekly rate and budget windows
release
17 total
Adds weekly (rpw) budget and usage windows so rate-limit caps align with weekly spend planning, not only per-minute or monthly aggregates.
updated · seen Aug 2026
· source
· release history
Adds weekly budget/usage windows (rpw) and endpoint-scoped rate limits, letting teams cap spend per API surface (chat completions, embeddings, admin routes) independently.
updated · seen Aug 2026
· source
· release history
Adds rpw (requests-per-week) budget and usage windows so rate limits can align with weekly planning cycles, alongside endpoint-scoped limits that let chat completions, embeddings, and admin routes carry independent caps.
updated · seen Aug 2026
· source
· release history
Introduces weekly rate/budget windows (rpw) and endpoint-scoped rate limits, letting teams cap spend per API surface (chat completions, embeddings, admin routes, etc.) independently.
updated · seen Jul 2026
· source
· release history
Supports weekly budget and usage windows (rpw) for rate limits, enabling caps aligned to weekly planning and review cycles.
updated · seen Jul 2026
· source
· release history
Supports weekly budget and usage windows (rpw) for rate-limit policies so spend caps align with weekly planning cycles.
updated · seen Jul 2026
· source
· release history
example
Set a weekly spend cap scoped only to the embeddings endpoint so it doesn't share budget with chat completions.$ In the Portkey console, go to Budget & Rate Limit Policies, create a new policy, set the window to `rpw` (weekly), set the endpoint scope to `embeddings`, and enter your desired token or cost limit.
updated · seen Jul 2026
· source
Cap a team's weekly LLM spend and keep chat completions under a separate limit from embeddings calls.$ In the Portkey console, open Budget & Rate Limit Policies, set a `rpw` (requests-per-week) budget window for the relevant virtual key or config, then add an endpoint-scoped limit targeting the chat…
updated · seen Jul 2026
· source
+Endpoint-scoped rate limitsshippedAllows independent rate limits to be set per endpoint type, such as chat completions versus embeddings, rather than sharing a single global limit.6 releases · first seen Mar 2026▸
release
Adds endpoint-scoped rate limits so chat completions, embeddings, and admin routes can each carry independent limits instead of one global rule.
updated · seen Aug 2026
· source
· release history
Adds endpoint-scoped rate limits so chat completions, embeddings, and admin routes can carry independent limits instead of a single global rule.
updated · seen Jul 2026
· source
· release history
Adds endpoint-scoped rate limits so chat completions, embeddings, and admin routes can each carry independent limits instead of a single global cap.
updated · seen Jul 2026
· source
· release history
Adds endpoint-scoped rate limits so chat completions, embeddings, and admin routes can each carry independent limits instead of a single global rule.
updated · seen Jul 2026
· source
· release history
Supports weekly budget/usage windows (rpw) and endpoint-scoped rate limits, letting teams cap chat completions, embeddings, and admin routes independently.
updated · seen Jul 2026
· source
· release history
Adds endpoint-scoped rate limits by endpoint type (e.g., chat completions, embeddings) to apply different limits to different API surfaces.
March 2026 · Mar 2026
· source
· release history
+Observability and Analytics2 capabilitiesPortkey captures structured telemetry from gateway traffic and exposes it through analytics and tracing integrations. Teams can inspect guardrail activity, multi-cloud log delivery, and usage across active and archived workspaces.▸
+OpenTelemetry GenAI semantic conventions and guardrail tracingshippedEmits OpenTelemetry spans following the latest GenAI semantic conventions, including trace coverage of guardrail flows and support for custom resource attributes used by downstream APM tools.24 releases · first seen Nov 2023▸
release
24 total
Adds configurable guardrail header forwarding, allowing client headers like x-session-id and traceparent to be sent to upstream providers
Enterprise Gateway 2.18.0 · Aug 2026
· source
· release history
OpenTelemetry GenAI semantic spans now follow semconv 1.40.0 for inference and embeddings, with OTEL exporter support for guardrail flows and custom resource attributes.
updated · seen Aug 2026
· source
· release history
Updates OpenTelemetry GenAI semantic spans to semconv 1.40.0 for inference and embeddings, with OTEL exporter support for guardrail flows and custom resource attributes.
updated · seen Jul 2026
· source
· release history
Updates OpenTelemetry GenAI semantic spans to semconv 1.40.0, adds OTEL exporter support for guardrail flows, and supports custom resource attributes for downstream APM and tracing.
updated · seen Jul 2026
· source
· release history
Updates OpenTelemetry GenAI semantic spans to semconv 1.40.0, adds OTEL exporter support for guardrail flows, and supports custom resource attributes for downstream APM standardization.
updated · seen Jul 2026
· source
· release history
Attaches Portkey tenant attributes (org_id, workspace, environment) to Gen AI and guardrail OTel spans for per-tenant filtering
Enterprise Gateway 2.13.0 · Jun 2026
· source
· release history
+Archived workspace analytics inclusionshippedLets organisation admins include archived workspaces in analytics views and filter queries, so historical usage is not silently excluded from reporting.7 releases▸
release
7 total
Enables analytics for archived workspaces and accepts workspace slugs (alongside IDs) in saved filters, keeping reporting stable as workspaces are wound down or renamed.
updated · seen Aug 2026
· source
· release history
Extends analytics so organization admins and owners can include archived workspaces in graphs and summaries; saved filters now accept workspace slugs alongside IDs.
updated · seen Aug 2026
· source
· release history
Allows organization admins to include archived workspaces in analytics graphs and summaries; saved filters now accept workspace slugs alongside IDs.
updated · seen Jul 2026
· source
· release history
Lets organization admins include archived workspaces in analytics graphs and filters, with workspace slugs now accepted alongside IDs in saved filters.
updated · seen Jul 2026
· source
· release history
Allows organization admins to include archived workspaces in analytics graphs and filters; saved filters now also accept workspace slugs alongside IDs.
updated · seen Jul 2026
· source
· release history
Organization admins can now include archived workspaces in analytics graphs and filters; saved filters also accept workspace slugs alongside IDs.
updated · seen Jul 2026
· source
· release history
+Other36 capabilities▸
+Provider supportshippedAdds gateway integration for new AI providers including Lambda, Stability AI (images), AWS SageMaker, and Ollama/Groq tool calling capabilities.69 releases · first seen Oct 2024▸
release
69 total
Extends xAI provider to support image generation with OpenAI-compatible parameters plus xAI-specific aspect ratio and resolution controls.
changelog · Oct 2026
· source
· release history
Adds Anthropic-protocol auto-detection on /v1/models so Claude Code and other Anthropic-native clients receive Anthropic's native model shape instead of the OpenAI-normalized shape.
changelog · Oct 2026
· source
· release history
Adds DashScope as a supported provider on the /v1/images/generations endpoint with region-based pricing attribution in logs.
Enterprise Gateway 2.26.0 · Oct 2026
· source
· release history
Wires Retrieve, delete, and list input items endpoints for xAI, DashScope, Perplexity, and Azure OpenAI providers via the Responses API.
Enterprise Gateway 2.25.1 · Sep 2026
· source
· release history
Streams thinking phase as a thinking content block in the Messages API instead of dropping it for routed reasoning models.
Enterprise Gateway 2.25.1 · Sep 2026
· source
· release history
Adds native routing for /v1/audio/speech and /v1/audio/transcriptions to ElevenLabs without custom host configuration
Enterprise Gateway 2.23.0 · Sep 2026
· source
· release history
+Security guardrails integrationsshippedScreens LLM prompts and responses via Lakera Guard's /v2/guard API, blocking on policy hits and redacting PII spans when only PII detectors fire.40 releases · 1 other source · first seen Jan 2025▸
previously: Lakera Guard guardrail integration
release
40 total
config — Adds piiCategories parameter to Guardrails settings to restrict detection to selected PII categories.
Backend 1.27.0 · Sep 2026
· source
· release history
Adds executeOnProxy parameter to webhook guardrails to run on /v1/* pass-through requests with method, path, and content-type metadata
Backend 1.26.0 · Sep 2026
· source
· release history
Integrates new partner guardrails for AI security scanning (singulr) and Alibaba Cloud's content moderation service
Backend 1.25.0 · Sep 2026
· source
· release history
Introduces Headroom plugin to compress request context before model ingestion, configured via standard guardrails workflow
Enterprise Gateway 2.19.0 · Aug 2026
· source
· release history
Validates Guardrail forwardHeaders at create/update time and defines them in provider schemas for static export
Backend 1.24.0 · Aug 2026
· source
· release history
Adds Soft Deny (200) toggle for guardrails, allowing denied requests to return a 200 response instead of a hard block
Frontend 1.9.4 · Jul 2026
· source
· release history
docs
Lakera Guard screens prompts and responses via the /v2/guard API — blocking on policy hits and redacting PII spans when only pii/* detectors fire. Requires Backend v1.16.2+ Using Lakera with Portkey 1.
docs update · Oct 2026
· source
+Observability enhancementsshippedAdds Prometheus metric labels for detailed tracking and supports sub-paths in S3 bucket names for log storage.19 releases · first seen Nov 2024▸
release
19 total
Adds per-attempt retry logging, giving each retry its own log row with its own status and response instead of only surfacing the final result.
changelog · Oct 2026
· source
· release history
Adds retry_count, response_status, response_headers, and response_body fields to log rows for intermediate retry attempts
Enterprise Gateway 2.24.0 · Sep 2026
· source
· release history
Adds PROMETHEUS_INCLUDE_MODEL_LABEL, PROMETHEUS_INCLUDE_METADATA_LABELS, and PROMETHEUS_LABELS_METADATA_ALLOWED_KEYS environment variables to configure Prometheus metric cardinality.
Enterprise Gateway 2.2.5 · Feb 2026
· source
· release history
Logs display any base64 URL with a Download option
Frontend 1.5.1 · Nov 2025
· source
· release history
Adds llm_token_sum Prometheus metric to track total LLM tokens consumed
Enterprise Gateway 1.16.6 · Nov 2025
· source
· release history
Adds new analytics data point for granular processing time for requests
Enterprise Gateway 1.13.1 · Aug 2025
· source
· release history
+Gateway routing and session persistenceshippedEnables advanced gateway routing capabilities including sticky sessions, forward header mapping, custom upstream host resolution, and automatic handling of overloaded errors.17 releases · first seen Feb 2025▸
release
17 total
Adds startHooks lifecycle stage to screen and normalize traffic before authentication, routing, or other hooks run — including two new checks: Header Check (allow/block by header key-value pairs) and Header Transform (remove, set, or rewrite headers before routing; x-portkey-* headers are protected); existing…
changelog · Oct 2026
· source
· release history
Extends conditional routing to read fields from multipart/form-data requests (image edits, audio transcriptions).
changelog · Oct 2026
· source
· release history
Unstrips interleaved-thinking-2025-05-14 and per-turn-control-2026-07-01 beta headers for Anthropic on Bedrock and Vertex AI.
Enterprise Gateway 2.25.1 · Sep 2026
· source
· release history
Makes vertexRegion config key honored for Vertex AI Rerank requests instead of defaulting to global Discovery Engine
Enterprise Gateway 2.23.0 · Sep 2026
· source
· release history
Config create/update schema validates default_params and drop_params on targets in addition to override_params.
Backend 1.17.0 · May 2026
· source
· release history
Adds anthropicInspectStreamForOverloadedError configuration key to inspect the first chunk of an Anthropic streaming response and return HTTP 529 on overloaded_error, enabling proper retry/fallback logic
Enterprise Gateway 2.7.1 · Apr 2026
· source
· release history
+Authentication hardeningshippedEnforces session-based authentication for specific self-service endpoints and removes legacy authentication endpoints to reduce attack surface.17 releases · first seen May 2025▸
Also counts toward: OIDC SSO
release
17 total
Allows JWT validation to accept comma-separated JWKS URIs for multiple identity providers, fetching keys in parallel
Backend 1.26.0 · Sep 2026
· source
· release history
Gateway-local JWT auth now accepts a comma-separated list of JWKS URLs via jwks_urls for multi-identity validation
Enterprise Gateway 2.21.0 · Sep 2026
· source
· release history
OIDC settings now accept token_endpoint_auth_method and jwks key set, enabling private_key_jwt authentication.
Backend 1.22.0 · Aug 2026
· source
· release history
Adds disable_auto_provision_user auth setting to restrict SSO login to invited users with verified allowed domains
Backend 1.20.0 · Jul 2026
· source
· release history
Adds VITE_PRESELECT_LOGIN_PERMISSION environment variable to pre-select the login permission checkbox on private deployments
Frontend 1.9.2 · May 2026
· source
· release history
Enables hardening of OIDC PKCE flows for SSO authentication and ensures JWT user attribution correctly resolves user email and enforces workspace membership
Backend 1.16.2 · May 2026
· source
· release history
+MCP Gateway management and observabilityshippedProvides a centralized gateway for managing Model Context Protocol servers with authentication, workspace provisioning, and detailed logging.16 releases · first seen Oct 2025▸
Also counts toward: Multi-tenant management, Role-based access control
release
16 total
Portkey now applies guardrails to MCP tool calls, extending coverage beyond standard model request/response traffic.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
changelog · Oct 2026
· source
· release history
Extends MCP Gateway guardrails so MCP tool calls pass through the same pre- and post-execution checks available for LLM requests; denied calls return a structured error with the guardrail and check ID.
changelog · Oct 2026
· source
· release history
Adds capability_ids mappings and run_on values (beforeToolCall, afterToolCall) to attach guardrails to MCP servers
Backend 1.25.0 · Sep 2026
· source
· release history
Enables MCP Registry Proxy in the MCP Gateway to expose registry endpoints like server listings directly through the gateway
Enterprise Gateway 2.19.0 · Aug 2026
· source
· release history
Adds target: mcp_tools to Rate Limit Policies for MCP Gateway enforcement via OAuth introspection and LIST filtering
Backend 1.24.0 · Aug 2026
· source
· release history
Introduces metrics-only logging mode for the MCP gateway, dropping request/response bodies from persisted logs while retaining span info and preserving response bodies on failures
Enterprise Gateway 2.11.2 · Jun 2026
· source
· release history
+Azure authentication mode expansionshippedSupports additional Azure OpenAI and AI Foundry authentication modes including Entra Federated identity and Workload Identity without client secrets.15 releases · first seen Jun 2025▸
release
15 total
Adds workload identity federation (wif) as a provider authentication type for keyless cloud workload authentication
Backend 1.25.0 · Sep 2026
· source
· release history
Allows OpenAI-compatible integrations to authenticate to upstream providers using OAuth Client Credentials grant (RFC 6749) instead of static API keys
Enterprise Gateway 2.19.0 · Aug 2026
· source
· release history
Supports per-request AWS Bedrock STS session tags via the AWS_BEDROCK_STS_SESSION_TAGS_ENABLED environment variable
Enterprise Gateway 2.19.0 · Aug 2026
· source
· release history
Adds oauthClientCredentials as a valid value for the provider_auth_type field in integration configs to enable OAuth 2.0 Client Credentials grant for upstream providers like OpenAI
Backend 1.24.1 · Aug 2026
· source
· release history
Adds support for AZURE_AUTH_MODE=workload environment variable to enable Azure Workload Identity authentication for log stores in self-hosted deployments
Backend 1.24.1 · Aug 2026
· source
· release history
Adds hardened SSRF checks for prompt playground and proxy calls by blocking IMDS, metadata endpoints, and private DNS-rebind targets for admin-supplied gateway URLs
Backend 1.23.0 · Aug 2026
· source
· release history
+Unified batch job processingshippedProvides a centralized API for submitting, managing, and tracking batch inference jobs across multiple providers with configurable storage, output fidelity, and line limits.12 releases · first seen Jan 2025▸
Also counts toward: REST API
release
12 total
Support output_expires_after parameter for batch creation, plus input_blob and output_folder for Azure OpenAI blob-based inputs
Enterprise Gateway 1.17.12 · Jan 2026
· source
· release history
v1.3.0 supports KMS keys for encrypting custom batch file output
Data Service 1.3.0 · Oct 2025
· source
· release history
Allows passing through parameters to the Bedrock batch create endpoint
Enterprise Gateway 1.15.6 · Oct 2025
· source
· release history
Handles file upload failures for AWS Bedrock during unified batch processing
Enterprise Gateway 1.10.16 · Apr 2025
· source
· release history
Preserves custom_id in VertexAI batch output
Enterprise Gateway 1.10.14 · Mar 2025
· source
· release history
Increased maximum lines for custom batches to 500k
Data Service 1.1.5 · Mar 2025
· source
· release history
+Log and analytics backend abstractionshippedIntroduces the `control_plane` log store backend, environment variable routing options, and support for arbitrary S3-compatible storage via new configuration keys.9 releases · first seen Oct 2024▸
release
9 total
Added support to read logs based on the path format identifier released in Gateway v1.17.0
Backend 1.5.1 · Nov 2025
· source
· release history
Adds a new column in ClickHouse to store the log object path format identifier
Backend 1.5.0 · Nov 2025
· source
· release history
Adds search functionality to the Analytics Filter API key field
Frontend 1.4.9 · Nov 2025
· source
· release history
Adds strict name filter parameter to list workspaces API
Backend 1.3.0 · Oct 2025
· source
· release history
Added support for passing encryption headers while uploading stream data to S3
Data Service 1.1.10 · Apr 2025
· source
· release history
Implemented end limit for log export records
Data Service 1.1.1 · Feb 2025
· source
· release history
+Usage cost attribution and trackingshippedCalculates and attributes costs for standard requests, tool usage, and fine-tuned models across providers for granular spend visibility.8 releases · first seen Mar 2025▸
release
8 total
Requests authenticated via Gateway-local JWT are attributed to existing Portkey users when their email matches a workspace user
Enterprise Gateway 2.21.0 · Sep 2026
· source
· release history
Adds credit-based cost tracking for Meshy and Tripo3D 3D-generation providers with a 24h duplicate-billing protection window
Enterprise Gateway 2.19.0 · Aug 2026
· source
· release history
Token usage from MCP requests (prompts, completions, tools) is tracked and reported in analytics and logs alongside LLM usage.
Enterprise Gateway 2.12.0 · Jun 2026
· source
· release history
Token usage from agent endpoints (messages and tasks) is tracked and reported in analytics and logs alongside LLM usage.
Enterprise Gateway 2.12.0 · Jun 2026
· source
· release history
Allows integration-level cost multipliers via pricing_adjustments.multiplier config key for per-integration markup or discount pricing
Enterprise Gateway 2.7.0 · Apr 2026
· source
· release history
Introduces cost calculation for tools like web_search, file_search and code_execution.
Enterprise Gateway 1.10.17 · Apr 2025
· source
· release history
+API key rotation automationshippedProvides automatic and manual API key rotation with configurable policies and dedicated scopes to control rotation access across organization, workspace, and user keys.8 releases · first seen Oct 2025▸
release
8 total
API key rotation enforcement user_api_key_rotation_period now accepts days only (integer 1–365), normalizing old weekly/monthly values.
Backend 1.17.0 · May 2026
· source
· release history
Adds user_api_key_rotation_period organization setting to enforce automatic API key rotation for workspace-user keys
Backend 1.15.0 · May 2026
· source
· release history
Adds API_KEY_PREFIX environment variable to prefix all newly-generated Portkey API keys in self-hosted deployments
Backend 1.15.0 · May 2026
· source
· release history
API Key Rotation is generally available; use *.rotate scope for organization-service, workspace-service, and workspace-user API key types to enable rotation
Backend 1.14.0 · Apr 2026
· source
· release history
Adds automatic and manual API key rotation with rotation_policy config (rotation_period, next_rotation_at, key_transition_period_ms) and new POST /api-keys/:apiKeyId/rotate endpoint
Backend 1.13.0 · Apr 2026
· source
· release history
Enables API key rotation on schedule or demand, including an explicit manual rotate endpoint and usage reset alongside rotation
April 2026 · Apr 2026
· source
· release history
+Observability and metrics customizationshippedAllows extensive configuration of Prometheus metric labels, histogram buckets, and the injection of request headers into metadata for enriched observability.4 releases · 1 other source · first seen Dec 2025▸
release
Adds PROMETHEUS_INCLUDE_CONFIG_NAME_LABEL and PROMETHEUS_INCLUDE_API_KEY_NAME_LABEL environment flags to attach config slug and API key name as labels on custom metrics
Enterprise Gateway 2.10.0 · May 2026
· source
· release history
Adds HEADERS_TO_METADATA environment variable to inject request headers into metadata for observability enrichment without client-side x-portkey-metadata changes.
Enterprise Gateway 2.5.0 · Apr 2026
· source
· release history
Adds PROMETHEUS_INCLUDE_MODEL_LABEL, PROMETHEUS_INCLUDE_METADATA_LABELS, PROMETHEUS_HISTOGRAM_BUCKETS, PROMETHEUS_HTTP_DURATION_BUCKETS, and PROMETHEUS_GC_BUCKETS environment variable support for configuring Prometheus metrics.
Enterprise Gateway 2.4.3 · Mar 2026
· source
· release history
Updates /spans endpoint aggregate metrics to include total tokens count
Backend 1.6.1 · Dec 2025
· source
· release history
docs
Add apiKeyName and/or configName to the PROMETHEUS_EXTRA_LABELS variable to expose these as labels on every custom metric. PROMETHEUS_EXTRA_LABELS string (comma-separated list) "" (empty) Additional labels to include.
docs update · Aug 2026
· source
+Workspace user key auto-provisioningshippedAutomatically creates default workspace-user API keys when members join or accept invites, reducing manual setup overhead.4 releases · first seen May 2026▸
release
Adds user_api_key_auto_create_scopes organisation setting to control default data-plane scopes for auto-provisioned workspace-user API keys
Backend 1.24.2 · Aug 2026
· source
· release history
Adds org-only setting default_workspace_user_api_key_auto_create to control auto-provisioning of workspace-user API keys.
Backend 1.17.0 · May 2026
· source
· release history
Allows setting defaults.user_api_key_config via PUT /v2/workspaces/:id to define a default config slug for auto-created or fallback workspace-user API keys, with validation preventing deletion of the active default
Backend 1.16.2 · May 2026
· source
· release history
Adds user_api_key_auto_create organization setting to automatically provision default workspace-user API keys on member join or invite acceptance
Backend 1.15.0 · May 2026
· source
· release history
+Structured output integrationshippedEnables structured outputs via Pydantic SDK integration for GoogleAI and VertexAI providers.4 releases · first seen Oct 2024▸
release
Adds support for base64 data URLs (format: data:<media_type>;base64,<data>) in file.file_data via /chat/completions to forward as Anthropic document content
Enterprise Gateway 2.6.0 · Apr 2026
· source
· release history
Enables passthrough of top-level cache_control parameter to Anthropic in /chat/completions and adds automatic additionalProperties: false for strict structured outputs
Enterprise Gateway 2.6.0 · Apr 2026
· source
· release history
Bedrock structured outputs now use outputConfig with json_schema text format via the Converse API for Claude models on Bedrock
Enterprise Gateway 2.4.2 · Mar 2026
· source
· release history
Adds Pydantic SDK integration for structured outputs in GoogleAI and VertexAI providers by dereferencing JSON schemas to ensure Google compatibility.
Enterprise Gateway 1.8.0 · Oct 2024
· source
· release history
+Realtime API supportshippedAdds gateway support for OpenAI and Azure OpenAI Realtime APIs, including parameter forwarding and socket event handling.4 releases · first seen Nov 2024▸
release
Add real-time voice interaction support for xAI via Realtime Voice Agent API (Grok Voice API) with WebSocket connections
Enterprise Gateway 1.17.12 · Jan 2026
· source
· release history
Retains the original close reason from the provider in the socket close event for Realtime APIs
Enterprise Gateway 1.9.1 · Nov 2024
· source
· release history
Adds prediction, store, metadata, audio and modalities parameters support for OpenAI and AzureOpenAI Realtime APIs
Enterprise Gateway 1.9.1 · Nov 2024
· source
· release history
Adds Realtime APIs integration capability for OpenAI and AzureOpenAI providers
Enterprise Gateway 1.9.0 · Nov 2024
· source
· release history
+Dynamic model configuration sourcingshippedSupports fetching and storing model configurations, pricing data, and capabilities from remote proxies or local paths to support air-gapped environments.3 releases · first seen Jan 2026▸
Also counts toward: Air-gapped deployment, REST API
release
PUT /v2/batches/:id now accepts internal_output_file_id for the guardrails-on-batches pipeline, supported by a new internal column on batches records
Backend 1.16.1 · May 2026
· source
· release history
MODEL_CONFIGS_PROXY_FETCH_ENABLED=ON environment variable enables dynamic model pricing fetch in Air-Gapped deployments via Backend service
Enterprise Gateway 2.0.0 · Jan 2026
· source
· release history
Adds MODEL_CONFIGS_PROXY_FETCH_ENABLED, MODEL_CONFIGS_PROXY_URL, MODEL_CONFIGS_PRICING_LOG_STORE_PATH, MODEL_CONFIGS_CAPABILITIES_LOG_STORE_PATH, MODEL_CONFIGS_CAPABILITIES_LOCAL_PATH, and MODEL_CONFIGS_PRICING_LOCAL_PATH environment variables for model config sourcing
Backend 1.7.0 · Jan 2026
· source
· release history
+Vertex AI cost attribution controlshippedAdds specific configuration to skip cost attribution for Vertex AI Provisioned Throughput deployments within the model catalog.3 releases · first seen Jul 2025▸
release
Adds vertex_skip_ptu_cost_attribution config key in Model Catalog settings to skip cost attribution for Vertex AI Provisioned Throughput deployments.
Enterprise Gateway 2.1.0 · Feb 2026
· source
· release history
media_resolution, vertex_skip_ptu_cost_attribution, and x-portkey-vertex-auth-type headers added for Vertex AI control.
February 2026 · Feb 2026
· source
· release history
Adds support for cost calculation for fine-tuned models on Vertex AI
Enterprise Gateway 1.11.9 · Jul 2025
· source
· release history
+Unified fine-tuning job processingshippedExposes a consistent API for submitting and tracking fine-tuning jobs across providers, including file upload, transformation, and storage management.3 releases · first seen Jan 2025▸
release
Added webm mimeType support in VertexAI batches and fine-tune APIs
Enterprise Gateway 1.10.11 · Mar 2025
· source
· release history
Unified Finetuning APIs now support VertexAI for file uploads and transformations.
Enterprise Gateway 1.10.10 · Feb 2025
· source
· release history
Adds unified finetune APIs for OpenAI, AzureOpenAI, Bedrock, and Fireworks
Enterprise Gateway 1.10.1 · Jan 2025
· source
· release history
+Meta provider supportshippedAdds Meta as a supported provider with Chat Completions, Anthropic-compatible Messages API, OpenAI-compatible Responses API, and Files API protocols.2 releases · first seen Sep 2026▸
Also counts toward: REST API
release
Adds Meta and ElevenLabs as new providers: Meta supports Chat Completions, Messages API, Responses API, and Files API, while ElevenLabs supports text-to-speech and speech-to-text with full observability and reliability features.
changelog · Oct 2026
· source
· release history
Adds Meta as a first-class provider with support for Chat Completions, Anthropic-compatible Messages API, OpenAI-compatible Responses API, and Files API protocols.
Enterprise Gateway 2.25.1 · Sep 2026
· source
· release history
+Typed-judgment model routingshippedRoutes structured prompts to typed-judgment models and returns calibrated choices, scores, or boolean judgments through the gateway's standard auth, routing, and tracking stack.1 release · 1 other source · first seen Oct 2026▸
Also counts toward: REST API
release
Adds a Decisions API endpoint for typed-judgment models: send a question with structured state and receive a typed judgment (boolean, choice, or score) with probabilities and a calibrated confidence score, routing through the full gateway stack (auth, routing, retries, caching, logging, cost tracking); initial support…
changelog · Oct 2026
· source
· release history
example
Call the Decisions API to get a calibrated boolean judgment from a TypeSafe Jev model — useful for automated triage or policy enforcement pipelines.$ curl -X POST https://api.portkey.ai/v1/decisions \ -H 'x-portkey-api-key: <your-api-key>' \ -H 'Content-Type: application/json' \ -d '{ "model": "jev", "question": "Does this request contain PII?",…
changelog · Oct 2026
· source
+Mistral AI moderation guardrail integrationshippedApplies Mistral AI's content moderation service to LLM inputs and outputs to detect harmful content across multiple policy dimensions.1 release · 1 other source · first seen Jan 2025▸
release
Adds new partner guardrails for Mistral mistral.moderateContent and Pangea pange.textGuard
Enterprise Gateway 1.10.0 · Jan 2025
· source
· release history
docs
Mistral AI provides a sophisticated content moderation service that enables users to detect harmful text content across multiple policy dimensions, helping to secure LLM applications and ensure safe AI interactions.
docs update · Oct 2026
· source
+Config target limitsshippedEnforces hard limits on config target fan-out (root, nested, and conditional) and allows overrides via environment variables to prevent excessive resource consumption.2 releases · first seen Jul 2026▸
release
Adds environment variables MAX_ROOT_CONFIG_TARGETS, MAX_NESTED_CONFIG_TARGETS, and MAX_CONDITIONAL_ROOT_CONFIG_TARGETS to override default config target fan-out limits.
Enterprise Gateway 2.14.0 · Jul 2026
· source
· release history
Config target fan-out is now capped at 100 root-level targets (1,000 for conditional strategy) and 50 nested targets per root target; configs exceeding these limits will be rejected at request time unless overridden by MAX_ROOT_CONFIG_TARGETS, MAX_NESTED_CONFIG_TARGETS, or MAX_CONDITIONAL_ROOT_CONFIG_TARGETS…
Enterprise Gateway 2.14.0 · Jul 2026
· source
· release history
+Agent integration granularity and securityshippedAdds granular RBAC scopes for agent integrations and servers, while enforcing SSRF protection on agent card discovery endpoints.2 releases · first seen May 2026▸
Also counts toward: Role-based access control
release
POST /v2/agent-integrations/fetch-agent-card now validates upstream endpoints against SSRF vectors (private IPs, cloud metadata, non-HTTP(S), fragments) and enforces valid JSON {url, name} responses under 1 MB
Backend 1.16.1 · May 2026
· source
· release history
Adds granular RBAC scopes: organisation_agent_integrations.*, workspace_agent_integrations.*, agent_servers.*, agent_server_skills.*, agent_integration_skills.*, agent_server_user_access.*, and agents.invoke
Backend 1.15.0 · May 2026
· source
· release history
+Enhanced usage limit policiesshippedExpands usage limit and rate limiting configurations to support periodic reset intervals based on days alongside existing weekly/monthly cycles.2 releases · first seen Feb 2026▸
release
Adds rotation_period_days column to rotation_policies and exposes periodic_reset_days, next_usage_reset_at, and last_reset_at fields on usage limit policies
Backend 1.15.0 · May 2026
· source
· release history
periodic_reset_days is mutually exclusive with the existing periodic_reset (weekly / monthly) option
Backend 1.10.0 · Feb 2026
· source
· release history
+Organization admin access controlsshippedIntroduces settings to control organization manager write access for workspace integrations and MCP servers, alongside log viewing permissions for admins.2 releases · first seen Apr 2026▸
release
Adds organisationAdminsViewLogs and organisationAdminsViewLogMetadata organization settings to control org admin access to request logs and metadata
Backend 1.15.0 · May 2026
· source
· release history
Added organization security settings managersWriteWsIntegrations, managersWriteWsMcpIntegrations, and managersWriteMcpServers with default enabled and workspace-level overrides to control manager write access
Backend 1.14.0 · Apr 2026
· source
· release history
+F5 Guardrails integrationshippedSupports F5 Guardrails backend dependencies and request routing to enforce content and security policies on LLM traffic.2 releases · first seen Nov 2025▸
release
Updated new Guardrails and Plugins support
Frontend 1.5.5 · Dec 2025
· source
· release history
Added backend dependencies for the new F5 Guardrails
Backend 1.5.1 · Nov 2025
· source
· release history
+Plugin provider supportshippedSupports Javelin, Qualifire, and Walled as new plugin providers to extend the cyber toolchain's routing and agent capabilities.2 releases · first seen Dec 2025▸
Also counts toward: Plugin system
release
Adds Javelin, Qualifire, and Walled as new plugin providers
Backend 1.6.1 · Dec 2025
· source
· release history
Updated new Guardrails and Plugins support
Frontend 1.5.5 · Dec 2025
· source
· release history
+JWT authentication expansionshippedAllows the gateway to verify JWTs against multiple JWKS endpoints and automatically route requests to the correct workspace user based on token attributes.1 release · first seen Oct 2026▸
release
Extends JWT authentication to accept multiple JWKS URLs and attribute requests to the matching workspace user.
changelog · Oct 2026
· source
· release history
+Reasoning model streaming supportshippedEnables streaming of the internal reasoning or thinking phase as dedicated content blocks for reasoning models via the Messages API.1 release · first seen Oct 2026▸
release
Messages API reasoning models now stream their thinking phase as a thinking content block.
changelog · Oct 2026
· source
· release history
+OCR routingshippedProvides a dedicated `/v1/ocr` endpoint to route OCR requests through the gateway's retries, fallbacks, load balancing, and pricing logic with support for Mistral AI and Azure AI Foundry.1 release · first seen Aug 2026▸
Also counts toward: REST API
release
Adds POST /v1/ocr endpoint to route OCR requests through gateway retries, fallbacks, load balancing, caching, logging, and pricing with support for Mistral AI and Azure AI Foundry
Enterprise Gateway 2.18.0 · Aug 2026
· source
· release history
+MCP server-side executionshippedEnables server-side Model Context Protocol execution via the `@portkey-mcp` prefix in tool calls, gated by a beta header.1 release · first seen Jun 2026▸
release
Adds @portkey-mcp prefix support in the tools array of Responses API and Messages API requests for server-side MCP execution, gated behind the x-portkey-beta: server-side-mcp-2026-06-01 header
Enterprise Gateway 2.13.0 · Jun 2026
· source
· release history
+Agent gateway managementshippedProvides centralized agent lifecycle management, skill configuration, workspace-level access controls, and RBAC support.1 release · first seen Apr 2026▸
Also counts toward: Role-based access control, REST API
release
Adds Agent Gateway with full CRUD APIs, agent skills management, workspace-level access control, and RBAC support
Backend 1.13.0 · Apr 2026
· source
· release history
+Batch pricing configurationshippedAllows organization-level configuration of dedicated batch inference pricing defaults, such as applying a percentage discount when specific pricing is not available.1 release · first seen Feb 2026▸
release
Adds dedicated batch pricing configurations via the Data Service, defaulting to 50% of standard pricing when specific pricing is unavailable.
Enterprise Gateway 2.1.0 · Feb 2026
· source
· release history
+Dedicated RBAC for Gateway DeploymentsshippedIntroduces fine-grained permissions specifically controlling the creation, reading, updating, deletion, and listing of gateway deployment resources.1 release · first seen Feb 2026▸
Also counts toward: Role-based access control
release
Adds dedicated RBAC permissions (deployments:create, deployments:read, deployments:update, deployments:delete, deployments:list) for Gateway Deployments
Backend 1.8.0 · Feb 2026
· source
· release history
+Prompt Playground enhancementsshippedAdds a copy option for individual messages in the prompt playground interface to streamline prompt iteration.1 release · first seen Dec 2025▸
release
Added copy option on Prompt Playground on Each messages
Frontend 1.5.5 · Dec 2025
· source
· release history
+Vertex AI grounding supportshippedAdds Gemini grounding mode support for OpenAI compatible tools format requests.1 release · first seen Dec 2024▸
release
Adds Gemini grounding mode support for OpenAI compatible tools format
Enterprise Gateway 1.9.5 · Dec 2024
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
7 commands for Portkey, each
with where it came from. This tool has no source analysis yet, so there
is no option reference and no captured run beside them.
View
Source
No command matches.
Screenshots
From the release notes, newest first. Click one to see it full size.
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Five scores for Portkey, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Portkey puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Portkey's home page and 37 more pages as they looked each month from April 2023 to October 2026: 47 renders, 7 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.