API Security, Priced at Real Request Volume
The metric here is not a feature list — it is what it costs to protect a product that already has traffic. Every option below is priced at 50M requests/month, the volume where an API stops being a demo: a WAF that bills per request, a rate limiter whose price doubles under replication, a CAPTCHA that costs ~667× the request it guards. Cloudflare’s self-serve plans charge $0 per request for WAF and rate limiting; AWS meters everything and adds surcharges per rule, per WCU and per CAPTCHA; Imperva, Akamai and Fastly publish no price at all. Every number comes from official pricing and docs pages checked on 2026-11-13 — where a vendor doesn’t publish, the cell stays “—” or says “Custom quote”.
WAF & bot protection — the sticker price versus the 50M-request bill
Two billing religions. Cloudflare sells flat plans — rules and regex move you up the ladder, requests are unmetered. AWS WAF is a pure meter: per ACL, per rule, per million requests, with inspection surcharges stacking on top. The last column runs the meter at our reference volume so the religions can be compared on money.
At the reference volume the unmetered WAF, rate limiting and DDoS cost $0 — the same traffic meters to $39–$89/mo on AWS WAF.
| Service | Price /mo | Custom rules | Regex | 50M req/mo costs | Score |
|---|---|---|---|---|---|
| | $0 | 5 | No | $0 — no per-request billing | 75/100 |
| | $20/mo billed annually $25/mo monthly | 20 | No — Business+ | $20 flat — WAF and rate limiting are unmetered | 77/100 |
| | $200/mo billed annually $250/mo monthly | 100 | Yes | $200 flat | 76/100 |
| | $5/web ACL + $1/rule + $0.60/1M requests | $1 per rule each | — | $5 + 4×$1 + 50×$0.60 = $39/mo (4 rules, AWS’s own example case) · +Bot Control $10 + 40M×$1 = $50 → ≈$89/mo | 68/100 |
| | Custom quote | 5 / 25 / 100 by tier | — | Custom quote | 44/100 |
| Imperva WAF Not one dollar figure on the official page — trial/demo only | Custom quote | — | — | Custom quote | 42/100 |
| | Custom quote | — | — | Custom quote | 41/100 |
“—” = not verified in our check (nothing found on official pages) — it does not mean “doesn’t exist”. Cloudflare’s pricing pages show no per-request charges for WAF/rate limiting on self-serve plans, and the docs confirm current rate limiting rules carry no metered usage fees. The AWS 50M column is arithmetic on the verified unit prices (4 rules = AWS’s own pricing-page example case); Fastly’s confirmed tier detail is the rule counts — Core 5 / Core Plus 25 / Total 100 custom rules, with Bot Management only in Total. Bot protection tiers moved to each provider’s review page (click the name) — Bot Fight Mode vs Super Bot Fight Mode vs Bot Management, AWS Bot Control’s free allowances, Imperva’s add-on quote. Scores are our editorial estimate (0–100) of value at 50M req/mo — price against protection and limits; pillars without a verified fact sit at the neutral 5, and the quote-only vendors carry transparency 1–1.5.
Rate limiting — free windows, $0.20/100K commands and the 10-second trap
The cheapest rate limiter is the one inside a WAF you already pay for — Cloudflare’s rules are $0 per request on every plan; the price is the window. The DIY route moves the meter to Redis (Upstash) or to nothing at all (nginx on your own box).
| Service | Pricing | Free tier | Windows & limits | Score |
|---|---|---|---|---|
| | $0 per request unmetered on every plan | 1 rule (IP-only counting, 10-second window) | Free: 1 rule, 10s · Pro: 2 rules, 1 min · Business: 5 rules, 10 min · Enterprise: 100 rules | 75/100 |
| | $0.60/1M requests a rate rule is a rule: +$1/mo | — | — | 68/100 |
| | $0.20 per 100K commands PAYG storage $0.25/GB (first 1 GB free) | 500K commands/mo + 250 MB | Global replication: 1 primary + 1 read region doubles writes → $0.40/100K | 66/100 |
| | $0 software you pay the VPS | — | Per-key leaky bucket: “limit the request processing rate per a defined key… excessive requests are terminated” | 75/100 |
Cloudflare’s rate limiting counts by IP only on Free; every counting characteristic other than IP (headers, cookies, JWT claims) is a Business+ feature. Upstash prices are per command — a token-bucket check is 1–2 commands per request, so 50M requests ≈ $10–20/mo on PAYG after the free 500K. The traps & perks column moved to each service’s review page (click the name) — Upstash’s replication doubling and fixed $10/$20 tiers, the retired Cloudflare legacy product, what nginx limit_req cannot stop. Scores are our editorial estimate (0–100) of value for the rate-limiting job at reference volume.
DDoS — what “unmetered” actually covers, layer by layer
The best deal in this entire page: Cloudflare absorbs unmetered L3/L4/L7 attacks on every plan, Free included — you only pay when your traffic isn’t proxied HTTP/HTTPS. AWS splits the same promise into a free network layer (Shield Standard) and a $3,000/mo everything-else (Advanced).
| Service | Price | Layers | Fine print | Score |
|---|---|---|---|---|
| | $0 all plans, including Free | L3 / L4 / L7 | Proxied HTTP/HTTPS only — you are protected “up to the layer on which your service operates”; raw TCP/UDP needs Spectrum / Magic Transit (Enterprise) | 75/100 |
| | $0 enabled automatically for every AWS customer | L3 / L4 only | No L7 — HTTP-layer flood protection is AWS WAF’s job, billed separately; cost protection (attack-spike credits) is Advanced-only | 64/100 |
| | $3,000/mo per payer account + 1-year commitment | L3 / L4 / L7 | Plus data transfer out (CloudFront/Global Accelerator $0.025/GB first 100TB, tiered to $0.01; Route 53 $0; ELB/Elastic IP render dynamically) AND a paid Business/Enterprise Support plan; WCU above 1,500 bill fully — official Example 9: 60B requests at 2,000 WCU = $12,000/mo in WCU charges alone | 46/100 |
Shield Advanced also requires a 1-year subscription commitment per payer account and a paid Business or Enterprise Support plan — a dependent cost the $3,000 headline hides. What’s covered — the “unmetered and unlimited” promise, Shield Advanced’s bundled WAF allowance (1,500 WCUs, 50B requests/mo, then $0.15/1M) — moved to each service’s review page (click the name). Scores are our editorial estimate (0–100) of DDoS value per dollar at reference volume.
50M req → $39–$89/mothe AWS WAF meter at reference volume — vs $0–$200 flat at Cloudflare
Traps — the fine print that moves the bill
Nine verified gotchas from the official pages — stale article numbers, hidden free tiers, hidden dependent costs, and one 667× multiplier hiding inside a rule action.
- — AWS CAPTCHA costs $4.00 per 10,000 attempts — the official pricing page computes it itself ($0.40/thousand, Case G). Articles still quoting “$0.40 per 10K” are 10× understated, and one attempt (~$0.0004) costs ≈667× a plain request at $0.60/1M (~$0.0000006). Serve CAPTCHAs surgically, never site-wide.
- — AWS Challenge pricing is dynamic: the exact per-million figure ($0.40) never renders in the static pricing page — only the “per million responses served” basis is confirmed. Re-check before modeling.
- — Cloudflare Free rate limiting 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; non-IP counting characteristics are Business+.
- — Cloudflare legacy rate limiting is retired — the docs say “no longer available”, all rules upgraded. Any article still billing it per 10K requests/month describes a product that no longer exists.
- — WAF false positives break webhooks: Stripe and GitHub webhook senders carry no browser headers. 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”. (Webhook breakage is field analysis, not a documented failure — route webhooks around managed rules.)
- — AWS WAF oversized inspection stacks on the whole request: at 2,000 WCU every request bills at $0.80/1M (official Case I), not just a surcharge — +$20/mo per extra 500 WCU at 100M requests.
- — AWS Bot Control hides free allowances: first 10M requests/mo free on Common ($1/1M after), first 1M free on Targeted ($10/1M after) — light traffic pays only the $10/mo per-ACL base.
- — Shield Advanced carries hidden dependents: $3,000/mo + 1-year commitment + data-transfer-out fees AND a paid Business/Enterprise Support plan. The 50B-request WAF allowance holds only at ≤1,500 WCU.
- — Fastly NGWAF request volumes are unpublished: the pricing page shows only rule counts (5/25/100) and workspaces (5/20/20) — the 2.5B/1.5B request-pool figures circulating in articles cannot be confirmed on fastly.com. Everything a rep quotes is negotiable.
The open-source path — nginx limit_req at $0
The documented behavior: nginx limits the request processing rate per a defined key with a leaky bucket, and excessive requests are terminated. Ten lines of config buys a per-IP rate limit with no meter, no plan and no vendor — the whole cost is the box it runs on.
# /etc/nginx/nginx.conf — per-IP leaky bucket, zero dependencies
limit_req_zone $binary_remote_addr zone=api:10m rate=10r/s;
server {
location /api/ {
limit_req zone=api burst=20 nodelay;
limit_req_status 429;
}
} What it cannot stop (our analysis — consistent with the module’s per-key design, not an nginx-documented limit): volumetric L3/L4 floods (the pipe dies before a request reaches nginx), distributed low-and-slow from 50K IPs (every address stays politely under 10 r/s — no single bucket trips), and NAT collateral (one office IP means the whole office shares a single 10 r/s bucket and humans start eating 429s). One layer down, nftables adds connection and packet-rate limits at the firewall itself — same $0, same single-box view, nothing above L4.
What is actually free — the Cloudflare Free ledger, with the corrections
The Free plan is a real security stack, not a trial. But two numbers circulate wrongly: Workers paid is $0.30/1M (not $0.15 — that is Durable Objects), and “Bot Management ~$2,000+/mo” is a third-party estimate for a product Cloudflare prices only by your account team.
| Item | What Free actually includes | The catch |
|---|---|---|
| Unmetered DDoS (L3/L4/L7) | Every Cloudflare plan including Free — “unmetered and unlimited” | Proxied HTTP/HTTPS only; raw TCP/UDP = Spectrum / Magic Transit (Enterprise) |
| Free Managed Ruleset | High-impact managed rules, automatic, on all plans | Full Cloudflare Managed Ruleset + OWASP Core are Pro+ |
| 5 custom WAF rules | Free plan | No regex — regex support starts at Business ($200/mo annual) |
| 1 rate limiting rule | Free plan, $0 per request | IP-only counting, 10-second window |
| Bot Fight Mode | Free — plus Block AI bots and AI Labyrinth at $0 | Super Bot Fight Mode is Pro/Business; Bot Management is an Enterprise add-on, no published price (“by your account team”) |
| Turnstile | Free plan: 20 widgets per account | Beyond that is Enterprise “Contact Sales” |
| Workers free tier | 100K requests/day · static assets free and unlimited | Paid Workers Standard is $0.30/1M requests with 10M/mo included — NOT the often-quoted $0.15/1M (that is Durable Objects); cache hits bill as requests |
Also free and verified: Workers static assets are “free and unlimited”, and the Workers free tier allows 100K requests/day. There is no $5/mo bot tier between Free and Pro — the ladder is Bot Fight Mode (Free) → Super Bot Fight Mode (Pro/Business) → Bot Management (Enterprise add-on).
Deep dives
- API Security: What 50 Million Requests Actually Cost — the four bills for the same traffic: $0 flat, $39–$89 metered, $3,000 with commitment
- How This Site Runs Bot Protection for $0 — our real stack: three zones on Cloudflare Free, the honest 10-second limit, what we refuse to pay for
- WAF Fine-Print Traps — CAPTCHA billing, a dynamic Challenge price, WCU surcharges, Shield Advanced's hidden dependents
- You Don't Need a WAF (Yet) — static site + Cloudflare Free + nginx limit_req carry real traffic; the honest thresholds for paying