How This Site Is Built, and Why It Costs Almost Nothing to Run

For years my default answer to "what should our website run on?" was WordPress. It is still the right answer for some businesses. But when I rebuilt this site I wanted to find out how far a much lighter approach could go, and whether it would suit the B2B clients I work with.

The short version

The site is a set of plain web pages, built ahead of time and served from Cloudflare's network. There is no database, no plugins to update and no server to patch. Hosting costs nothing at this size.

• Astro turns templates and content into finished pages.
• GitHub stores every version of the site, so any change can be rolled back.
• Cloudflare publishes a new version a couple of minutes after each change.
• Claude did most of the building, working from my briefs and corrections.

What changes for the business

Speed is the obvious win. Pages are small and arrive from a server close to the visitor, which matters for search rankings and for anyone reading on a phone on a site visit.

The less obvious win is control. Structured data, redirects, page titles and accessibility are all set deliberately rather than left to a theme or plugin. Search engines and AI search tools get a clear, consistent picture of who the business is and what it does.

Editing without code

The worry with a site like this is that every change needs a developer. That is no longer true. A simple editor sits at /keystatic, where named sections of the site, including this blog, can be edited and saved. Saving publishes the change.

Is it right for everyone?

No. A large site with many editors, e-commerce or complex permissions may still be better on a traditional platform. For a focused B2B site, landing pages or a regional version of an existing site, it is fast, cheap and easy to look after.

If you are weighing up a rebuild, I am happy to talk it through.