We rebuilt brixio.io on Cloudflare Workers in 19 days.

The challenge

Brixio sells one thing: Cloudflare operations. Its own website ran on WordPress, with a Roots Sage theme and 54 custom blocks built on PHP templates. The contradiction was visible: advising organisations to move to the edge while running the corporate site on a PHP stack that has nothing to do with it.

The brief had four constraints, not one:

• Move to the edge and retire the PHP and plugin maintenance surface.
• Prove the stack at the right moment. EmDash, a CMS positioned as a serverless reimplementation of WordPress, had just shipped on Cloudflare. Running the corporate site on it was the most direct proof point available.
• Protect search visibility. A pivot toward a 100% Cloudflare positioning, in both classic search (SEO) and generative engines (GEO), could not come at the cost of existing rankings.
• Capture leads. The old site had no measurable acquisition loop into the CRM.

A full rebuild from a blank page would have risked the rankings. The approach had to preserve the existing site before changing it.

What Brixio deployed

Phase 1 · Mirror reconstruction

The first goal was a faithful mirror of the existing site, running on Cloudflare, with no SEO regression.

• The 54 WordPress blocks (ACF, rendered through Blade templates) were rebuilt as native Astro components, matching the original site visually and functionally. PHP templates cannot run on the edge, so the block library was reconstructed, not transplanted.
• Content was migrated by script: a WordPress export (WXR) plus custom field data, converted to the EmDash Portable Text content model and stored in D1.
• Media files were moved to R2, and legacy WordPress URLs were preserved and redirected through Worker middleware.

Phase 2 · Iteration

• Progressive redesign of the templates.
• Restructuring of the information architecture toward the 100% Cloudflare positioning.
• Update of all existing content.
• Writing and creation of the new pages.
• Connection of Turnstile (form bot protection) and the Zoho CRM lead capture loop.

Fast, and verified

The block reconstruction was assisted by AI, which is why it took hours rather than weeks. Speed was governed, not assumed. The work went through a systematic, detailed review of the code and the security posture before production: Brixio is ISO/IEC 27001:2022 certified and applies that framework across all its work. Every block and every entry point, forms and CRM API included, was reviewed.

Results

These are early signals, measured in the first month after launch and during a Google core update, so they remain in motion. They are already positive.