Lattice
Skip to content

Cloudflare AI Gateway alternatives

3 substitutes · 3 in routing · 0 adjacent

The short answer

3 tools on this index are recorded as a substitute for Cloudflare AI Gateway. 1 of these runs the same way you already deploy Cloudflare AI Gateway (saas), and 2 are permissively licensed, so they do not change what you can ship. All of them sit in Routing & Gateways, so the choice is a real one rather than a category change. There is no overall winner here: which one is right depends on traffic shape, operational budget and how much of Cloudflare AI Gateway you have already built around.

By Lattice editorial · Comparison reviewed · method

Better than this page

3

Real substitutes

in Routing & Gateways
  • LiteLLMlibrary · MIT

    OpenAI-format proxy translating across 100+ model providers.

    Use when The widest provider coverage, deployed the least committal way.

    Skip when You want routing policy to live in a SaaS console.

  • Portkeyplatform · proprietary

    AI gateway with routing, caching and guardrails in one layer.

    Use when A managed gateway with guardrails and analytics already bundled.

    Skip when Prompts cannot leave your infrastructure.

  • Envoy AI Gatewayruntime · Apache-2.0

    CNCF-track gateway for LLM traffic on an Envoy data plane.

    Use when A Kubernetes shop that already runs Envoy and needs the gateway in-cluster.

    Skip when You want a gateway configurable without a data plane.

This graph is bidirectional and unsponsored. A tool appears here if Cloudflare AI Gateway or another entry names it as a substitute, and LiteLLM, Portkey and Envoy AI Gateway point at Cloudflare AI Gateway as well. How this index is compiled — including where it is wrong.