nRouter.ai
Get a Key
← All posts
Comparison

Vercel AI Gateway alternative: a managed LLM gateway that isn't tied to one host

Head-to-head: nRouter vs Vercel AI Gateway on the axes that decide it — BYOK spend that budgets cannot cap, governance gated to Pro and Enterprise, OIDC auth that assumes a Vercel deployment, and what a zero-markup gateway costs you elsewhere. One base-URL switch.

nRouter team · 12 min read
#comparison#llm-gateway#pricing
Vercel AI Gateway alternative: a managed LLM gateway that isn't tied to one host

If you are here because of the coupling: Vercel AI Gateway charges no markup on tokens, which makes it very hard to beat on price and very easy to adopt from a Next.js route. The question worth asking before you standardise on it is not "what does it cost" — it is "what can I enforce through it, from code that does not run on Vercel." That question has three specific answers in Vercel's own docs, and they are what this post is about.

Let us start where most comparison posts will not. On fee alone, Vercel wins. Their docs say it plainly: tokens cost the same as they would from the provider directly, with zero markup, including with BYOK (vercel.com/docs/ai-gateway, checked 2026-08-23). nRouter's pay-as-you-go fee is a flat 4% of your credits. If your only decision criterion is the percentage on top of provider spend and you are content to manage governance yourself, close this tab and use Vercel.

The reason this post exists is that most teams shopping for a gateway are not buying a discount. They are buying a place to put a rule — a spending cap, a model restriction, a guardrail — that holds no matter which service made the call. That is the axis where the two products diverge, and Vercel documents the divergence themselves.

Why teams search for a Vercel AI Gateway alternative

1. A budget cannot cap BYOK spend. This is the sharpest one, and it is not an inference from architecture — it is in Vercel's BYOK documentation: spend through your own credentials "isn't counted in budgets… It's metered separately and doesn't count toward a team, project, or API key limit, so a budget can't be used to cap BYOK spend" (BYOK docs, checked 2026-08-23). BYOK is also the recommended path for using provider-granted credits and for reaching private cloud data, so the traffic most likely to be BYOK is often the traffic with the largest or least predictable bill. A budget that covers some of your spend is a report, not a control.

2. BYOK is paid-tier, requires purchased credits, and falls back silently. The same page: BYOK is available on the paid tier, and to use it your team needs purchased AI Gateway credits, because when a request with your credentials fails, the gateway keeps it running by falling back to system credentials — and that fallback usage is billed against your credit balance. It is a sensible availability choice. It also means the answer to "whose key paid for this call?" is sometimes yours and sometimes theirs, decided at runtime by a failure you did not see. Zero Data Retention interacts with the same seam: with ZDR enabled, the gateway skips your BYOK keys by default unless you have marked an individual key as ZDR-compliant under your own provider agreement.

3. Some governance is plan-gated, and auth assumes a Vercel deployment. Model Allowlist — restricting which models your team can reach — is documented as available on Pro and Enterprise (model allowlist, checked 2026-08-23). And the gateway's two authentication methods are an API key or a Vercel OIDC token (authentication, checked 2026-08-23). OIDC is the better of the two — a short-lived, deployment-scoped identity beats a long-lived secret in an env var — and it is issued to a Vercel deployment. Code running on Lambda, Cloud Run, a Fly machine or a customer's own infrastructure is back to the static key, which means the good authentication story is the one that only works where you already deploy.

None of this makes Vercel AI Gateway a bad product. It makes it a gateway whose strongest guarantees are strongest inside Vercel.

Side-by-side, on the axes that decide it

Rows chosen for where the products actually differ. Every Vercel and Cloudflare cell traces to that vendor's own documentation, checked on the date in ## Sources.

AxisVercel AI GatewayCloudflare AI GatewaynRouter
Markup on tokensNone, including with BYOKProvider rates pass through; 5% fee on credit purchaseProvider rates pass through; a flat 4% of your credits on pay as you go, 0% on Pro
Provider credentialsBYOK (paid tier) or Vercel system credentialsBYOK, stored BYOK, or Unified Billing creditsNo BYOK — one credential model, one ledger
Do budgets cover every dollar?No — BYOK spend is metered separately and cannot be capped by a budgetRate limits by gateway; spend caps not published as budgetsYes — org, team and per-key ceilings apply to all spend
Budget enforcement signalBudgets and spend dashboardsAnalytics and rate limits402 budget_exceeded on org/team/user, 429 key_budget_exceeded per key
AuthenticationAPI key or Vercel OIDC token (deployment-scoped)Provider keys in the request, or account credentialsOne sk-nrouter-… virtual key per team, revocable
Model restrictionModel Allowlist on Pro and EnterpriseGateway configurationPer-key model access, every plan
Guardrails, evals, A/B tests, prompt managementVerify on Vercel's docsGuardrails ✅; verify the rest on Cloudflare's docs✅ included on every plan
Data controlsZDR, disallow prompt training, regional inferenceLog retention controlsSOC 2 Type II in progress
Provider breadthHundreds of models across many providersOpenAI, Anthropic, Google AI Studio, Vertex, xAI, Groq on managed credentialsAnthropic, OpenAI, Azure AI Foundry, AWS Bedrock — see /models

Vercel and Vercel AI Gateway are trademarks of Vercel Inc.; Cloudflare and Cloudflare AI Gateway are trademarks of Cloudflare, Inc. nRouter is not affiliated with or endorsed by either. All claims above are sourced from their public pricing or documentation on the dates linked in ## Sources; if any have changed, email hello@nrouter.ai and we will update.

The budget hole, worked

Take a team with three workloads: a customer-facing chat feature on Vercel system credentials, a batch enrichment job running on their own OpenAI enterprise agreement because that is where their committed spend lives, and an internal analytics agent on a Bedrock account with a SigV4 credential.

On Vercel, workloads two and three are BYOK. A team budget will happily cap workload one and will not see the other two at all — Vercel documents that BYOK spend does not count toward a team, project, or API key limit. The month the enrichment job regresses into a retry loop, the budget you configured is untouched and the bill that moves is your OpenAI invoice, on a different cadence, reconciled by a different person. The control existed. It was pointed at a third of the spend.

nRouter's answer is structural rather than clever: there is no BYOK, so there is no second meter. Every call is authenticated with an sk-nrouter-… key, every dollar lands in one ledger, and a ceiling is therefore able to be enforced before the provider call rather than reported after it. When an organisation, team or user ceiling is exhausted the request is refused with 402 budget_exceeded; when a per-key ceiling is exhausted it is refused with 429 key_budget_exceeded. Two different codes because they are two different problems — the first is a finance decision, the second is one key behaving badly and the other keys on the team still working. Both are used as HTTP defines them rather than as house codes: 402 Payment Required is reserved for the payment case, and 429 Too Many Requests describes a condition that clears with time, which is precisely the difference between the two ceilings.

That trade has a real cost and you should price it honestly: with no BYOK you cannot spend provider-granted credits through nRouter, you cannot point us at your own private deployment, and you cannot use a negotiated enterprise rate you already hold. If any of those is load-bearing, Vercel's BYOK is a feature you need and we do not have. The full argument for the trade — including what we gave up to make it — is in why nRouter does not do BYOK.

One consumer-side detail worth carrying across: nRouter reports an unknown cost as unpriced and omits the x-nr-request-cost header entirely rather than sending a zero, paired with x-nr-cost-status. A dashboard that treats a missing cost as 0 will under-report rather than show a gap, which is exactly the failure mode a budget is supposed to prevent.

What Vercel AI Gateway does better

Zero markup, and it is not a loss-leader footnote. Tokens at the rates the providers themselves publish — Anthropic posts its per-million-token prices openly, so "provider rate" is a number either side can be held to rather than a claim. Tokens at provider rates, with BYOK included. Compared against nRouter's 4% pay-as-you-go fee that is a straightforward win, and it does not stop being one because we would rather talk about budgets.

The AI SDK. generateText, streaming, tool calling and structured outputs across providers, with the gateway as a first-class provider, is the most pleasant TypeScript surface in this category. nRouter is an OpenAI-compatible endpoint; you can point @ai-sdk/openai-compatible at it, but the ergonomics of the native integration are Vercel's and we are not going to pretend otherwise.

Data controls that are actually documented. Zero Data Retention enforceable per request or team-wide, a documented way to disallow prompt training, and regional inference with an inferenceRegion that also applies to BYOK requests. nRouter's compliance position is that SOC 2 Type II is in progress — in progress, not certified — and a team with a data-residency requirement today should weigh a shipped, documented control over a roadmap.

Provider breadth. Vercel's catalog is wider than ours, including families nRouter does not serve at all. No Google model is in nRouter's live catalog. If Gemini is on your shortlist this comparison is over.

OIDC. A deployment-scoped, short-lived identity is better than a static secret. It is limited to Vercel deployments, which is the point of this post, but where it applies it is the stronger design.

Pricing: the one number that matters here

Against Vercel, the number that matters is not a fee differential in our favour — it is $50/mo, the price of the Pro plan that takes nRouter's platform fee to 0% and therefore to parity with Vercel's zero markup, while keeping guardrails, evals, A/B tests, prompt management and enforceable budgets on every plan including the cheapest. The pay-as-you-go fee is a flat 4% of your credits, so below $1,250/mo of provider spend it is smaller than the subscription; above it, Pro is the cheaper of the two and the fee is zero (about $1,042/mo is the line if you pay $500/yr instead). The plan table and the worked breakeven live on /pricing.

Signup is not free and there is no trial: a card is required, the minimum credit purchase is $5, and the platform fee is charged on top.

Switch cost: one base URL, one API key

If you already call the gateway through an OpenAI-compatible client, the change is two lines:

  // your existing code, OpenAI SDK or any OpenAI-compatible client
  const client = new OpenAI({
-   baseURL: 'https://ai-gateway.vercel.sh/v1',
-   apiKey: process.env.AI_GATEWAY_API_KEY,
+   baseURL: 'https://api.nrouter.ai/v1',
+   apiKey: process.env.NROUTER_API_KEY,
  });

If you are on the AI SDK, @ai-sdk/openai-compatible points at any OpenAI-compatible base URL, so the change is the same two values inside createOpenAICompatible. Model strings change shape — Vercel's slugs are provider-prefixed, and you should map them against nRouter's live catalog rather than assuming a name carries across.

What leaves your configuration entirely is the credential fan-out: the per-provider BYOK entries, the request-scoped byok blocks, and the modelMappings arrays that point a gateway slug at your own Azure deployment names. nRouter holds the provider credentials, so there is nothing on your side to rotate, scope to a team, or test from a dashboard.

Migrating your Vercel-specific config

Maps cleanly. Provider fallback ordering becomes routing configuration. Budgets become organisation, team and per-key ceilings — and, unlike the originals, they cover every dollar. Spend monitoring becomes per-key and per-team spend. App attribution becomes per-key identity, which is the same idea with a credential attached to it.

Maps differently. Vercel's OIDC token has no counterpart: nRouter authenticates a virtual key, not a deployment. The equivalent hygiene is a short-lived, narrowly scoped key per service rather than one shared secret, plus rotation when a service is retired. That is more work than OIDC and less work than a per-provider key matrix.

Has no equivalent. Request-scoped byok, modelMappings, inferenceRegion and per-request ZDR all assume you supply the provider credential; with no BYOK there is nothing for them to attach to. Google-family models have no equivalent because they are not in the catalog. And the AI SDK's native gateway provider becomes the OpenAI-compatible provider — same calls, less sugar.

Why every feature on every plan is sustainable

Short version: the platform fee is not where the margin is meant to come from, which is why there is no commercial reason to gate a budget or a guardrail behind an upgrade the way Model Allowlist sits on Pro and Enterprise. The long version — what funds it, and what would have to change for the position to break — is written once, here: every feature on every plan: we charge a fee, not a gate.

When nRouter is the right choice

Pick nRouter over Vercel AI Gateway if two or more of these are true:

  • You need a spending cap that covers all of your LLM spend, not the share of it that runs on system credentials.
  • Meaningful inference originates outside Vercel — Lambda, Cloud Run, Fly, a Kubernetes pod, a customer's own environment — and you want the same rules to apply there without a second auth story.
  • You want model restriction, guardrails, evals and per-team budgets on the cheapest plan rather than on Pro and Enterprise.
  • You would rather never hold a provider key again, including the ones you are currently holding only because a budget could not reach them.
  • Your shortlist is Anthropic, OpenAI, Azure AI Foundry and Bedrock models.

When to stay on Vercel AI Gateway

Stay if any of these is true. These are not close calls:

  • A Google, Gemini or Vertex model is on your shortlist. nRouter serves none.
  • You hold provider-granted credits or a negotiated enterprise rate you need to spend through the gateway. That is BYOK, and BYOK is theirs.
  • You have a data-residency or ZDR requirement today. Vercel ships documented controls; nRouter's SOC 2 Type II is in progress.
  • Every AI call originates from a Vercel deployment and OIDC is doing real work in your threat model.
  • The AI SDK's native gateway integration is deep in your codebase and the ergonomic downgrade costs you more than the governance gap costs you.

For everyone else — teams whose spend crossed a hosting boundary, teams who discovered their budget covered a third of the bill — the switch is the two lines above.

Try it

Pay as you go starts at $5. Load the $5 minimum, with the platform fee on top and no subscription. Set a team budget deliberately low and watch a call come back 402 budget_exceeded — the cheapest possible way to find out whether a governance claim is real.

→ Get started at app.nrouter.ai/signup

Weighing pay as you go against Pro? Bring your current Vercel AI Gateway usage and your provider invoices to a 30-minute call and we will do the breakeven math live. Questions go to the public nRouter Slack — #support for migration, #feature-requests if there is a Vercel capability you want next.

See also

Sources

Every Vercel and Cloudflare claim above is sourced from that vendor's own public documentation and was checked on 2026-08-23. If a vendor has changed a number since, email hello@nrouter.ai and we will re-audit within one business day.

Vercel, Cloudflare and Anthropic are trademarks of their respective owners. nRouter is not affiliated with or endorsed by them.

Share
Written by nRouter teamEngineering, product, and company posts from the nRouter team — code-first, cost-honest, no vendor-marketing fluff.

More from Comparison

All posts →
Langfuse alternative: observability AND routing AND governance included on every plan
Comparison

Langfuse alternative: observability AND routing AND governance included on every plan

Head-to-head: nRouter vs Langfuse. A self-hostable observability + prompt + evals specialist vs a hosted LLM gateway that bundles observability, routing, and governance — every feature included on every plan. Pay-as-you-go fee of 4% of your credits, 0% on Pro. Models available in your live catalog behind one API key.

nRouter team
9 minRead →
TrueFoundry AI Gateway alternative: buying one module of a platform
Comparison

TrueFoundry AI Gateway alternative: buying one module of a platform

TrueFoundry's gateway is one module of a platform that also sells model deployment, GPU serving, and agent, MCP and skills registries — metered by requests and by seat. nRouter sells the gateway alone, priced as a share of model spend. A procedure for deciding which purchase you are making.

nRouter team
12 minRead →
NotDiamond alternative: a router picks a model, a gateway runs the call
Comparison

NotDiamond alternative: a router picks a model, a gateway runs the call

Not Diamond returns a model recommendation and charges $0.05 per million tokens routed — you still hold every provider key and make the call yourself. What that leaves you to build, and how deterministic A/B tests compare to a trained router when you have to reproduce a decision.

nRouter team
12 minRead →