Cloudflare

Cloudflare has become one of the most solid pillars of modern web infrastructure. Originally a simple CDN and anti-DDoS shield, it's now a complete ecosystem: fast reliable DNS, WAF (Web Application Firewall), static pages (Cloudflare Pages), serverless workers, Zero Trust, CrowdSec bouncer, and many other bricks. For an SMB, putting your site behind Cloudflare instantly offers three critical benefits: performance accelerated by the global CDN, protection against basic attacks, and observability of incoming requests.

• →FastlyMore expensive but finer on complex caching, often chosen by very large sites
• →BunnyCDN / KeyCDNMore economical on pure bandwidth, no complete ecosystem
• →AWS CloudFrontIf you're already 100% AWS, simpler native integration
• →French cloud CDN (Scaleway, OVH)If sovereignty is an absolute criterion, less wide coverage but guaranteed EU data

1. 01

   DNS migrated to Cloudflare first: it's the foundation of other services

2. 02

   Proxy mode (orange icon) enabled on public subdomains, disabled on internal subdomains (mail, SSH)

3. 03

   Cache rules adapted to content type (long static, short dynamic, uncached API)

4. 04

   Managed WAF enabled in defensive mode: start in log-only, switch to block after a week of observation

5. 05

   Cloudflare bouncer for CrowdSec: perimeter + runtime defense, complementary

• Is free Cloudflare enough for an SMB?

  Often yes. The Free plan includes unlimited global CDN, basic anti-DDoS, automatic SSL, fast DNS, some page rules. For most SMB sites, that's largely sufficient. The Pro plan ($25/month) adds managed WAF, image optimization, basic bot management, relevant for e-commerce sites or those with significant audience.
• Cloudflare or a competing CDN (Fastly, KeyCDN)?

  Cloudflare for nearly all SMB cases: best price/quality ratio (often free), integration simplicity, complete ecosystem. Fastly is more expensive but offers more finesse on complex caching. KeyCDN is more economical on pure bandwidth. For an SMB, Cloudflare remains the default without debate.
• Does Cloudflare really block attacks?

  Yes for the vast majority of common attacks (volumetric DDoS, automated scans, basic bots). For targeted application attacks (SQL injection, XSS on specific parameters), managed WAF helps but doesn't replace real application defense (secure code, CrowdSec in runtime). Defense in depth remains the rule.
• How much does Cloudflare deployment cost on an existing site?

  For a standard site with a domain name and single server, it's typically 1-2 hours of configuration. For more complex infrastructures (multi-region, various subdomains, outbound integrations), expect 1-2 days. The investment is almost always paid back by bandwidth savings and gained stability.
• And GDPR compliance?

  Cloudflare is GDPR compliant with a signed DPA and offers SCCs. European data centers are available ('Regional Services' option from Business plan to keep traffic in EU). For standard SMB cases, the default configuration is GDPR-acceptable with a mention in the privacy policy. For sensitive cases (health, very personal data), a specific legal review is recommended.