Cloudflare logo
Cloud

Cloudflare

Edge network for DNS, CDN, security and serverless. Cloudflare runs a global edge network that sits in front of websites and APIs, providing DNS, caching, DDoS protection, a web application firewall and Zero Trust access. It also offers developer services such as Workers for serverless code, R2 object storage and Workers AI for running models at the edge.

When it is the right choice

  • You want DNS, CDN and DDoS protection in front of your sites and APIs
  • You want to replace a VPN with identity-based access to internal tools
  • You need lightweight code or static sites served close to users
  • Not a full replacement for a cloud provider when you need large databases or heavy compute

How we use it

  • Manage DNS, WAF rules and caching with Terraform so changes are reviewed and versioned
  • Lock origin servers so they only accept traffic from Cloudflare
  • Put internal dashboards behind Cloudflare Access instead of a public login
  • Watch traffic, cache and security analytics and tune rules as patterns change
Works well with

Often used together

Questions

Cloudflare: frequently asked

Can Cloudflare be bypassed by attacking our server directly?

Yes, if the origin's IP is known and open to everyone. We restrict the origin to Cloudflare's IP ranges or use Cloudflare Tunnel so there is no public origin at all.

Should Cloudflare settings be managed in code?

Yes. Clicking in the dashboard is fine for tests, but managing zones and rules with Terraform gives you review, history and quick rollback.

Running Cloudflare, or deciding whether to? Tell us what you have; the first consultation is free.

Let's talk »