Skip to content

Alternatives

Vercel AI Gateway alternatives (and the AI SDK without a gateway)

Vercel AI Gateway charges no markup on tokens, so the reason to look elsewhere is control, not price: when a request on your own key fails it is retried on Vercel's system credentials and charged to your Vercel balance, and its budgets do not count your own-key spend. The alternatives are INFRO, Cloudflare AI Gateway, OpenRouter, LiteLLM and Portkey, or the AI SDK pointed straight at a provider with no gateway at all.

By INFRO Editorial

Last updated

Last checked

On this page
  1. Why teams look past Vercel AI Gateway
  2. First option: the AI SDK without a gateway
  3. The alternatives, side by side
  4. How each one treats your own keys
  5. Which one to choose
  6. Using INFRO with the AI SDK
  7. Questions
  8. Sources

Why teams look past Vercel AI Gateway

Vercel AI Gateway charges "no markup and no platform fee on tokens", including with your own keys. It is a good default for an app on Vercel. Two documented behaviours are the usual reasons to look further:

  • A failed BYOK request runs on Vercel's credentials. Vercel's pricing page says that when a request on your credentials fails, AI Gateway retries it with its own system credentials and charges that usage to your AI Gateway balance. Good for availability; but a request you meant to keep on your own contract and data terms can run on Vercel's.
  • Budgets do not see BYOK spend. Spend through your own credentials is not counted in budgets, so a budget cannot cap BYOK traffic.

If neither matters to you, stay.

First option: the AI SDK without a gateway

The AI SDK uses AI Gateway by default when you pass a model string, but it does not need it. Set a provider package such as @ai-sdk/openai as the default, or pass a provider instance, and the SDK calls that provider directly with your key. For one provider and one app, that removes a hop and a dashboard; you give up cross-provider failover and budgets, which you then build yourself.

The alternatives, side by side

Each option is described from its own pricing page and documentation, checked on the date at the top. INFRO is listed first because this is INFRO's site; its limits are listed as plainly as everyone else's.

Who it is for
Teams that hold, or want to hold, their own provider contracts and need routing, failover, budgets and cost per customer across them.
How it charges
A flat plan of $35–$599 a month, chosen by request volume (100K–10M requests a month), never by spend. 0% markup on model spend: your providers bill you directly.

Strengths

  • Every request runs on a provider account you own; INFRO holds none, so nothing falls back onto someone else's contract.
  • Budgets refuse a request before the provider is called, per organization, project, member and key, and (from the Team plan) per end customer.
  • Each response names the provider, connection and model that served it, with an estimated provider cost.

Limits

  • No shared capacity: when every connection you own fails, the request fails with an error that says why.
  • Hosted only on its plans; a self-hosted deployment needs an enterprise agreement.
  • No prompt management or output evaluation.
  • A subscription, where Vercel charges nothing on tokens.
Who it is for
Applications already on Cloudflare that want logging, caching and spend limits close to their Workers.
How it charges
Core features are free. Your own keys carry no fee; paying through Cloudflare's Unified Billing adds 5% on each purchase.

Strengths

  • Free core gateway with caching, logging, rate limits and model fallbacks.
  • Spend limits that count your own-key traffic for models with known pricing.

Limits

  • Spend limits are eventually consistent: a burst of concurrent requests can briefly pass them.
  • Caching is exact-match only, for text and image responses.

Full comparison with Cloudflare AI Gateway

Who it is for
Teams that want hundreds of models behind one key and one balance, without an account at each provider.
How it charges
5.5% on each balance purchase (8% on Business). With your own keys: no fee on the first $25,000 a month of list-price usage, then 5%.

Strengths

  • 500+ models, 80+ providers behind one API key.
  • Inference at each provider's list price, with routing and fallbacks between providers.

Limits

  • The fee grows with your spend, and your negotiated rates do not apply to its balance.
  • With your own keys, a failed request falls back to OpenRouter's shared capacity by default.

Full comparison with OpenRouter

Who it is for
Teams that want no vendor in the request path and have engineers to run a production service.
How it charges
MIT-licensed and free to self-host. Enterprise is a license key on the same image, priced by deployment size; no price is published.

Strengths

  • No third party sees your traffic or your keys.
  • Spend tracked per key, team, user, tag, with a budget and model list on each key.
  • Broad provider coverage and an active open-source project.

Limits

  • You run it: a server, a Postgres database, upgrades, and someone on call while it is in the request path.
  • Its release pipeline is part of your supply chain: two PyPI releases carried credential-stealing code on 24 March 2026.

Full comparison with LiteLLM

Who it is for
Enterprises buying an AI gateway as part of a security platform, or teams self-hosting Portkey's open-source gateway.
How it charges
Production is $49 a month with 100,000 recorded logs, plus $9 per additional 100,000. The open-source gateway is MIT licensed. Enterprise is custom.

Strengths

  • Mature routing, fallbacks, guardrails and observability.
  • An MIT-licensed gateway you can host yourself.

Limits

  • Palo Alto Networks completed its acquisition on 29 May 2026; the product is now Prisma AIRS AI Gateway, so check its roadmap fits a team not buying the wider platform.
  • Logs, observability and prompt management are in the hosted app, not the open-source gateway.

Full comparison with Portkey (Prisma AIRS AI Gateway)

Who it is for
Apps on the AI SDK that call one provider and do not need a gateway yet.
How it charges
No gateway fee. You pay each provider directly.

Strengths

  • No extra party in the data path.
  • Provider-side limits per organization and project.

Limits

  • Failover, budgets per customer and cross-provider cost attribution are yours to build.
  • One error model, rate-limit scheme and dashboard per provider.

How each one treats your own keys

GatewayWhen your key failsBudgets count your own-key spend
Vercel AI GatewayRetried on Vercel's credentials, charged to your balanceNo
OpenRouterFalls back to OpenRouter's shared capacity by default; per-key setting to turn offOnly with "Include BYOK spend"
Cloudflare AI GatewayModel fallbacks you configureYes, for models with known pricing
LiteLLMFallbacks you configure, across your deploymentsYes, a budget on each key
INFRONext of your own connections only; otherwise an error naming each attemptYes, every request is on your keys
From each vendor's own documentation, read on the date at the top.

Which one to choose

Stay on Vercel AI Gateway
if you build on Vercel and a fallback on Vercel's credentials is acceptable.
The AI SDK, no gateway
if one app calls one provider and its own limits are enough.
INFRO
if every request must stay on your own accounts and budgets must cap all of it, per project, key and customer.
Cloudflare AI Gateway
if you want a free gateway whose spend limits count your own keys.
OpenRouter
if you want every model behind one balance without provider accounts.
LiteLLM or Portkey
if you want to self-host, or a gateway inside a security platform.

Questions

Does Vercel AI Gateway charge a fee?
Vercel says it charges no markup and no platform fee on tokens, including with your own keys; some capabilities are paid add-ons.
What happens when my own key fails on Vercel AI Gateway?
Vercel retries the request with its own system credentials and charges that usage to your AI Gateway balance.
Can I use the Vercel AI SDK without AI Gateway?
Yes. The SDK defaults to AI Gateway for model strings, but you can set a provider such as @ai-sdk/openai as the default, or pass a provider instance, and call the provider directly.

Sources

Every statement about another company on this page comes from that company's own page, opened on the date shown. Prices and defaults change; check the source before you decide.

  1. 1.vercel.com/docs/ai-gateway/pricing (opens in a new tab) — checked Oct 24, 2026.
    • Vercel AI Gateway charges no markup and no platform fee on tokens; you pay the provider's list price.
    • Bringing your own provider key adds no Vercel fee.
    • When a request on your own credentials fails, Vercel retries it on its own system credentials and charges that usage to your Vercel AI Gateway balance.
    • Spend on your own credentials is not counted in Vercel AI Gateway budgets, so a budget cannot cap BYOK spend.
  2. 2.vercel.com/docs/ai-gateway/byok (opens in a new tab) — checked Oct 24, 2026.
    • Vercel's BYOK docs describe the same retry on system credentials.
  3. 3.ai-sdk.dev/docs/ai-sdk-core/provider-management (opens in a new tab) — checked Oct 24, 2026.
    • The Vercel AI SDK uses AI Gateway by default when you pass a model string; you can set a provider such as @ai-sdk/openai instead and call it directly.
  4. 4.developers.cloudflare.com/ai-gateway/reference/pricing (opens in a new tab) — checked Oct 24, 2026.
    • Cloudflare AI Gateway's core features are free.
  5. 5.developers.cloudflare.com/ai-gateway/configuration/bring-your-own-keys (opens in a new tab) — checked Oct 24, 2026.
    • Cloudflare AI Gateway can store your own provider keys (BYOK) in the dashboard.
  6. 6.developers.cloudflare.com/ai-gateway/features/unified-billing (opens in a new tab) — checked Oct 24, 2026.
    • Usage paid for through Cloudflare's Unified Billing carries a 5% fee on each purchase.
  7. 7.developers.cloudflare.com/ai-gateway/features/spend-limits (opens in a new tab) — checked Oct 24, 2026.
    • Cloudflare's spend limits count both Unified Billing and BYOK requests, for models with known pricing, and answer 429 when exceeded.
    • Cloudflare's spend limits are eventually consistent: a burst of concurrent requests can briefly pass the limit.
  8. 8.developers.cloudflare.com/ai-gateway/configuration/fallbacks (opens in a new tab) — checked Oct 24, 2026.
    • Cloudflare AI Gateway can fall back to another model or provider through its Universal endpoint when a request returns an error.
  9. 9.developers.cloudflare.com/ai-gateway/features/caching (opens in a new tab) — checked Oct 24, 2026.
    • Cloudflare caches only identical requests, for text and image responses, for 60 seconds to one month; semantic caching is planned, not available.
  10. 10.openrouter.ai/pricing (opens in a new tab) — checked Oct 24, 2026.
    • OpenRouter charges a 5.5% fee each time you add balance on its Standard (pay-as-you-go) tier.
    • On its Business (pay-as-you-go) tier the fee on each balance purchase is 8%.
    • With your own provider keys (BYOK), the first $25,000 a month of list-price inference carries no OpenRouter fee.
    • OpenRouter bills inference at the provider's list price; its fee is charged when you add balance instead.
    • OpenRouter's paid tiers list 500+ models from 80+ providers.
  11. 11.openrouter.ai/docs/guides/overview/auth/byok (opens in a new tab) — checked Oct 24, 2026.
    • Past the allowance, BYOK usage is charged 5% of what the same model and provider would cost on OpenRouter.
    • By default, a BYOK request that fails or is rate limited on your key falls back to OpenRouter's shared endpoints, paid from your OpenRouter balance; a per-key "Shared capacity fallback" setting turns that off.
  12. 12.litellm.ai (opens in a new tab) — checked Oct 24, 2026.
    • The LiteLLM gateway is MIT licensed and free to self-host.
  13. 13.docs.litellm.ai/docs/enterprise (opens in a new tab) — checked Oct 24, 2026.
    • LiteLLM Enterprise is a license key on the same image, priced by deployment size and usage; no price is published.
  14. 14.docs.litellm.ai/docs/simple_proxy (opens in a new tab) — checked Oct 24, 2026.
    • LiteLLM records the cost of each request and shows spend per key, team, user and tag; each key carries a team, a budget and a model list.
    • The LiteLLM gateway is a self-hosted server started with Docker, Helm or Terraform, backed by a Postgres database you run.
  15. 15.docs.litellm.ai/blog/security-update-march-2026 (opens in a new tab) — checked Oct 24, 2026.
    • On 24 March 2026, litellm 1.82.7 and 1.82.8 on PyPI carried credential-stealing code for about 40 minutes; LiteLLM says the official Proxy Docker image was not affected and 1.83.0 is clean.
  16. 16.portkey.ai/pricing (opens in a new tab) — checked Oct 24, 2026.
    • Portkey's Production plan is $49 a month and includes 100,000 recorded logs.
    • Past the included volume, Production adds $9 for each additional 100,000.
    • Portkey's pricing page says Portkey is now Prisma AIRS AI Gateway.
  17. 17.github.com/Portkey-AI/gateway (opens in a new tab) — checked Oct 24, 2026.
    • Portkey's open-source gateway is MIT licensed; logging, observability and prompt management are available on the hosted app only.
  18. 18.paloaltonetworks.com/company/press/2026/palo-alto-networks-completes-acquisition-of-portkey-to-secure-ai-agents (opens in a new tab) — checked Oct 24, 2026.
    • Palo Alto Networks completed its acquisition of Portkey on 29 May 2026.
  19. 19.developers.openai.com/api/docs/guides/rate-limits (opens in a new tab) — checked Oct 24, 2026.
    • OpenAI sets rate limits per organization and per project, not per user.

The team building INFRO, a BYOK-first control plane for production AI. Articles are written from the engineering work on the gateway and cite their external sources.