Cloud and infrastructure

Cloudflare

A global edge network doing DNS, caching, TLS and denial-of-service protection, and increasingly a place to run code close to the user.

When we reach for it

Public sites with an international audience, and any origin that should not be exposed directly to the internet. The performance improvement from getting caching right is usually the cheapest one available.

When we would argue against it

Putting the edge in front of an application whose own response times are the problem hides the symptom and leaves the cause. We measure the origin first.

What it looks like in delivery

Cache rules written deliberately rather than left at defaults, and the origin locked down so it can only be reached through the edge — otherwise the protection is optional and attackers know it.

Where this appears on the site

Nothing on this site names it yet

We work in Cloudflare, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.

Working in Cloudflare?

Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.