Miron Blog When you make a website, you have it — but a website that only lives on your own computer is like a letter you wrote and left in your desk drawer. For anyone else to read it, it has to be delivered to them. Cloudflare is, more than anything, a delivery service for websites.
But to feel why it matters, it helps to picture how this normally works, and how much quiet difficulty it spares you.
Where a website actually “lives”
Imagine you’ve baked something and you want people all over the world to taste it. The old way: you keep the one and only cake in your kitchen. Everyone who wants a slice has to travel to your kitchen, wait while you cut it, and travel home again. Someone next door gets their slice quickly. Someone on the other side of the planet waits a very long time — and if too many people show up at once, your one small kitchen can’t keep up, and the whole thing slows to a crawl.
A website works the same way. It lives on a server — really just a computer, sitting somewhere in the world, that hands out copies of your pages to whoever asks. If that computer is in Germany and your reader is in Australia, every click has to travel all the way to Germany and back. Far away means slow.
So what is a “server,” really?
A server is not a special or mysterious machine. It’s an ordinary computer whose whole job is to sit there, always switched on, waiting for requests — “please send me that page” — and answering them. Your laptop could be a server. The only difference is that a real server is kept running day and night in a building designed for it, with reliable power and a fat internet connection, so it never goes to sleep and is always ready to answer.
Cloudflare keeps a copy near everyone
Now imagine instead that, the moment your cake is ready, an identical fresh copy quietly appears in a kitchen in every major city — Tokyo, São Paulo, Berlin, Mumbai. Now whoever wants a slice just walks to the nearest kitchen. Nobody travels far. Nobody waits.
That is the core of what Cloudflare does. It has computers in hundreds of cities, and it keeps a copy of your website in all of them. When someone visits, they’re served from the city closest to them. A reader in Australia is answered from Australia; a reader in Germany, from Germany. The page arrives almost instantly, anywhere on Earth.
Picture a reader far from where your site lives, and watch the request actually travel. Flip between the two and press Send the request: with one faraway home, every click crosses the world and back; with a copy in every city, the same reader is answered from next door — and you can see how much shorter that journey is.
your request hops clear across the world to the one server — and all the way back
The words people use for this: “edge,” “CDN,” “anycast”
You’ll hear three bits of jargon for the idea you just understood — and now that you have the idea, the words are easy.
- The edge — those hundreds of nearby computers, out at the “edges” of the network, close to real people, rather than one machine in the middle.
- CDN (Content Delivery Network) — the whole arrangement of keeping copies spread out so each visitor is served from nearby. That’s all the letters mean.
- Anycast — the clever trick that automatically routes each visitor to their nearest copy, without them or you having to choose. You ask for the website once, and the network quietly hands you to the closest kitchen.
You deploy once; it spreads everywhere
Here’s the part that feels almost too easy. You don’t set up those hundreds of computers. You hand your website to Cloudflare once — a single command — and Cloudflare copies it out to every city for you, in seconds. People call this little program a Worker, because it’s a small worker that runs your site out at every location. You wrote it once; now it works everywhere at the same time.
And because you can register your website’s name (its domain, like miron.blog) right
there in the same place, the whole path — from “I have a website” to “anyone in the world
can visit it, fast” — can take minutes, not days.
The hard, invisible work it does for you
This is the quiet gift, and it’s worth slowing down on, because it’s the part you’d otherwise spend months learning.
Running a fast, safe website by hand means wrestling with a long list of deeply technical things: squeezing pages smaller so they travel faster, speaking the newest and quickest languages browsers understand, turning away the endless robots that probe every site looking for weakness, and keeping every visitor’s connection private and secure. Each one of those is a craft in itself. People spend years getting good at them.
Cloudflare does all of it for you, automatically, without you ever learning their names. You get a website that is fast, modern, and safe — and you simply never had to know how.
For the curious: the actual things it handles silently
If you ever hear these terms, this is them — and the point is precisely that you don’t need to understand them to benefit from them:
- Compression (Brotli, zstd) — shrinking pages so they travel faster, like vacuum-packing before shipping.
- Modern delivery protocols (HTTP/2, HTTP/3, QUIC, 0-RTT) — newer, faster ways for your reader’s browser and the server to talk, cutting out wasted back-and-forth.
- Security (HTTPS) — locking each connection so what passes between site and visitor can’t be read or tampered with by anyone in between. It’s why the little padlock shows in the address bar.
- Bot filtering — recognising and turning away the swarms of automated programs that constantly poke at every website, so the real humans get through smoothly.
The reason this matters: the author of this blog once spent a whole year hand-tuning a server to do a fraction of this. Cloudflare gives it to you for free, on day one, as a side effect of just being there.
Hands-on: how this very page got online
If you’re the kind of curious where you’d like to actually do it — here is the whole path that took this blog from “a folder on a laptop” to “a website anyone in the world can open,” start to finish. None of it is hard. It’s mostly waiting for things to finish, and each step is just one short instruction.
Walk me through it, step by step
1. Claim a name for your site. This name is your domain — miron.blog,
your-name.com, whatever you like. You rent it (a few dollars a year) right inside the
Cloudflare dashboard, in the same place everything else lives. A minute of typing, and
the name is yours.
2. Build the site on your own computer first. Nothing is public yet. You make your pages locally and look at them in your own browser, exactly as visitors eventually will. This is the safe sandbox: you can change anything, break anything, and no one sees it. (The site itself is built with Astro — that’s its own story, with its own explainer.)
3. Keep a safety net with Git. Before sending anything anywhere, you save a snapshot of your work with Git — think of it as a perfect undo button that remembers every version, so you can always step back if something goes wrong. (Also its own explainer — it’s friendlier than its reputation.)
4. Send it to Cloudflare — the “deploy.” When you’re happy, you run a single command that hands your finished site to Cloudflare. This is the deploy. It looks like this:
npm run deployThat’s the whole thing. You press Enter, wait a few seconds while it works, and Cloudflare copies your site out to all those cities around the world. (If you’d like to see that you’re connected to Cloudflare before you ever deploy anything, there’s a gentle, harmless command that just says hello and tells you who you’re signed in as — nothing is changed, nothing is sent:
npx wrangler whoamiIt simply prints your account name back at you. A nice first thing to try, just to watch a command do something real and safe.)
5. Point your name at your site. You tell Cloudflare “when someone types my domain, show them this site.” A couple of clicks. And that’s it — your website is live, fast, and secure, reachable by anyone, anywhere.
The remarkable part: there was no moment where you had to rent a server, configure it, secure it, or keep it running. You went from a folder on your laptop to a worldwide website, and the hardest thing you did was choose a name.
So, in one breath
Cloudflare is the friend who takes your finished website and makes sure it reaches everyone, everywhere, quickly and safely — keeping copies close to your readers, and shouldering all the invisible difficulty of modern web delivery so that you’re free to think only about what you actually want to say.