Cloudflare ships an official Rust SDK for Flagship feature flags
The cloudflare-flagship crate adds an OpenFeature provider for async Rust services, with local evaluation and caching so flags do not need a network call per check.
Cloudflare published an official Rust SDK for Flagship, its feature-flag service, on 10 November. The cloudflare-flagship crate ships a direct client plus an OpenFeature provider, so an async Rust server can evaluate flags with the same targeting rules and percentage rollouts as Flagship’s existing JavaScript and other SDKs. It needs Rust 1.88 or later and a Tokio runtime.
cargo add cloudflare-flagshipBy default the provider evaluates flags over HTTP. Turning on local evaluation downloads flag definitions and checks them in-process instead, with periodic refresh and an optional fixed-TTL cache, so a hot path does not need a network round trip per check.
Why it matters: Flagship only reached public beta in May, and until now Rust services had to hand-roll HTTP calls or lean on the generic OpenFeature spec with no official backing. A supported crate with local evaluation makes Flagship a realistic option for Rust backends that can’t afford a network call on every flag read.