When a client asks “where does my site actually live?”, the answer matters more than it sounds. We deploy everything on Cloudflare — not because it is trendy, but because it changes three things that clients feel: speed, cost and reliability. Here is the honest version.
In short
- Your site runs on Cloudflare’s global edge — every visitor is served from the nearest city, not from one server.
- You get DDoS protection, TLS and caching included, not as paid add‑ons.
- Compute (Workers) starts instantly — no cold starts on dynamic pages.
- Storage (R2), key‑value (KV) and databases (D1) sit on the same network.
- Pricing is usage‑based and honest, and you own the account.
What Cloudflare actually is
Cloudflare started in 2009 as a CDN and security company. Today it is a full edge platform. “Edge” means the computation happens at data centres around the world, close to your users, instead of in a single origin region.
For us, that platform is three products working together:
- Workers — run back‑end code at the edge (our API routes, auth checks, personalisation).
- Pages / static assets — serve pre‑rendered HTML and assets from cache.
- R2, KV and D1 — durable storage and databases, close to the compute.
Read the full capability list on our Cloudflare hub page.
Why “the edge” matters
Imagine a server in Frankfurt and a customer in Sydney. Every request travels ~16,000 km and back — roughly a quarter of a second of pure physics before your code even runs. Now imagine 300+ Cloudflare locations, and the same customer is served from Sydney.
That is the difference between “fast enough” and “instant”. Search engines and, increasingly, AI assistants reward it. Users definitely do.
The capabilities we use every day
- Zero cold starts. Workers run in lightweight V8 isolates that start instantly, so a dynamic route responds like a static file.
- Security by default. DDoS mitigation, a WAF and TLS are part of the platform. We do not bolt them on. And because Workers run no PHP, whole classes of vulnerabilities never reach your site — we wrote a separate piece on why our sites don’t get hacked like PHP servers do.
- Caching that just works. Static assets get immutable, hashed URLs and are served from cache worldwide.
- Data at the edge. R2 stores files without egress fees; KV and D1 keep small data and SQL close to the user.
Cost and ownership
Traditional hosting charges you more as you grow and locks features behind tiers. Cloudflare’s model is usage‑based: you pay for what you use, and the free tier is genuinely generous. Crucially, the account is yours. If you ever move on, you take the domain, the DNS and the data with you. We design for that exit from day one.
This is part of a bigger principle: we assemble open, portable platforms instead of proprietary black boxes. It is the same reason we use Supabase for the backend side.
When Cloudflare is not the right fit
We are not dogmatic. If you have a heavy, stateful legacy application, or a workload that must run in a specific country for compliance, a traditional host or a regional cloud may be the better call. We will tell you that plainly. For most content sites, SaaS front‑ends and marketing sites, the edge wins.
Summary
Cloudflare gives us global speed, built‑in security and honest pricing — and it gives you control of your own infrastructure. That combination is why it is the first name on our platform slide, ahead of any framework. See the capabilities in detail, or how we apply them in web development.