GateLLM vs Cloudflare AI Gateway
A source-verified comparison. Cloudflare AI Gateway is a managed edge proxy fronting 20+ providers; GateLLM is a self-hosted BYOK gateway. The differences are deployment, protocol entrypoints, and the fee model.
Comparison table
Only GateLLM does this
Mechanisms the managed edge gateway does not offer — the one-line "how it works" sits under each capability.
| Capability | GateLLM | Cloudflare AI Gateway |
|---|---|---|
| Native multi-protocol entrypointsFour native ingresses (OpenAI / Anthropic / Gemini / DashScope) translate any-to-any. Cloudflare AI Gateway fronts providers through a single OpenAI-compatible endpoint. | Yes | No |
| Self-hosted, data stays in your networkRuns fully in your VPC / on-prem. Cloudflare AI Gateway is a managed edge service — traffic transits Cloudflare's network. | Yes | No |
| Conditional model switching (built-in plan-mode detection)Declarative switch-route rules + built-in Claude Code plan-mode detection + useModel scripts. Cloudflare offers retry / fallback routing but no per-request rewrite layer. | Yes | No |
Both do these well
A settled baseline — either gateway covers this layer. The decision lives in the layers above and below.
| Capability | GateLLM | Cloudflare AI Gateway |
|---|---|---|
| Multi-model routing & fallback | Yes | Yes |
| Load balancing across providers | Yes | Yes |
| Token usage & cost metering | Yes | Yes |
| Rate limiting & quotas | Yes | Yes |
| Multiple API key management | Yes | Yes |
| MCP tool integration | Yes | Yes |
| Visual console | Yes | Yes |
| Audit logging | Yes | Yes |
Different in kind
Not better or worse — different deployment, pricing, and configuration models you should weigh directly.
| Capability | GateLLM | Cloudflare AI Gateway |
|---|---|---|
| Runtime | Single Rust binary · no GC pauses | Managed edge (Workers / proxy) |
| Pricing | Flat per-instance license, no token markup | Free core + paid plans; 5% fee on unified-billing credits |
| Configuration | Fully in console — no YAML, atomic commits | Dashboard + API |
| Ecosystem lock-in | Cloud-neutral — any model vendor | Tight Cloudflare edge + Workers integration |
| Ops model | You run the gateway | Managed edge service |
Verified against official docs as of 2026-09-06 (developers.cloudflare.com / docs.gatellm.io). Features and pricing drift — check the sources before procurement.
How the differentiators work
Each GateLLM differentiator is a mechanism, not a marketing line. Here is what it does under the hood, and what Cloudflare AI Gateway does instead.
Native multi-protocol entrypoints
GateLLM: Four native ingresses (OpenAI / Anthropic / Gemini / DashScope) translate any-to-any — one gateway serves every SDK natively.
Where rivals fall short: A single OpenAI-compatible endpoint across 20+ providers.
Self-hosted data path
GateLLM: Runs inside your VPC / on-prem. Prompts never enter our systems; request logs off by default.
Where rivals fall short: Managed edge — traffic transits Cloudflare's network.
Plan-mode model switching
GateLLM: Declarative switch-route rules + built-in Claude Code plan-mode detection + useModel scripts — planning on top-tier models, execution on open SOTA, zero client change.
Where rivals fall short: Retry / fallback routing without a per-request rewrite layer.
Migrating from Cloudflare AI Gateway
Point your SDK base_url at GateLLM — no other code changes. Your model keys and routing policies carry over; enable plan-mode switching only as needed.
- 1Point your OpenAI SDK base_url at GateLLM (with /v1) — one line, no other code changes.
- 2Enter your model-provider keys into the console (BYOK) — they live in gateway memory, never persisted.
- 3Recreate your routing / fallback policies in the console — they carry over 1:1.
BYOK self-hosted vs managed edge proxy
GateLLM is licensed per instance / memory with never a token markup, and your prompts never transit a third-party edge. Cloudflare AI Gateway charges a 5% fee on unified-billing credits and keeps traffic on Cloudflare's edge.
Cost structure
- •GateLLM: flat per-instance license (Pro 2GB $400/mo) — no token markup.
- •Cloudflare AI Gateway: free core features; paid plans add limits; 5% fee on credits purchased through unified billing.
- •At high volume the flat license decouples cost from usage; the 5% credit fee scales with spend.
When to choose which
Choose Cloudflare if…
You want a zero-setup edge proxy and accept a 5% unified-billing fee plus data transiting Cloudflare's network.
Choose GateLLM if…
Data must stay in your VPC, you need native multi-protocol entrypoints and plan-mode switching, and you want a flat license with no percentage fee.
Both can coexist
Use Cloudflare AI Gateway for edge experiments, then route production through your own GateLLM gateway once you have BYOK keys and a compliance requirement.
FAQ
Verified 2026-09-06 against developers.cloudflare.com and docs.gatellm.io. Features and pricing drift — check the sources before procurement.