Features
- Edge evaluation: Flag rules evaluate at Cloudflare’s edge locations worldwide
- Ultra-low latency: Evaluation happens close to users, minimizing latency
- WebAssembly powered: Rust-based resolver compiled to WASM for performance
- Background sync: Flag rules sync with Confidence in the background
Deployment
The Cloudflare resolver is deployed using a Docker-based deployer that handles building and publishing the Worker to your Cloudflare account.Prerequisites
- Docker installed
- Cloudflare API token with Workers permissions
- Confidence client secret
Build the deployer
From the root of the confidence-resolver repository:Deploy to Cloudflare
Run the deployer with your credentials:- Cloudflare account ID from your API token
- Resolver state from Confidence CDN
- Existing deployment to avoid unnecessary re-deploys
Optional configuration
| Variable | Description |
|---|---|
CLOUDFLARE_ACCOUNT_ID | Required only if API token has access to multiple accounts |
CONFIDENCE_RESOLVER_STATE_URL | Custom resolver state URL (overrides CDN) |
CONFIDENCE_RESOLVER_ALLOWED_ORIGIN | Configure allowed origins for CORS |
FORCE_DEPLOY | Force re-deploy regardless of state changes |
NO_DEPLOY | Build only, skip deployment |
Limitations
- Sticky assignments: Not currently supported with the Cloudflare resolver. Flags with sticky assignment rules will return “flag not found”.

