API Security: What 50 Million Requests Actually Cost
50M req/mo: $0 vs $39 vs $3,000 the number that matters here
By Stan K.
At 50 million requests a month, protecting the same API costs $0 on Cloudflare Free, $39 on AWS WAF, about $89 with Bot Control — and $3,000/mo if you reach for Shield Advanced. The verified math, plus the CAPTCHA that costs 667× the request it guards.
API security pricing comes in two religions. Cloudflare sells flat plans — you pay for features (rules, regex, windows), and requests are unmetered. AWS sells a meter — every request, every rule, every CAPTCHA has a unit price. Same API, same traffic, radically different invoices. To make the religions comparable we ran both at 50 million requests a month, the volume where an API stops being a demo. Every number below is a verified official price, checked 2026-11-13 — nothing is estimated.
The same traffic, four different bills
| Stack | The bill at 50M requests/month |
|---|---|
| Cloudflare Free | $0 — no per-request billing for WAF or rate limiting |
| Cloudflare Pro | $20 flat (billed annually; $25 monthly) |
| AWS WAF, 4 rules | $5 web ACL + 4 × $1 rules + 50 × $0.60/1M = $39 |
| AWS WAF + Bot Control | the $39 meter + $10/mo per ACL + 40M × $1/1M = ≈$89 |
| AWS Shield Advanced | $3,000/mo + 1-year commitment, before its dependents |
The AWS column is not our invention — four rules is the pricing page’s own example case. The Cloudflare column is the whole point of the flat religion: the plan price is the price, at 50M or at 500M. What Free actually includes: the Free Managed Ruleset (high-impact rules), 5 custom rules, 1 rate-limiting rule, Turnstile, AI-bot blocking, and unmetered DDoS absorption on layers 3, 4 and 7. Pro’s $20 adds the full Cloudflare Managed Ruleset, the OWASP Core Ruleset, a second rate rule and 1-minute counting windows.
Bot Control deserves an honesty note: it hides free allowances. The first 10M requests a month on Common are free ($1/1M after), the first 1M on Targeted are free ($10/1M after) — at light traffic you pay only the $10 base. Our 50M arithmetic (40M billable) is the volume-sensitive way to read it.
The CAPTCHA that costs 667 times the request it guards
667×one CAPTCHA attempt versus the request it guards
AWS WAF CAPTCHA bills $0.40 per 1,000 attempts — $4.00 per 10,000 (the pricing page computes it itself, Case G). A plain request at $0.60/1M bills ≈$0.0000006; one CAPTCHA attempt ≈$0.0004. That is 667 ordinary requests’ worth of bill for one challenge. Old articles quoting “$0.40 per 10K” are 10× understated.
The consequence is architectural, not cosmetic: a site-wide CAPTCHA action turns your security bill into a function of your attackers’ enthusiasm. Challenges belong on the few endpoints that matter, never on the front door.
When the meter is worth it
The AWS meter buys things Cloudflare’s self-serve plans genuinely don’t sell: Bot Control’s Common and Targeted detection tiers, per-rule granularity at $1 each, and integration with everything else AWS already meters around your API. Cloudflare’s ladder only moves when features force it — regex arrives at Business ($200/mo billed annually), and so do non-IP rate-limiting counting characteristics (headers, cookies).
Shield Advanced’s $3,000/mo is a different product entirely: L7 DDoS response plus cost protection — the credits that repay attack-driven scaling spikes, which exist nowhere else. It includes AWS WAF up to 1,500 WCUs and 50B requests/month. But the fine print bills separately: a 1-year commitment per payer account, a paid Business or Enterprise Support plan, data-transfer-out fees (CloudFront at $0.025/GB for the first 100TB, tiering down to $0.01), and any WCU above 1,500 billed fully.
For a working API with ordinary traffic, the real shortlist is $0 vs $20 vs $39–89 — the same order of magnitude until CAPTCHAs or Shield enter. The full tables behind this math (rate limiting, DDoS, the quote-only vendors) are in the API Security hub, and the same reference-volume method applied to data scraping is in The Real Cost of Scraping.