In one line: Cloudflare bundles DNS / CDN / WAF / DDoS protection / edge compute / tunnels on top of a global Anycast network. The free tier is more than enough for most personal sites, making it the best-value edge stack for small projects.
What it is#
Your domain's NS points to Cloudflare
↓
Cloudflare gives you:
- Authoritative DNS (HA, low-latency)
- HTTPS at the edge (auto TLS, HTTP/3)
- CDN cache
- WAF / Bot management / DDoS
- Workers (edge JS / WASM)
- Tunnel (expose internal services without opening ports)
- R2 (S3-compatible object storage)
300+ PoPs worldwide — the IP is always the one closest to your user.
Analogy#
Cloudflare is a global retail manager for your website: it opens shops in every city (CDN), hires guards (DDoS / WAF), can process products on-site in each shop (Workers), and even gives you temporary corridors to ship goods from your warehouse (your private network) without opening loading docks (Tunnel).
Key concepts#
How it works#
Mark a DNS record "proxied" and Cloudflare takes over the traffic.
Practical notes#
- Cache Everything: by default Cloudflare only caches static extensions; cache HTML via Cache Rules / Configuration Rules.
- TLS mode = Full (strict): origin must have a valid cert.
Flexibleis plaintext-to-origin — never use. - Tunnel is the killer feature: home / corp / NAS — no public IP, no port-forwarding; the daemon dials outbound to Cloudflare and exposes services.
- WAF / Rate Limiting: even the free tier supports a few rules; combine with Bot Fight Mode.
- Workers isn't Cloudflare-exclusive syntax: standard
fetch/Response; develop locally with wrangler, deploy with one command. - Don't treat it as the only line of defense. If your origin IP leaks (e.g. via misconfigured
X-Real-IP), DDoS can bypass Cloudflare. Allowlist Cloudflare IP ranges in the origin firewall.
Easy confusions#
Trivial setup — **value scales with audience**.
Full control — **DDoS resilience is on you**.