# Cloudflare Flagship [[Cloudflare]] Flagship is a feature-flag service launched in public beta in May 2026, integrated natively with [[Cloudflare Workers]]. It exposes typed flags evaluated at the edge — boolean, string, JSON — with targeting rules (user attributes, percentage rollouts, regions, custom traits) and a UI for managing experiments. It positions against LaunchDarkly, GrowthBook, PostHog feature flags, and Cloudflare's own Workers-KV-as-feature-flag patterns. The pitch: native binding, single-digit-millisecond evaluation at the edge, no separate SaaS account, no flag-fetch latency. ## Why It Matters Most feature-flag products solve "how do I toggle without redeploying" but introduce a separate vendor, a separate SDK, a separate billing line, and a non-trivial latency budget. Flagship lives in the same place Workers code lives — same auth, same observability, same wrangler.jsonc. For Cloudflare-native apps this is the obvious default once it leaves beta. ## Core Capabilities - **Boolean, string, and JSON flags** with typed evaluation - **Targeting rules** by user attributes, region, traffic percentage - **A/B experiments** with consistent bucketing - **Edge evaluation** via Workers binding (no network hop) - **Audit log** of flag changes ## Common Use Cases - **Gradual rollouts** — 1% → 10% → 100% - **Kill switches** for risky features - **A/B tests** at the edge with no client-side flicker - **Per-tenant feature gating** in multi-tenant SaaS - **Replacing [[Cloudflare KV]]-as-flag-store** patterns ## References - Flagship beta announcement: https://developers.cloudflare.com/changelog/post/2026-05-26-public-beta/ - Documentation: https://developers.cloudflare.com/flagship/ ## Related - [[Cloudflare]] - [[Cloudflare Workers]] - [[Cloudflare KV]] - [[Wrangler]]