The architecture: your site served close to whoever is reading it
A headless stack deployed on Cloudflare does three things at once: it answers each visitor from near wherever they are, it keeps pages small enough to load on a bad connection, and it leaves no single server that can fall over and take you with it. South Africa shows all three at their sharpest: expensive data, a long round trip to overseas servers, and a grid you cannot count on, which is why the examples below are local. The architecture is not: it does the same job for a business in London or Lagos.
What that solves, concretely
-
Your site is served from near whoever is reading it
Ordinary hosting puts your website on one server in one place, and every visitor pays the distance between themselves and that machine. You feel it as the pause before a page appears. We replicate our sites across Cloudflare's whole network instead, so a visitor is answered from wherever is closest to them. South Africa is the sharpest example: a site on a server in Europe makes a round trip of many thousands of kilometres, while Cloudflare runs equipment in Johannesburg, Cape Town and Durban, so a visitor in Durban is answered from Durban. The same mechanism answers a visitor in Manchester from Manchester.
-
Small pages respect whatever the visitor is paying for data
Because we hand-code sites as pre-built pages rather than shipping a page builder's machinery, the pages are a fraction of the usual size. That is speed on any connection, and it matters most exactly where connections are worst. South African mobile data is not cheap and a large share of your visitors are on it, but the same is true of a patchy signal in rural Wales or a commuter train anywhere. Nobody has ever left a site because it loaded too quickly.
-
There is no single machine whose bad day becomes your outage
No single server has to be awake for your site to work. The pages are already built and copied across Cloudflare's network, so there is no box in one office or one data centre that can take you offline by losing power or falling over. In South Africa that has an obvious name: stage six in your suburb does not reach your website. Everywhere else it is the data centre outage you never hear about, because it never became your problem.
-
The headless part means the site stays this fast
Your content lives separately from the code that presents it, what the industry calls headless architecture. Editing content does not mean loading a heavy platform in front of every visitor; the site stays pre-built, tiny and fast, and the same content can later feed an app or anything else without a rebuild.
-
Serious machinery, without serious hosting bills
The same network also gives us databases, file storage and small pieces of server logic at the edge when a project needs them. The Manor Gardens community site runs its listings and images on exactly this. And because serving pre-built pages costs Cloudflare very little, it costs you very little: hosting is not a place we make margin.
Not a theory. It's how our own work ships
Every site on our work page runs on this stack: hand-coded, headless, deployed to Cloudflare's edge. The Manor Gardens community site goes further and runs its database and image storage there too. This page you are reading is served the same way, from the same city you are probably reading it in.
See the work ↗Common questions
Where is my site actually hosted?
It is served from South Africa, which is the part that matters for speed. Your pages are replicated across Cloudflare's whole network, including its South African locations in Johannesburg, Cape Town and Durban, so local visitors are answered locally, and an overseas visitor is answered from wherever is closest to them.
I am not in South Africa. Does any of this still apply?
All of it. Cloudflare's network is global, so the same replication that answers a Durban visitor from Durban answers a Toronto visitor from Toronto. We work remotely as a matter of course and take card payments from anywhere, so where you are changes nothing about the build. And on load-shedding specifically: the site does not live on one machine that can lose power, so a grid failure takes your office offline, never your website.
Does this cost more than normal hosting?
It usually costs less. Serving pre-built pages is cheap, and Cloudflare's pricing reflects that. We pass that through rather than marking hosting up. The build is what you pay us for, not the electricity behind it.
Is Cloudflare only for big companies?
The network was built for the biggest sites on the internet, but it serves a forty-product shop exactly the same way. That is rather the point: a small business in Durban or Dorset gets the same infrastructure as a multinational, without a multinational's hosting bill.
Want a site that's fast from here?
Tell us briefly what you're building. We reply directly, with no account manager in between.