Skip to main content
Mintive is the new name for MintMCP.Read the announcement

LLM gateway comparison

Last updated: October 23, 2026.

LLM gateways sit between your applications or agents and the model providers, so you can route calls, cap spend, restrict models and log every request in one place. They come from four directions. Open-source proxies (LiteLLM, Helicone) run in your own infrastructure. Managed routers (OpenRouter, Requesty, Vercel AI Gateway, Cloudflare AI Gateway) give one account across many providers. API gateways add AI plugins to existing API management (Kong, Azure API Management), and AI platforms pair the gateway with deployment and guardrails (Portkey, TrueFoundry). Mintive's LLM gateway (early access) governs agents' model traffic with the same users, groups and audit trail as its MCP gateway, so tool calls and model calls follow one set of policies.

How we compared these LLM gateways​

The facts come from each vendor's public documentation, pricing pages and repositories, checked on October 23, 2026. A cell says "not documented" when we couldn't find the fact on the vendor's own pages, which doesn't mean the capability is missing. There is no ranking column: each row ends with when it fits best.

LLM gateway pricing, deployment and supported providers​

GatewayTypeDeployment and licensePricing modelProviders and modelsBest fit when
MintiveLLM gateway beside the MCP gateway and Agent Monitor (early access)Managed cloud service in the US or EU; Private Networks reach internal MCP services (Enterprise); on-premise or self-hosted by arrangement. License: paid plansEarly access; contact MintiveOpenAI, Anthropic, Fireworks and Amazon Bedrock (providers)You want agents' model spend and access governed with the same identities as their MCP tools
LiteLLMOpen-source LLM gateway (proxy)Self-hosted. License: MIT except the enterprise/ directoryOpen source $0; Enterprise annual100+ LLMsYou want an open-source proxy you run and extend yourself
PortkeyLLM gateway and control planeSaaS, self-hosted, private cloud or VPC. License: Gateway repository MIT; platform paidFree; Production $49/month; Enterprise custom1,600+ LLMsYou want a managed gateway with built-in guardrails and workspaces
OpenRouterManaged model routerManaged; EU endpoint. License: commercial5.5% fee on credits (8% on Business); bring-your-own-key options500+ models from 80+ providersYou want one account across many providers and models
Kong AI GatewayAPI gateway with AI pluginsKonnect hybrid or serverless; self-hosted. License: Kong Gateway Apache 2.0; AI plugins on EnterprisePlus from $25/month plus usageMajor providers through one APIYou already run Kong for APIs
Cloudflare AI GatewayManaged AI gatewayManaged, on all Cloudflare plans. License: commercialCore features free; 5% fee on unified billing creditsWorkers AI, OpenAI, Anthropic, Gemini and moreYou run on Cloudflare and want a free managed gateway
TrueFoundryAI gateway on an AI deployment platformSaaS, hybrid, self-hosted VPC or on-premise. License: commercialFree (3 users); Pro $25 per user/month; Enterprise custom1,000+ LLMsYou want a self-hostable gateway beside model and agent deployment
HeliconeOpen-source observability with an AI gatewayCloud or self-hosted. License: Apache 2.0Free; Pro $79/month; Team $799/month100+ providersYou mainly want open-source request logging and cost tracking
Vercel AI GatewayManaged AI gatewayManaged, callable from anywhere. License: commercialNo token markup; paid add-ons400+ models from 70+ providersYou want no-markup model access with one-command coding-agent setup
Azure API ManagementAI gateway features in API ManagementManaged Azure; self-hosted gateway. License: commercialAPI Management tier pricingOpenAI-compatible, Anthropic, Vertex; Foundry and Bedrock modelsYour models run in Azure and you already use API Management
RequestyManaged model routerManaged; EU data residency. License: commercialFree; 5% markup pay as you go600+ modelsYou want managed routing with organization model allowlists

Portkey's site states that it is now part of Palo Alto Networks as "Prisma AIRS AI Gateway", and Helicone's site states that it is no longer part of Mintlify.

LLM gateway budgets, access control and Claude Code support​

GatewaySubscription seatsBudgets and rate limitsAllowed models per groupIdentity (SSO, SCIM, groups)Coding-agent setup documented
MintiveAnthropic: routes through each caller's linked Claude subscriptionA monthly budget per policy, with optional per-user caps and per-user overrides; calls get a 429 once a budget is spentYes: models per policy, policy granted to groupsSSO and SCIM; Can Use grants by group or user (access)Claude Code, Codex and Claude Desktop through the mintive CLI; Coworker Agents
LiteLLMClaude Pro, Max, Team and EnterprisePer key, user, team and organizationPer key; model access groupsSSO and SCIM on EnterpriseClaude Code, Codex, Cursor
PortkeyClaude Max and Anthropic OAuthPer workspace, team and keyYes, per workspaceSSO and SCIMClaude Code, Codex, Cursor and more
OpenRouterNot documentedPer member, key and workspaceYes, per member, key and workspaceSAML SSO and SCIM on EnterpriseClaude Code, Codex, Cursor
Kong AI GatewayNo: its Claude Code guide sends seats directly to AnthropicToken and cost limits per consumer groupYes, per consumer groupSSO, SCIM and RBAC on EnterpriseClaude Code; Codex CLI mentioned
Cloudflare AI GatewayNot documentedSpend limits by model, provider or userNot documentedCloudflare Access with your IdPClaude Code, Codex, Cursor
TrueFoundryClaude plans; ChatGPT plans for CodexPer user, team, virtual account and modelYes, per team or userOIDC or SAML SSO and SCIMClaude Code, Codex, Cursor
HeliconeNot documentedRate limits per user or property, cost-basedNot documentedSAML SSO on EnterpriseClaude Code, Codex
Vercel AI GatewayClaude subscription with Claude CodePer team, project, key and memberTeam-wide allowlistSAML SSO; directory sync on EnterpriseClaude Code, Codex, Cursor and 25+ more
Azure API ManagementNot documentedToken limits per subscription or custom keyNot documentedEntra ID or another IdP over OAuthNot documented
RequestyNot documentedPer key, user and groupYes: organization list plus group access listsSAML or OIDC SSO; SCIM on requestClaude Code, Codex

LLM gateway logging, guardrails and compliance​

GatewayLogging and audit exportGuardrails on LLM trafficCompliance stated by the vendor
MintiveEvery call logged in Agent Monitor; budget changes in the audit log; SIEM export over OTLP or Splunk HEC, or as batched files to S3No content screening in the LLM gateway itself; Agent Monitor rules screen coding-agent prompts for secrets and prompt injection through agent hooks; Mint Guard (enabled on request) screens MCP tool callsSOC 2 Type II and HIPAA, with a BAA available; ZDR covers the LLM gateway
LiteLLMOpenTelemetry, Datadog, S3; audit logs on EnterprisePresidio PII masking; Lakera, Bedrock Guardrails and othersSOC 2 Type II
PortkeyOpenTelemetry export; audit logPII detection; partner prompt-injection checksSOC 2, ISO 27001, GDPR, HIPAA
OpenRouterBroadcast to OpenTelemetry, Datadog, S3 and morePII redaction; prompt-injection detectionSOC 2 Type II
Kong AI GatewayAudit logs, metrics, OpenTelemetryPII sanitizer; prompt guardNot documented on the pages checked
Cloudflare AI GatewayLogs, Logpush, OpenTelemetry tracesSafety guardrails; DLPNot documented on the AI Gateway pages
TrueFoundryOpenTelemetry; audit logsPII redaction; prompt-injection detectionSOC 2, HIPAA, GDPR
HeliconeRequest logsPrompt Guard (OpenAI models)SOC 2 Type II, HIPAA
Vercel AI GatewayRequest logs; OpenTelemetry trace drainsNone at the gateway level, per VercelSOC 2 Type 2, ISO 27001, HIPAA BAA
Azure API ManagementAzure Monitor and Application InsightsAzure AI Content Safety with prompt shieldsNot documented on the AI gateway pages
RequestyUsage analyticsPII and secrets scanning on EnterpriseNot documented

How to choose an LLM gateway​

LLM gateway for AI agents and coding agents​

Coding agents and autonomous agents make model calls and tool calls in the same session, so governing only one half leaves gaps. Look for budgets and allowed models tied to your directory groups, setup for the harnesses your people run (Claude Code, Codex, Cursor), and logs that land in the same place as tool-call logs. Mintive's LLM gateway uses the same users and groups as its MCP gateway and logs every call to Agent Monitor, and the mintive CLI configures local harnesses (user setup).

Open source and self-hosted LLM gateways​

LiteLLM (MIT, with an enterprise directory) and Helicone (Apache 2.0) run in your own infrastructure, and Portkey's gateway repository and Kong Gateway are open source too. You operate upgrades, scaling and identity integration yourself, and SSO, SCIM and audit logs are often on paid tiers.

LLM routers for many models and providers​

Managed routers such as OpenRouter, Requesty, Vercel AI Gateway and Cloudflare AI Gateway give one API and one bill across hundreds of models. Compare their fees (a percentage on credits, or no markup), their model allowlists, and whether budgets can be set per team or member.

AI gateway features in an existing API gateway​

Kong AI Gateway and Azure API Management add token limits, content safety and model routing to the API management you already operate. Check how each handles subscription seats and coding agents, since Kong's Claude Code guide sends subscription traffic directly to Anthropic.

LLM gateway FAQ​

What is the difference between an LLM gateway and an AI gateway?​

The terms overlap. Kong, Cloudflare, Vercel and Azure call their products AI gateways, and they route LLM traffic alongside other AI traffic, with Kong and Azure also covering MCP. An LLM gateway focuses on model calls: provider routing, budgets, allowed models and request logs. See the MCP gateway comparison for tool traffic.

Is there an open source LLM gateway?​

Yes. LiteLLM is MIT licensed except its enterprise directory, Helicone is Apache 2.0, Portkey's gateway repository is MIT, and Kong Gateway is Apache 2.0 with its AI plugins on the Enterprise tier. You host and operate these yourself, and SSO, SCIM and audit logs are often paid features.

Which LLM gateways work with Claude Code?​

Mintive, LiteLLM, Portkey, OpenRouter, Kong, Cloudflare, TrueFoundry, Helicone, Vercel and Requesty all document Claude Code setup. Mintive's CLI configures local harnesses such as Claude Code and Codex, and Vercel's CLI configures Claude Code, Codex, Cursor and other agents in one command.

Can an LLM gateway use Claude or ChatGPT subscription seats instead of API keys?​

Some can. Mintive (Anthropic), LiteLLM, Portkey, TrueFoundry and Vercel document routing Claude subscription traffic, and TrueFoundry also documents ChatGPT plans for Codex. Kong's Claude Code guide sends subscription seats directly to Anthropic instead. See provider and model selection.

How do LLM gateways limit spend by team?​

Most attach budgets to a unit you manage: a policy, with optional per-user caps (Mintive), a key, team or organization (LiteLLM), a workspace (Portkey, OpenRouter), a consumer group (Kong), or a team, project or key (Vercel). Azure API Management limits tokens per subscription or custom key rather than dollars. See budgets.

Do LLM gateways screen prompts for PII and prompt injection?​

Many do, with different coverage. LiteLLM, Portkey, OpenRouter, TrueFoundry, Kong and Azure document PII or prompt-attack checks on LLM traffic, and Vercel states its gateway ships no guardrails. Mintive screens prompts from coding agents with Agent Monitor rules and screens MCP tool calls with Mint Guard.

Sources​

Every competitor fact on this page comes from that vendor's own public documentation, pricing pages or repository, checked on October 23, 2026.