blog.cloudflare.com 22 Sept 2026, 13:00 UTC

Cloudflare Gives Every Git Branch Its Own Isolated Worker Preview

Cloudflare Gives Every Git Branch Its Own Isolated Worker Preview
CyberSIXT Evidence Panel Source marked as original reporting

CLOUDFLARE has launched Worker Previews, giving each Git branch an isolated, production-like environment for testing Cloudflare Workers before changes are merged. Developers can create a Preview with `npx wrangler preview`, or have one created automatically through Workers Builds. Each Preview has its own stable URL, code, configuration, variables, secrets, bindings and observability data, while custom domains can support production-like cookies, OAuth redirects, authentication and CORS behaviour.

The system also isolates stateful resources. Cloudflare says every Preview automatically receives a separate Durable Objects namespace and Container application, helping contain failed migrations, schema changes and test data to the relevant branch rather than affecting production or other Previews. Developers and automated agents can send requests to the Preview, inspect logs, errors, metrics and traces, and use Browser Run to test user journeys, capture screenshots or record sessions. Previews can also be protected with Cloudflare Access.

Cloudflare says the feature is already used internally, including for testing CloudflareOS workflows involving OAuth, permissions and approval flows, and has been adopted by customers including IKEA, Supermemory and Ramp. It distinguishes Worker Previews from existing Version URLs, which target specific Worker versions but do not provide isolated resources. Current limitations include service bindings still calling production deployments, and the lack of fully isolated Queue consumers and Workflows. Cloudflare says it is working on multi-Worker previews and longer-lived environments for staging and QA.

View full article

Article by CyberSIXT