Squiid vs Portkey
Portkey is a serious AI gateway: one API over a large model catalogue, with fallback, guardrails, caching, observability and virtual keys that carry budgets. Squiid is about everything else.
Short answer. If you want per-key budgets, guardrails, prompt observability and config-driven fallback over providers you already hold, Portkey is the better tool and Squiid does not compete with it. Squiid answers a different question: how many provider accounts, credentials and invoices your project has.
The one-line difference. Portkey governs model traffic from providers you own. Squiid holds the provider relationships for the whole stack, so the database, host, email sender and auth tenant arrive provisioned on one key.
Side by side
| Portkey | Squiid | |
|---|---|---|
| What it covers | An AI gateway. One OpenAI-compatible API over a large provider catalogue, with fallback, load balancing, retries, caching, guardrails, prompt management and observability. | 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 | No. It is a model-traffic product from end to end. | Yes. Postgres, object storage, email, phone numbers, error tracking. |
| Provisioning of accounts | No. You bring your own accounts and keys, stored as virtual keys with limits attached. | Yes. Squiid opens the account and holds the credential. |
| Key custody and rotation | Portkey holds your provider keys behind virtual keys. Rotating the real credential is still a job at the provider. | Squiid holds and rotates the provider keys. Your project carries one gateway key, worthless outside it. |
| Billing model | You pay each provider for usage. Portkey charges for the gateway platform, as of their public docs. | Prepaid credits at par: $1 of credit is $1 at the provider. Subscriptions pass through at list price. |
| Fee | No markup on inference. You are paying for the gateway, not for the tokens. | 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 | A Portkey invoice plus one invoice per model provider you hold. | Yes. One monthly PDF: credits, plan, subscriptions. |
| Spend caps and pause-on-zero | Strong at the model layer. Budgets and rate limits per virtual key, a genuinely good leash for an agent. | Yes. Alerts at 75, 90 and 100%, capped auto top-up, pause at zero. |
| Works with coding agents | Yes. An OpenAI-compatible base URL and a key. | Yes. One variable and one base URL convention for every service. |
| Self-host option | Yes. The gateway is open source, with hosted and enterprise options too. | No. Hosted only. Leaving is a transfer where the provider supports one, a documented export otherwise. See handover. |
| Best for | Budgets, guardrails and observability over model providers you intend to keep owning. | Projects where the model bill is one line next to the database. |
When to pick Portkey instead
Pick Portkey when governance of model traffic is the requirement. Virtual keys with budgets give each app, team or agent a hard ceiling on inference, the control most teams want a week after handing an agent a provider key.
Pick it when you need guardrails in the request path: input and output checks, redaction, policy that runs whether or not the calling code remembers to. Squiid does not operate in that category.
Pick it when prompt management and per-request tracing matter. Seeing the exact prompt, response, latency and cost, then replaying it, is the difference between debugging and guessing.
Pick it when you want to self-host. The gateway is open source, so the traffic path can live inside your own network, which some compliance postures require.
When Squiid is the better fit
Squiid is the better fit when the account count, not the model policy, is the problem. Portkey assumes you hold OpenAI, Anthropic and the rest. Squiid opens those accounts and holds the credentials.
It is also the better fit when you want one prepaid balance for the whole stack. Virtual key budgets cap model spend, not what the database, email sender and SMS number cost.
And it is the better fit for the paperwork: one monthly PDF instead of a gateway invoice, a model invoice, a database invoice and a hosting invoice on four dates.
Use both
The combination suits a team that has outgrown a single model key. Portkey for model governance over the providers you keep direct, Squiid for the database, host, email, SMS, storage and auth. If your model policy needs are simple, Squiid alone is fewer moving parts.
Questions people ask
Is Squiid an AI gateway like Portkey?
Only partly. Squiid routes model calls to named providers, with no routing config, guardrails or prompt management. What it adds is provisioning, key custody and billing, mostly over services that are not models.
Does Portkey mark up my inference?
No. As of their public docs you pay the providers and pay Portkey for the gateway. Squiid also takes nothing on usage: credits are at par and the fee is taken at top-up.
Which gives an agent a harder spending limit?
For inference, Portkey virtual key budgets are more granular. For the whole app, a prepaid balance is stricter: every service pauses at zero rather than billing in arrears, including the ones a model budget never sees.
Can I self-host Squiid the way I can self-host the Portkey gateway?
No. Squiid is hosted, because holding the upstream provider relationships is the product. If self-hosting the traffic path is a requirement, Portkey or LiteLLM is the right tool.
Do they overlap on observability?
Lightly. Squiid shows which key called which service and what it cost, which answers billing questions. Portkey is built for request-level tracing. To inspect prompts, use a product designed for it.
Governing models is
one job of sixteen.
One key, provider prices, and a balance that pauses at zero.