Squiid vs Vercel AI Gateway
Vercel AI Gateway is the model layer of the Vercel platform: one endpoint, one credential, failover and analytics in a dashboard you already have open. Squiid is the same idea for the whole stack.
Short answer. If you deploy on Vercel and the only thing you want unified is model access, use the AI Gateway: it is wired into the AI SDK and usage lands on the invoice you already pay. Squiid is the better fit when the list is longer than models.
The one-line difference. Vercel AI Gateway unifies model providers for an app that lives on Vercel. Squiid unifies every provider an app needs, on any host, and opens the accounts instead of assuming you already did.
Side by side
| Vercel AI Gateway | Squiid | |
|---|---|---|
| What it covers | Models. One endpoint and credential over many providers, wired into the AI SDK, with failover and analytics in the Vercel dashboard. | The whole catalogue: databases, hosting, email, SMS, storage, auth and payments, models included. Model calls go to a named provider, not a router. |
| Non-AI services | Not through the gateway. Other services come from Vercel or its marketplace. | Yes. Postgres, object storage, email, phone numbers, error tracking. |
| Provisioning of accounts | No signup for routed models, or bring your own provider keys, as of their public docs. | Yes. Squiid opens the account and holds the credential. |
| Key custody and rotation | One gateway credential for models, in your Vercel environment variables. Other secrets stay in that same list. | Squiid holds and rotates the provider keys. Your project carries one gateway key, worthless outside it. |
| Billing model | Bills through your Vercel account. Vercel describes the gateway as passing provider pricing through; check their pricing page. | Prepaid credits at par: $1 of credit is $1 at the provider. Subscriptions pass through at list price. |
| Fee | We do not quote a figure we have not verified. See Vercel pricing for current terms. | Free $0/mo + 15% at top-up. Solo $19.97/mo from 8%, falling to 3.5% with spend. Team from $29.97/seat, one point lower. Custom 3% or less. |
| One invoice PDF | One Vercel invoice for Vercel products. Anything else invoices separately. | Yes. One monthly PDF: credits, plan, subscriptions. |
| Spend caps and pause-on-zero | Spend management lives in the Vercel account and covers Vercel billed usage, as of their public docs. | Yes. Alerts at 75, 90 and 100%, capped auto top-up, pause at zero. |
| Works with coding agents | Yes, particularly anything written against the AI SDK. It behaves like any OpenAI compatible base URL. | Yes. One variable and one base URL convention for every service. |
| Self-host option | No. It is part of the Vercel platform. | No. Hosted only. Leaving is a transfer where the provider supports one, a documented export otherwise. See handover. |
| Best for | Teams on Vercel who want model access on the invoice they already receive. | Projects where the model bill is one line next to the database. |
When to pick Vercel AI Gateway instead
Pick it when your app lives on Vercel and is likely to stay. Variables are already managed in the project, the AI SDK talks to it natively, and usage shows up next to bandwidth and functions.
Pick it when you want the fewest new relationships. If Vercel is already your host, adding model access there is zero new vendors, invoices or logins.
Pick it if your model needs are simple and the stack is settled. Plenty of apps need models, a Postgres database and nothing else.
When Squiid is the better fit
Squiid is the better fit when you are not on Vercel, or do not want your host deciding the rest of the stack. Vercel, Netlify, Railway, Fly and Render sit in one catalogue, so hosting stays a choice.
It is also the better fit when the services you need are not models. A phone number, an email domain, an auth tenant, storage and error tracking each need an account, key and invoice.
And it is the better fit if you want a hard stop on spend. Prepaid credits that pause at zero are a different safety model from a postpaid platform invoice.
Use both
Running both is reasonable. Deploy on Vercel, use the AI Gateway for model traffic, and Squiid for the database, email, SMS, storage and auth behind it: one Vercel-managed credential and one SQUIID_API_KEY. For one prepaid balance and one PDF, point the model calls at Squiid too.
Questions people ask
Do I have to be on Vercel to use their AI Gateway?
It is designed around a Vercel project, convenient if you are there and awkward if you are not. Squiid is host-neutral: the same key works on Vercel, Fly, Railway, Render or a box you rent.
Does Vercel mark up model tokens?
Vercel has described the gateway as passing provider pricing through, but packaging changes often enough that we will not print a number. Check their pricing page. Squiid credits are at par.
Is the Vercel Marketplace the same thing as Squiid?
It is the closest thing Vercel has. See Squiid vs the Vercel Marketplace for where they differ.
Can I keep Vercel hosting and still buy it through Squiid?
Yes. Vercel is in the catalogue as a hosting service, so the subscription passes through at list price with no fee. Nothing about how you deploy changes.
Which one does my coding agent prefer?
Neither cares. Both are a base URL and a bearer token. The difference is how many variables the agent sees: one per layer, or one for everything.
Your host should not
pick your stack.
One key for every service, on whatever platform you deploy to. Provider prices, no markup.