Cloudflare's network
Cloudflare's network is a set of hundreds of data centres around the world that can hold a copy of your site and serve it from whichever one is closest to the visitor.
Most small business websites live on one computer in one building. You rent a slice of it, someone else keeps it running, and every visitor from anywhere in the world has to reach that one building to see your page. If it is slow, everyone waits. If it is down, everyone is locked out.
Cloudflare’s network is the other way of doing it. Cloudflare runs data centres in hundreds of cities. A site built to run on that network is copied to all of them. When someone in Kamloops opens your site, they get it from a nearby data centre. Someone in Toronto gets it from a different one. Nobody is waiting on a single machine across the country.
The same network also handles the plumbing around the site: DNS, certificates, the filtering that keeps junk traffic out, and the mail routing that gets a contact-form enquiry into your inbox. It is one company, one account, one place to look.
Why it matters to you
Speed is the obvious part. A page served from a data centre near the visitor loads faster than one served from a rented server three time zones away, and that shows up in how Google ranks the site and in how many people stick around long enough to call.
The less obvious part is that there is no single server to break. When I rebuild a site that was compromised through a plugin on a shared server, moving it onto Cloudflare’s network removes the server entirely. There is no box to patch, no operating system to update, no login to guess. The site is a set of files that Cloudflare hands out.
Cost is the third part. The free tier covers a practice or a trade business comfortably. When something does need a paid feature, it is billed by Cloudflare at their own rate, direct to you, with nothing added by me. I write more about that under costs at cost.
How I set it up
I build the site as a static site: every page is generated ahead of time and pushed to Cloudflare as plain files. There is no database behind the pages and no code running when a visitor arrives. The files are copied across the network automatically the moment I deploy.
The account is yours, not mine. Your domain’s DNS lives in it, you hold super admin, and the billing runs on your card. If I am unavailable, nothing lapses and nobody has to chase me. That has been the arrangement on every site I have moved onto the network, whether it is a counselling practice, a rubbish removal company, or a public speaker.
What it looks like in practice
Day to day, you see nothing. The site is quick from anywhere. It stays up. Certificates renew themselves. When I push a change, it is live everywhere within a minute or so.
When you log in to the Cloudflare dashboard, you see your domain, a traffic graph, and a handful of settings. You do not need to touch any of it. It is there so that you can, and so that you can hand it to someone else if you ever need to. That is the difference between owning a site and renting one.
Questions I get about this
- Is Cloudflare's network the same thing as a web host?
- For the sites I build, yes. The site's files live on Cloudflare and are served from there. There is no separate server somewhere that Cloudflare sits in front of. For an older site on a rented server, Cloudflare can still sit in front as a shield, but the server is still doing the work.
- Do I have to pay Cloudflare a lot for this?
- No. The free tier covers most small businesses. Where a site needs paid features, the bill comes from Cloudflare directly, in your name, at their published rate. I do not mark it up.
- What happens if one of their data centres goes down?
- Traffic moves to the next nearest one. That is the point of having hundreds of them. A single rented server has no next one.
Want this set up properly for your business?
This is the kind of thing I build every week. Grab a time and we will talk through what fits.