Sample on our own property: this is an internal demo, not a customer engagement.

Static FAQ site: Netlify-style setup to Cloudflare Workers

Run date: 2026-10-16

What we did

In an internal demo, we converted a static FAQ site from a simulated Netlify-style setup to Cloudflare Workers and ran it live on a test host with search indexing blocked.

Result

• Rollbacks performed: 3, all live
• Median time to roll back to the previous deployed version: 2.36 seconds
• Range: 2.19 to 2.49 seconds

"Rollback time" here means the time to return the site to its previously deployed version. It relates to the recovery time objective (RTO), the maximum downtime a team plans to tolerate. These numbers describe this one demo only; they are not a promise about any other site.

Method (general)

• The site's files are served as static assets on Cloudflare Workers.
• Every deploy creates a new Worker version, so earlier versions stay available.
• Rollbacks use wrangler rollback to return to the previous deployed version.

Logging and privacy

Every run is logged with the commit, timestamps, and request IDs. Raw logs containing visitor data are never published.

Want this for your site?

See our Cloudflare migration audit, or book it on Contra instead.