How This Site Runs Bot Protection for $0
$0/mo — 3 zones, full bot stack the number that matters here
By Stan K.
Not theory — deployment. Toolscore runs three zones on Cloudflare's free plan: 5 custom rules, one rate-limiting rule with its honest 10-second window, Turnstile, AI crawlers blocked at the edge. What we run, what we refuse to pay for, and where the free walls are.
Most bot-protection writeups price a hypothetical API with hypothetical traffic. This one is a deployment report: this site runs on Cloudflare’s Free plan — three zones, $0/month — in front of a static site, with the AI-crawler and abuse settings actually turned on. Here is exactly what that buys, where it honestly stops, and what we deliberately don’t pay for.
The stack, as deployed
- Unmetered DDoS, layers 3/4/7 — official words: “unmetered and unlimited… to all customers on all plans”, Free included. It covers proxied HTTP/HTTPS, which is everything behind the orange cloud.
- The Free Managed Ruleset — high-impact managed rules, automatic on every plan. The full Cloudflare Managed Ruleset and OWASP Core start at Pro; we don’t miss them, because…
- 5 custom WAF rules — the Free allotment, no regex (regex is a Business feature, $200/mo billed annually). Five literal rules cover a static site’s entire attack surface: there barely is one.
- 1 rate-limiting rule — the Free limit, and the honest part: it counts by IP only, in a 10-second window. “60 requests per minute” is not expressible on Free — 1-minute windows arrive with Pro, 10-minute with Business.
- Bot Fight Mode, Block AI bots, crawler protection — all $0, all on.
- Turnstile — free plan, 20 widgets per account, $0. We have never needed the 21st.
Blocking AI crawlers is positioning, not paranoia
The Block AI bots setting costs nothing, and for a site whose product is verified research it is also the strategy. Every AI crawler that distills our tables into someone else’s answer-engine response is traffic we gifted away. robots.txt is a request; the edge setting is enforcement — and enforcement keeps the raw pages for the humans, and the search engines, that link back.
What we don’t run — and why
- Super Bot Fight Mode — Pro and above. It exists to protect logins and sessions; a static site has neither.
- Bot Management — an Enterprise add-on priced “by your account team”; Cloudflare publishes no number. The “$2,000+/mo” figures in third-party articles are estimates, not quotes. There is no $5/mo middle tier — the ladder is Free, Pro, then the Enterprise add-on.
- AWS WAF — a meter ($5/web ACL, $1/rule, $0.60/1M requests) that buys nothing for us here; and its CAPTCHA action bills $4 per 10,000 attempts, a trap we would be importing on purpose.
- Business ($200/mo) — buys regex and 100 rules. Five rules and zero server-side state make this an easy decline.
$0/month: DDoS absorption on three layers, a managed ruleset, five custom rules, one rate-limiting rule, Turnstile, and AI-bot blocking. The walls are real but knowable in advance — no regex, one 10-second window, IP-only counting. The day we need more, the next step is $20/month; what that buys, and what 50M requests cost on every ladder at once, is in API Security: What 50 Million Requests Actually Cost.
A static site changes the threat model more than any plan tier does: no database to inject into, no session to hijack, no POST that mutates anything. The edge caches, the rules filter, the origin serves files. When the first dynamic endpoint with users ships, the calculus changes — that path is mapped in the API Security hub.