Cloudflare deployment

Fabric Experiments can use Cloudflare in the same style as Fabric Harness and Fabric Platform for the docs site, and for product edge workers.

Docs site

pnpm run docs:deploy

The docs worker serves static assets from dist/cloudflare-docs at:

https://experiments.fabric.pro

Product workers

Create resources:

cd cloudflare/manifest-worker
wrangler kv:namespace create fx_manifests --env staging
wrangler secret put HMAC_SECRET --env staging
wrangler deploy --env staging

cd ../exposure-worker
wrangler r2 bucket create fx-exposures-staging
wrangler queues create fabric-experiments-telemetry-staging
wrangler queues create fabric-experiments-telemetry-staging-dlq
wrangler deploy --env staging

cd ../audit-export-worker
wrangler r2 bucket create fx-audit-exports-staging
wrangler secret put WORKER_API_TOKEN --env staging
wrangler deploy --env staging

Update each wrangler.toml with staging bindings and route names before deploy.

Tenant-isolation setting

Do not configure DEFAULT_TENANT on a shared multi-tenant worker. It enables legacy unscoped manifest and telemetry URLs and intentionally sends those requests to one organization. A missing value fails closed; an incorrect value can cross-route delivery or telemetry. Use /{tenantId}/manifest and /{tenantId}/v1/{exposure|conversion} in production. Reserve the fallback for a dedicated single-tenant worker whose binding is reviewed and tested.