Cloudflare WAF
Cloudflare, Inc. · api security · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-13
The $0 edge stack — unmetered WAF, rate limiting and L3/L4/L7 DDoS on every plan including Free; the price of the plan buys rules and windows, never requests.
#1 of 8 in Api Security
ToolScore breakdown — why 75/100
10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →
What it does well
- ▸$0 per request for WAF and rate limiting on every self-serve plan — 50M requests/month cost $0 on Free
- ▸"Unmetered and unlimited DDoS protection at layers 3, 4, and 7 to all customers on all plans and services" — Free included
- ▸The $0 bot stack is real: Bot Fight Mode, Block AI bots and AI Labyrinth at $0, plus Turnstile with 20 widgets per account
- ▸Every self-serve price is published ($20/$25 Pro, $200/$250 Business) and the docs confirm rate limiting rules carry no metered usage fees
- ▸The ladder is self-serve all the way: regex and 100 rules arrive at Business without talking to sales
Where it costs you
- ▸Free walls are hard: 5 custom rules, no regex (Business+), and 1 rate rule with IP-only counting in a 10-second window — Free cannot express "60 requests/minute"
- ▸Full Cloudflare Managed Ruleset + OWASP Core Ruleset are Pro+; Free gets the high-impact Free Managed Ruleset only
- ▸Super Bot Fight Mode is Pro/Business; Bot Management is an Enterprise add-on with no published price ("by your account team")
- ▸Unmetered DDoS protects proxied HTTP/HTTPS only — raw TCP/UDP needs Spectrum / Magic Transit (Enterprise)
Hidden traps — the stuff the pricing page doesn't say
The Free plan gets 1 rule, IP-only counting, and a 10-second counting period. 1-minute windows start at Pro, 10-minute at Business; non-IP counting characteristics (headers, cookies, JWT claims) are Business+ features.
You are protected "up to the layer on which your service operates" — raw TCP/UDP DDoS absorption requires Spectrum / Magic Transit, both Enterprise. If your API is not web-transport, the famous $0 does not apply to it.
Stripe and GitHub webhook senders carry no browser headers, so WAF false positives hit them first. The documented dial is the OWASP Core paranoia level (higher paranoia = more false positives) and Cloudflare's Browser Integrity Check docs themselves say "disable selectively". Route webhooks around managed rules — the breakage pattern is field analysis, not a documented failure.
The docs say the old product is "no longer available" and all rules were upgraded. Any article still billing Cloudflare rate limiting per 10K requests/month describes a product that no longer exists.
Know the limits before you pay: read the traps above, then decide with eyes open.
Visit official siteAffiliate link where available — never affects the score.
- official Cloudflare plans and prices (official, checked 2026-11-13) verified
- official Cloudflare custom rules — rule counts per plan, regex (official) verified
- official Cloudflare rate limiting — windows, characteristics, availability (official) verified
- official Cloudflare managed rules — Free Managed Ruleset vs Pro+ (official) verified
- official Cloudflare bots plans — Bot Fight Mode / Super / Bot Management (official) verified
- official Cloudflare DDoS — "unmetered and unlimited", L3/L4/L7 (official) verified
- official Turnstile plans — 20 widgets on Free (official) verified
- official Cloudflare Workers pricing — 100K requests/day free tier (official) verified
Data as of 2026-11-13. Prices and limits change monthly — report anything stale. How we verify: methodology.
Closest alternatives
The $0 rate limiter you own outright: a per-key leaky bucket in ten lines of config — no meter, no p
Pure pay-as-you-go with every cent published — $5/web ACL, $1/rule, $0.60/1M requests — and a meter
The DIY rate limiter's meter: $0.20 per 100K Redis commands PAYG, a real free tier (500K commands/mo
Cloudflare WAF review
In-depth analysis · last updated 2026-11-13
The $0 edge stack
Cloudflare's Free plan is a real security stack, not a trial: unmetered DDoS at layers 3, 4 and 7 — "to all customers on all plans and services" — the high-impact Free Managed Ruleset, 5 custom WAF rules, one rate limiting rule at $0 per request, Bot Fight Mode plus Block AI bots plus AI Labyrinth, and Turnstile with 20 widgets per account. At our reference volume of 50M requests/month, all of it costs $0, which is why it is the hub's value pick: the same traffic meters to $39–$89/mo on AWS WAF.
The plan ladder — money buys rules and windows, never requests
WAF and rate limiting are unmetered on every plan, so the ladder sells control, not capacity. Pro ($20/mo billed annually, $25 monthly) adds the full Cloudflare Managed Ruleset + OWASP Core Ruleset, Super Bot Fight Mode, 20 custom rules and 1-minute rate windows (2 rules). Business ($200/mo billed annually, $250 monthly) is where regex arrives, with 100 rules, 10-minute windows (5 rules) and non-IP counting characteristics — headers and cookies, not just addresses. In our hub Pro scores 77 and Business 76; this page leads with Free because Free is where the value is.
The honest limits of Free
The Free rate limiter cannot express "60 requests/minute": one rule, IP-only counting, a 10-second counting period — 1-minute windows start at Pro, 10-minute at Business. Regex waits for Business. Bot Management — the analytics tier above Block/Challenge — is an Enterprise add-on with no published price, quoted "by your account team". And the famous unmetered DDoS covers proxied HTTP/HTTPS only: you are protected "up to the layer on which your service operates", and raw TCP/UDP requires Spectrum or Magic Transit, both Enterprise. The legacy per-10K-requests rate limiter is retired — "no longer available", all rules upgraded.
How the pillars land
Price/Value 10: $0 at 50M with unmetered requests — nothing in this hub touches it. Request & rate limits 8: request volume is unmetered, but the Free walls (5 rules, no regex, 1 IP-only rule in 10 seconds) are real and the windows are the paid product. Latency & edge 7: a flood absorbed at the edge is a flood your server never sees — the qualitative edge argument; no latency numbers are published, so the pillar stays near neutral. Data handling 5 and Self-host/own WAF 5: nothing verifiable in this snapshot — it is a hosted edge, and the open-source exit from this hub is nginx, not Cloudflare. Feature set 9: WAF + rate limiting + unmetered L3/L4/L7 DDoS + a genuine $0 bot stack + Turnstile, docked only because the full managed rulesets and Bot Management sit above Free. Track record 9: the unmetered commitment is published policy on all plans, and the retired legacy product was upgraded rather than stranded. Ease of use 8: self-serve ladder, zero-config DDoS — our own site runs on three Cloudflare Free zones. Pricing transparency 9: every self-serve dollar is published and the docs confirm no metered usage fees; docked a point for the unpriced Enterprise add-on. Support & docs sits at the neutral 5 — nothing support-related was verifiable from the official pages in this snapshot.
Verdict — BEST VALUE, 75/100
For most public APIs, $0 is enough: proxied through Cloudflare Free you get unmetered DDoS on all three layers, the Free Managed Ruleset, 5 custom rules, 1 rate rule and Turnstile. Pay when you hit a hard Free wall — regex or 100 rules ($200/mo Business, self-serve), raw TCP/UDP DDoS (Spectrum / Magic Transit, Enterprise quote), or bot analytics beyond Block/Challenge (Bot Management, Enterprise quote). The meter at Cloudflare only starts when you need regex or Enterprise; AWS's starts with the first request.