Start from what you already run

Every other page here starts with a product. This one starts with your infrastructure. Pick something you already run and see which of the 20 products slot into it — and, more usefully, which ones say they do and mean something else.

The middle column is the point of this page. A product lands there when the support is real but not the thing the marketing implies: documented by somebody else, a community package with no support obligation, or a Helm chart nobody names. Those are workable answers. They are not the same answer as a yes, and this page refuses to round them up into one.

The OpenAI SDK

18 fit · 2 with a caveat · 0 no

My code already uses the OpenAI SDK. What can I point it at?

Fits18

  • OpenRouter Drop-in: change the base URL and key, nothing else.
  • Requesty Drop-in: change the base URL and key, nothing else.
  • Braintrust Gateway Drop-in: change the base URL and key, nothing else.
  • Helicone Drop-in: change the base URL and key, nothing else.
  • Orq.ai Router Drop-in once set up — but first-call work is cloud console setup.
  • Portkey Drop-in once set up — but first-call work is sdk install.
  • Vercel AI Gateway Drop-in once set up — but first-call work is sdk install.
  • Bifrost Drop-in once set up — but first-call work is cli or container.
  • LiteLLM Drop-in once set up — but first-call work is cli or container.
  • LLM Gateway Drop-in: change the base URL and key, nothing else.
  • Amazon Bedrock Drop-in once set up — but first-call work is cloud console setup.
  • Azure AI Foundry Drop-in once set up — but first-call work is cloud console setup.
  • Cloudflare AI Gateway Drop-in once set up — but first-call work is cloud console setup.
  • Google Vertex AI Drop-in once set up — but first-call work is cloud console setup.
  • TrueFoundry AI Gateway Drop-in once set up — but first-call work is cloud console setup.
  • Fireworks AI Drop-in once set up — but first-call work is sdk install.
  • Groq Drop-in once set up — but first-call work is sdk install.
  • Together AI Drop-in once set up — but first-call work is sdk install.

With a caveat2

No0

Everything here has some answer.

Back to top ↑

The Vercel AI SDK

13 fit · 4 with a caveat · 3 no

I build with the AI SDK. Which products have a real provider package?

Only “official provider” means a maintained first-party package. The rest are workarounds of varying quality.

Fits13

With a caveat4

No3

Back to top ↑

Cloudflare Workers

4 fit · 2 with a caveat · 14 no

I run on Workers. What can I actually call from the edge?

Three products market Cloudflare Workers heavily and mean their own gateway runs there. That does not help you call them from your Worker, so they are not counted as a fit.

Fits4

With a caveat2

No14

Back to top ↑

Kubernetes

11 fit · 2 with a caveat · 7 no

I have a cluster and want this inside it. What can I install?

Fits11

  • Requesty Helm repo https://helm.requesty.ai (chart name not stated)
  • Braintrust Gateway braintrust from oci://public.ecr.aws/braintrust/helm/braintrust
  • Helicone helicone-core, helicone-infrastructure, helicone-monitoring, helicone-argocd
  • Kong AI Gateway kong/ingress and kong/kong from https://charts.konghq.com
  • Orq.ai Router single Orq chart, Kubernetes 1.28+
  • Portkey charts/portkey-gateway and charts/portkey-app in Portkey-AI/helm
  • Apache APISIX AI Gateway apache/apisix-helm-chart; API7 ships api7/gateway from https://charts.api7.ai
  • Bifrost bifrost/bifrost from https://maximhq.github.io/bifrost/helm-charts
  • LiteLLM litellm-helm at oci://ghcr.io/berriai/litellm-helm — the GitHub page describes it as community maintained
  • LLM Gateway OCI chart on GHCR; deploys gateway, API, UI and worker, and needs PostgreSQL plus Redis
  • TrueFoundry AI Gateway tfy-llm-gateway for the Gateway Plane, truefoundry for the full control plane plus gateway plane

With a caveat2

No7

Back to top ↑

Terraform or OpenTofu

4 fit · 11 with a caveat · 5 no

Everything I run is in code. What can I declare?

Fits4

With a caveat11

No5

Back to top ↑

An existing API gateway

2 fit · 6 with a caveat · 12 no

I already run Kong or APISIX. Can AI traffic go through it?

Fits2

With a caveat6

No12

Back to top ↑

Cloud IAM I already run

10 fit · 1 with a caveat · 9 no

Can I authenticate with my existing cloud identity instead of another API key?

Fits10

With a caveat1

No9

Back to top ↑

LangChain or LlamaIndex

14 fit · 5 with a caveat · 1 no

I orchestrate in Python. What has documented framework integrations?

Fits14

With a caveat5

No1

Back to top ↑

MCP servers to govern

7 fit · 12 with a caveat · 1 no

I have MCP servers and need one place to control access to them.

Only an MCP gateway answers this. A hosted MCP server or MCP tool support in a completion API is a different product shape wearing the same acronym.

Fits7

With a caveat12

No1

Back to top ↑

Nothing — plain Node or Python

9 fit · 5 with a caveat · 6 no

I want to write code and call something. No console, no cluster.

Fits9

With a caveat5

  • Kong AI Gateway You have to run a process locally before any call works.
  • Portkey Install a package, but an upstream provider key is a prerequisite.
  • Apache APISIX AI Gateway You have to run a process locally before any call works.
  • Bifrost You have to run a process locally before any call works.
  • LiteLLM You have to run a process locally before any call works.

No6

Back to top ↑

A note on what “no” means here

Almost every “no” on this page is silence in the vendor’s documentation rather than a refused feature. A product with no published Workers guidance may well work fine from a Worker — it is a fetch call — but nobody has committed to that in writing, so verifying it is your job rather than theirs. That distinction is worth more when you are choosing than a confident tick would be.

Reading it the other way round: each product’s own page carries the same checklist scored for that one product, alongside the evidence links behind every answer. See the full list, or answer a few questions and let the site narrow it for you.