The mental model
Traditional hosting: your website lives on a computer — one machine, in one building, in one city. Every visitor on earth connects to that machine. If it's slow, far away, overloaded or down, that's your website's day.
Cloudflare hosting: your website lives on a network. Your pages are distributed to Cloudflare's data centers — 330+ cities across 125+ countries — and every visitor is answered by whichever one is nearest. A visitor in Miami is served from Miami; one in Manchester, from Manchester. There is no “the server.”
The product that does this is called Cloudflare Pages: you give it your site's files, it puts them everywhere at once. (Its sibling, Workers, runs code the same way — that's how forms and dynamic pieces work without a server.)
What falls out of that design
Speed you don't tune
Pages are pre-built and served from next door — no CMS assembling the page per visit, no database round-trips, no cross-country hops. Modern protocol niceties (HTTP/3, Brotli compression, automatic SSL) are on by default rather than plugins you install. The speed isn't an optimization; it's the shape of the system.
Security by subtraction
The attacks that actually hit small-business sites need something to grab: a login page, a database, an out-of-date plugin. A static site on Pages has none of those — there's no origin server to break into, because there's no origin server. And the network absorbs DDoS traffic as part of the fabric (Cloudflare's mitigation is unmetered — they don't bill you for being attacked). The compliance certifications behind the infrastructure — SOC 2 Type II, ISO 27001 — are Cloudflare's, and the honest framing is that you inherit the benefit of them, not the credential itself.
Deploys you can undo
Every version of the site is kept. A change that shouldn't have shipped rolls back in one click, to any previous state. Combined with staging — every change viewable on a private URL first — the scary parts of touching a live website mostly stop being scary.
The honest limitations
This model is not for everything, and anyone who tells you otherwise is selling something.
- There's no CMS dashboard. The site is files, not a WordPress admin. That's the source of the speed and the security — and it means changes need either a developer or a service that includes them. (Our answer: you email the change to us, it gets done — that's the Managed tier's whole point.)
- Heavily dynamic applications need real engineering. Stores, portals, booking systems and logins absolutely can run on this stack — Workers exist for exactly that — but they're built, not installed. If your site is mostly an application, the fit depends on the build.
- Email doesn't live here. Cloudflare serves web traffic; your mail stays wherever it is. (Done right, a migration doesn't touch it — but “done right” is load-bearing; moving DNS around mail records is where amateur migrations go wrong.)
What a migration actually involves
The part that surprises people: moving to this stack usually means rebuilding, not transferring. A WordPress site can't be copy-pasted onto Pages — it gets rebuilt as pure HTML, CSS and JavaScript, pixel-for-pixel, and the WordPress layer simply ceases to exist. Done carefully, that's a feature, not a cost: the rebuild is where the plugins, the bloat and the attack surface all disappear. We've been doing exactly this since the platform matured — it's the standard path for every site we take on, we do it for free, and the old site stays live until the new one is proven, so the cutover involves no downtime.
What it costs
Cloudflare's own pricing for Pages starts at free — the infrastructure is startlingly cheap because serving pre-built files is startlingly cheap. The rebuild itself we do for free. What you pay a host like us for is everything around it and after it: DNS done without breaking your email, monitoring, staging discipline, content changes handled, and a person who answers. Our numbers are public: $120 a year, or $365 managed with content edits included.