Cloudflare Flagship vs Flagger.gg
Cloudflare Flagship is Cloudflare's feature flag service, in public beta since May 2026, built on OpenFeature and evaluated inside Workers from config at the edge. Flagger.gg is a hosted flag service for teams whose code is written by AI agents: its Go and Node SDKs evaluate in memory in your own servers, and agents work through MCP and a JSON CLI with scoped tokens. Pick Flagship if your app runs on Workers; pick Flagger.gg when agents ship your Go or Node code.
Updated
What Cloudflare Flagship is
Cloudflare announced Flagship on April 17, 2026 (Cloudflare's blog) and opened a public beta on May 26, 2026 (changelog). It's built on Workers, Durable Objects and KV. A Worker with a Flagship binding evaluates flags from config at the edge with no outbound HTTP call. Its official SDKs are OpenFeature providers for TypeScript, Python and Go; the Go SDK "evaluates flags over HTTP and does not support the Cloudflare Workers binding" (Go SDK, SDKs). Facts checked November 3, 2026, from Cloudflare's own docs.
Side by side
| Cloudflare Flagship | Flagger.gg | |
|---|---|---|
| Status | Public beta (May 2026) | Open sign-up; built from the flag system that runs Sandboxer and Transformer in production |
| Where checks run | In Workers via the binding, at the edge; Go and Python SDKs over HTTP, with optional caching | In memory in your Go or Node app; no network call per check |
| Change propagation | Up to 30 seconds globally (concepts) | Pushed over a stream within a second; 5-second polling if the stream drops |
| SDKs | OpenFeature providers: TypeScript (Workers, Node.js, browser), Python, Go | Go and Node; other SDKs In development |
| Targeting | Ordered rules with 13 operators, nested AND/OR groups, boolean, string, number and JSON variants (targeting) | Five states (off, admins, targets, percent, on); users, verified emails and workspaces; richer targeting In development |
| Percentage rollouts | Consistent hashing on a configurable attribute; A/B/n splits (rollouts) | Sticky bucket from sha256(key:userId), with shared test vectors in both SDKs and the service |
| Kill switch | Disabling a flag serves its default variation (Wrangler commands) | flagger kill, the flag_kill MCP tool or the console; always allowed, even on protected flags |
| History | Create, update and delete events per flag (wrangler flagship flags changelog) | Org audit log with actor, agent token, run, note, before and after, filterable by run |
| CLI and tokens | Wrangler commands with --json output; account-wide or app-scoped API tokens (API tokens) | flagger CLI with --json everywhere; agent tokens scoped to one project, chosen environments and actions, 90 days at most |
| Agent access | Wrangler and the REST API, which agents can call | MCP server (hosted at mcp.flagger.gg, or flagger mcp) with 11 tools listed by token scope, a note on every agent write, no approve tool |
Where Flagship is stronger
- Apps on Workers. The binding reads config from KV in the same Cloudflare location that handles the request, so a Worker needs no SDK fetch and no extra service.
- OpenFeature. Its SDKs are OpenFeature providers, so switching from another provider changes only the setup, not your call sites.
- Richer rules and variants. Thirteen operators, nested conditions, multi-variant flags with string, number or JSON values, and A/B/n splits.
- More languages. TypeScript, Python and Go today, plus a browser provider (which Cloudflare doesn't yet recommend for public-facing apps, since it needs an API token in client code).
Where Flagger.gg fits better
- Servers outside Workers. Flagger.gg's Go and Node SDKs check flags in memory from a streamed ruleset, with a disk cache for restarts during an outage, so no check waits on the network.
- AI agents ship your code. Scoped agent tokens, an MCP server whose tools follow the token's actions, a required note and an optional run id on every agent write, and protected flags agents can only kill.
- People stay in charge of wide changes. With approvals on, agents can roll out up to a cap in production (10% by default) and anything wider becomes a request a person approves; there's no approve tool.
Flagger.gg isn't the Flux/CNCF Flagger, a Kubernetes operator; it's the hosted flag service at flagger.gg.
FAQ
What is Cloudflare Flagship?
Cloudflare's feature flag service, in public beta since May 2026. It's built on OpenFeature and evaluates flags inside Workers from config stored at the edge.
Can I use Cloudflare Flagship outside Workers?
Yes. Its TypeScript, Python and Go SDKs work in other runtimes, but outside the Workers binding they evaluate over HTTP, with optional caching.
Is there a Cloudflare Flagship alternative for Go or Node servers?
Flagger.gg's Go and Node SDKs evaluate every check in memory, with changes streamed within a second. LaunchDarkly, Unleash and Flagsmith are other options.
Which one works better with AI coding agents?
Flagger.gg is built for it: an MCP server, a JSON CLI, agent tokens scoped to a project, environments and actions, and an audit log of each agent run. Flagship's docs describe Wrangler and a REST API, which agents can also call.
Ship your next change behind a flag.
Sign up, add an SDK key to your app and give your agent a token.