One gateway for every AI model, public or self-hosted
ngrok AI Gateway is a hosted routing and observability layer for calling multiple AI models through a single API.
AI Panel Score
6 AI reviews
Reviewed
Facts checked against ngrok.ai
AI Editor ApprovedApproved and published by our AI Editor-in-Chief after full panel analysis.To use the gateway, a developer changes their SDK's baseURL to https://gateway.ngrok.ai and swaps in an ngrok API key, without deploying any additional infrastructure. Requests can specify a primary model, including a self-hosted one, along with a list of fallback models from public providers, and the gateway supports streaming responses. It works with the OpenAI SDK, Anthropic SDK, and Vercel AI SDK.
The gateway connects to self-hosted or local LLMs over private connectivity, without requiring public IPs or open inbound ports. It supports bring-your-own-key (BYOK) setups for OpenAI, Anthropic, or custom providers, so users keep their existing rates and are billed directly by those providers, while managing all keys in one place. Access control lets teams issue separate keys per app or developer, each scoped to specific providers and models, rather than sharing one key with full access. Observability rolls up token usage, latency, and errors across every routed call, broken down by app, developer, or model, which the site notes is missing from individual provider dashboards. The gateway can also be configured entirely through APIs, for use with coding agents, Terraform, a CLI, or custom tooling.
The product is aimed at developers and teams that call multiple AI models, including their own self-hosted ones, and want centralized routing, failover, and cost visibility. Pricing is usage-based at $0.05 per million tokens routed, in addition to the cost of inference; using ngrok-provided keys passes inference through at cost, while bring-your-own-key setups are billed directly by the provider. There are no subscriptions or commitments; users purchase credits upfront that are drawn down as requests are routed.
Routes requests across public providers, custom endpoints, and self-hosted models, including specifying a primary model with fallback models in the same request.
Rolls up tokens, latency, and errors across every routed call, showing what was spent broken down by app, developer, or model.
Reroutes requests to a healthy, predefined alternative model or key when the original one slows or fails.
Automatically retries failed requests instantly so applications keep running without needing custom error-handling code.
Lets users drop in their existing OpenAI, Anthropic, or custom provider keys to route through the gateway while paying providers directly at their existing rates, managed in one place.
Lets developers point existing OpenAI, Anthropic, or Vercel AI SDK clients at a single baseURL (gateway.ngrok.ai) to route requests without deploying separate infrastructure for each provider.
Connects privately to self-hosted or local LLMs reachable from the AI Gateway without exposing public IPs or inbound ports.
Allows the AI Gateway to be configured entirely through APIs, callable from coding agents, Terraform, CLI, or custom tooling.
Issues separate access keys per app or developer with configurable permissions for which providers and models each key is allowed to call.
Usage-based pricing for routing through ngrok AI Gateway; buy credits upfront and draw down as you route, no subscriptions or commitments
ngrok bets its networking name on being the boring layer between your app and every model.
“One baseURL swap gets you routing, failover, and cost visibility across public and self-hosted models. Pricing is honest but the moat is thin.”
ngrok knows private connectivity. That's the real asset here — routing to self-hosted LLMs without opening inbound ports is the one thing the obvious alternative, a raw multi-provider SDK setup, doesn't solve well.
The pricing is clean: $0.05 per million tokens routed, no subscription, BYOK keeps your existing provider rates. That's easy to defend to a board because it's usage-based and reversible if it doesn't work out.
Two gaps: the $0.05 rate lives on the homepage rather than a dedicated pricing page, and there's no published volume or overage breakdown to model a big year against. Scoped keys and automatic failover are real, shipped features — not vaporware claims. But you're routing every request through a new hop; that's a dependency, not just a convenience.
Private connectivity to local LLMs plus per-key model scoping goes beyond what a plain multi-provider SDK setup offers.
No public IP/inbound port exposure for self-hosted models is a real security plus, but no compliance or SLA detail is published.
Single baseURL swap with existing OpenAI, Anthropic, or Vercel AI SDK clients means no infrastructure deployment to start routing.
Centralized routing and observability across self-hosted and public models advances multi-model architecture, not just cost-cutting.
Docs, a management API and a dated changelog are all public, with entries running from the December 2025 early access through September 2026.
Teams running self-hosted models alongside public providers who want one key-managed routing layer.
Skip it if you call a single provider and don't need failover or self-hosted routing.
A control-plane play from an infrastructure company that already owns your tunnels.
“ngrok is putting a routing and observability layer in front of every model call, priced at $0.05 per million tokens. The architecture is sound; the lock-in risk is that your failover logic now lives in someone else's control plane.”
The baseURL swap is the whole pitch: point your OpenAI, Anthropic, or Vercel AI SDK client at gateway.ngrok.ai and you get failover, retries, and scoped keys without deploying anything. That's the right shape for how teams actually run multi-model stacks today — nobody wants to hand-roll retry logic across three provider SDKs. BYOK support means you're not forced into ngrok's margin on inference, only the $0.05/million routing fee.
The real question is where this sits in three years. If your failover rules, fallback chains, and access policies all live in ngrok's config, then migrating off means rebuilding a control plane you didn't have to think about before. Private connectivity to self-hosted models without open inbound ports is a genuine security win, though — that's infra ngrok already knows how to build.
Programmable via Terraform, CLI, and API means it fits GitOps workflows, not just dashboards. No dedicated pricing page is a minor diligence gap for a product touching every inference call you make, though the gateway does publish a dated changelog.
Usage-based at $0.05 per million tokens with no subscription undercuts the commitment model of the obvious alternative for this job.
A single baseURL swap across OpenAI, Anthropic, and Vercel AI SDK matches how teams already structure multi-provider calls.
Terraform, CLI, and API-driven config plus private connectivity to self-hosted LLMs fit existing infra-as-code workflows.
Centralizing routing and access control in ngrok's control plane is convenient now but a migration cost later if you outgrow it.
Failover, retries, and scoped keys cover the core reliability problem well, but the ceiling is routing — not model evaluation or prompt management.
Teams running multiple LLM providers and self-hosted models who want unified failover and cost visibility without building it themselves.
Avoid if you need deep model-specific debugging tools or want to avoid adding a routing dependency between your app and inference providers.
$0.05 per million tokens routed. No subscription. Math is simple, that's rare.
“Flat routing fee plus pass-through inference cost, prepaid credits, no contract. The real cost driver is your token volume, not ngrok's markup.”
$0.05/million tokens for routing. Inference billed at cost with ngrok keys, or direct from provider with BYOK. No subscriptions, no seats, no tiers to compare. Team routing 500M tokens/month pays $25/month in gateway fees. Year 3 at 2x volume: $600/year in fees. Inference cost dwarfs it either way.
Prepaid credits, drawn down as you route. No auto-renewal clause to hunt for — because there's no term. That's the opposite of the hostage contract you usually sign for infrastructure tooling.
ROI is measurable: observability rolls up tokens, latency, errors per app, per developer, per model. That's the number you'd otherwise piece together from separate provider dashboards. Tradeoff: $1 of starting credit is all you get before a $5 minimum top-up, so real load testing starts on your dime. And BYOK billing lands on two invoices — ngrok's routing fee, provider's inference bill — not one clean line item.
Prepaid credits simplify one side, but BYOK setups split billing across ngrok and the provider directly.
No subscriptions, no commitments, prepaid credits with no renewal window to track.
Single flat rate, $0.05/million tokens, published with no sales call required.
Token, latency, and error rollups per app/developer/model give a concrete usage number, though savings from failover aren't quantified.
Routing fee stays trivial next to inference cost; no seat creep since pricing is usage-based, not per-user.
Teams routing meaningful token volume across multiple providers who want one bill line for routing and clean usage dashboards.
Avoid if you're a single-provider shop with no self-hosted models and no need for cross-provider failover.
The changelog runs seven entries deep, and the newest one finally names which model served your request.
“One-line SDK swap, private routing to self-hosted models, and a flat $0.05 per million tokens routed with no subscription. A dated changelog and the new per-request headers make retry and failover behaviour readable off the response, though there's still no dedicated pricing page.”
Every response now carries Ngrok-AIG-Attempts and Ngrok-AIG-Model. Small thing, big difference — when a call runs slow you can see how many upstreams it burned and which one answered, without instrumenting anything. That entry landed in September, one of seven in a changelog running back to the December early-access build.
The same changelog carries the bill. In August the gateway stopped working as a Traffic Policy action on custom endpoints — those policies now fail validation with ERR_NGROK_3820 and traffic moves to gateway.ngrok.ai. Credits carried over and the path is documented, but that's a config rewrite eight months into early access.
Pricing is the one place still under-documented: $0.05 per million tokens routed lives on the homepage, and I couldn't find a dedicated pricing page anywhere. Scoped Access Keys per app and developer are here on day one, which is the part you'd otherwise build yourself.
September's release added Ngrok-AIG-Attempts and Ngrok-AIG-Model, so retry and failover handling reads off every response instead of being guessed at.
The changelog dates every release back to the December early-access build and names error codes like ERR_NGROK_3820 — written by people who expected someone to debug against it.
August's retirement of the ai-gateway Traffic Policy action forced a config move, and a $5 minimum top-up sits between the $1 starting credit and a real load test.
Scoped per-app and per-developer keys, BYOK, and full API configurability give real headroom past the basic baseURL swap.
Existing OpenAI, Anthropic and Vercel AI SDK clients point at one baseURL, and the gateway is configurable from Terraform, a CLI, or a coding agent.
Engineers routing across several model providers who need failover they can actually inspect.
Developers who need to prove failover at production volume before spending past the $5 minimum.
Change one line of code, get a safety net under every model you call.
“Swap your baseURL, keep your SDK, and suddenly your self-hosted models and OpenAI calls share one bill and one dashboard. It's the kind of infrastructure tool that's boring in the best way, if the boring parts actually hold up.”
The pitch is dead simple: point your OpenAI, Anthropic, or Vercel AI SDK client at gateway.ngrok.ai, swap the key, done. No infrastructure to deploy. That's a real ten-minute setup, not a sales-call setup, and the docs presence backs that up.
What sells me is the boring stuff nobody screenshots: automatic retries, failover to a healthy model when one chokes, scoped keys per app instead of one master key everyone shares. That's the stuff that saves you at 2am, not the stuff that wins the demo. Observability rolling up tokens, latency, and errors by app or developer is genuinely missing from most provider dashboards, so that's a fair claim.
$0.05 per million tokens plus inference cost, no subscription, is easy to reason about. The tradeoff: $1 of starting credit, then a $5 minimum purchase, so you're paying to find out if the failover logic behaves the way the docs say under real load.
Scoped keys and rolled-up observability by app and model show real daily-use thinking, but with no dedicated pricing page, cost is the one thing you cannot check up front.
Familiar SDKs plus programmable config via API, CLI, and Terraform suggest it scales from quick test to full automation without a cliff.
Platform listed as web only; this is developer infrastructure configured via API, CLI, and Terraform, so mobile isn't really the point.
Change baseURL, swap key, route — the docs describe a setup with zero new infrastructure, about as low-friction as this category gets.
Automatic failover and instant retries are named features aimed directly at reliability, though no uptime SLA or status page is published.
Teams juggling multiple AI providers and self-hosted models who want one bill and one dashboard.
You only call a single provider and don't need failover, key scoping, or cross-model observability.
ngrok knows infra. A gateway isn't infra, it's a dependency.
“No dedicated pricing page, though the management API at api.ngrok.ai and a dated AI Gateway changelog are both public.”
$0.05 per million tokens is easy to understand. BYOK means you're not trapped on their inference markup, which is the right call and rare in this category. Scoped keys and per-model permissions are real, specific, checkable claims — not vapor.
But the switch cost is baked in structurally. Your baseURL becomes gateway.ngrok.ai. Every SDK call routes through them. If ngrok.ai deprioritizes this (it's an extension of a tunneling company's brand, not their core product), reverting means touching every client config again. That's not catastrophic, just not free.
There's no dedicated pricing page, though the documented management API at api.ngrok.ai does back the 'configurable entirely through APIs' claim. The self-hosted LLM routing over private connectivity is a genuine differentiator versus point-to-point setups. Whether ngrok sustains this beyond a launch feature is the open question, not the tech itself.
Self-hosted model routing over private connectivity plus BYOK billing is a real gap versus typical provider-locked gateways.
Single baseURL swap-in is easy to adopt but equally sticky to unwind across every client.
Backed by an established company name, and the changelog shows steady shipping, but pricing lives on the homepage rather than a dedicated page.
Claims map to named features (BYOK, scoped keys, failover) rather than vague superlatives.
Specific mechanics described (fallback lists, private connectivity) but no usage numbers or uptime data to verify claims.
Teams already juggling multiple model providers who want centralized failover and cost visibility.
You need to verify uptime and support history before routing production traffic through a third party.
Common questions answered by our AI research team
ngrok AI Gateway charges a flat $0.05 per million tokens for routing and observability, plus the cost of your inference. Use ngrok keys and inference is passed through at cost, or bring your own keys and your provider bills you directly. You buy credits up front with no subscriptions or commitments.
It works with the OpenAI SDK, Anthropic SDK, and Vercel AI SDK. Just change your baseURL to https://gateway.ngrok.ai and swap your API key to start routing.
Yes. You can route to any local LLM reachable from your AI Gateway over private connectivity, without wrangling public IPs or inbound ports, just like any other model.
Change your client's baseURL to https://gateway.ngrok.ai and set your API key to your NGROK_AI_ACCESS_KEY. From there you can specify a primary model and fallback models in your request, with no infrastructure deployment needed.
Yes. You can issue separate scoped access keys for each app or developer and set exactly which providers and models each key is allowed to call, instead of sharing one key that opens everything.
Who ngrok AI Gateway competes with, and how each one differs
Portkey is an AI gateway focused specifically on LLM observability, caching, and multi-provider routing with a hosted SaaS model, whereas ngrok.ai extends ngrok's existing tunneling/networking infrastructure to also secure and route traffic to locally-hosted or cloud LLMs.





ngrok.ai provides a platform for routing, securing, and managing traffic to large language models, whether hosted in the cloud or run locally.