JSON content. Custom edit panels. Pre‑rendered HTML on Cloudflare's edge. Three hundred cities. Zero hosting bills.2 Built for everyone who's done renting their website from a plugin economy.
{
"page": "home",
"hero": {
"headline": "The Electric Age",
"sub": "40 years of rock,
in one room.",
"cta": "Buy tickets →"
},
"tour": [
{ "city": "Belfast",
"date": "2026-06-12" },
{ "city": "Dublin",
"date": "2026-06-19" }
],
"published": true,
"updated": "2026-05-16"
}
40 years of rock, in one room. Four-piece touring band, covers Alice in Chains through Pink Floyd.
WordPress was the right answer in 2009.3 It's the wrong answer in 2026 — not because the core got worse, but because everything bolted on around it got expensive, fragile, and someone else's problem.
Ask any agency why your site is on WordPress and you'll get the same answer dressed up in seven different ways. The honest one is: their next hire knows WordPress. Their plugin licences renew. Their content shape is locked to The Post.
So every brochure site, every band page, every regional law firm — same five-page WP install. Same fourteen plugins. Same £840 a year disappearing into a maintenance contract nobody can quite itemise.
None of this is your fault. It's what the supply side chose. We're trying to choose differently.
Typical 30-page brochure site. Costs vary; the direction doesn't.
You edit in a panel as friendly as WP. It writes JSON to your Git repo. A build turns it into HTML. Cloudflare serves it from the closest edge to whoever asked. Done.
Custom-built for your content shape — pages, products, posts, tour dates, whatever. Reads and writes JSON. No PHP behind it. Your team logs in, types, hits commit.
Every save is a commit. Every commit is a version. Roll back to last Tuesday's headline in two clicks. The history is yours — not buried in a hosted database somewhere.
Cloudflare Pages takes the build and replicates it to 300 cities. No origin server. No PHP. No "please wait while the database catches up". 38ms TTFB, anywhere.
The reason people stay on WordPress is editing. So we built editing. A custom panel, shaped to your content. Your team uses it the same way they used WP — minus the 27 plugins.4
40 years of rock, in one room. Four-piece touring band, covers Alice in Chains through Pink Floyd.
Claude generated something. v0 generated something. Your designer sent you a 2,400-line single-file experiment. A one-off campaign landing. An archive of a thing that mattered.
You don't want to learn Vercel for it. You don't want to deal with Netlify CLI for it. You don't want it living on a Notion link that breaks next Tuesday.
Drag the file in. We give it a URL. We keep it there.
Cloudflare Pages is free. GitHub is free. Static HTML serves itself. We charge exactly £0/mo for hosting and we mean it. If we charged for it, we'd be the same line item we're trying to get you off.
Since 1998, in Belfast. We've spent twenty-eight years building sites that load in under a second — first because dial-up forced it, then because we couldn't unlearn the habit.
hosting.io is the platform we run our own client work on. We're opening it up because the alternative — watching another two thousand SMEs sleep-walk into another £840/yr WP maintenance contract — is harder to stomach every year.
Rebuilds for businesses stuck on WordPress. Custom editors, JSON content, static HTML on the edge. Twenty-eight years of building things on the web. We still pick up the phone.