In Cloudflare, how do Bot Fight Mode, Super Bot Fight Mode and Bot Management for Enterprise differ in plan, control and exceptions?
answer
- one detection engine, three tiers
- Free tier ignores Skip
- phase after custom rules
- Likely automated starts at Business
- per-request score needs the add-on
basics
~20 sBot Fight Mode (Free) challenges bot patterns site-wide and no custom rule can skip it. Super Bot Fight Mode (Pro and up) adds per-group actions and Skip exceptions. Bot Management for Enterprise exposes a per-request score and fields for custom rules.
solid answer
~40 sAll three share Cloudflare's detection technology and differ in control. **Bot Fight Mode**, on the Free plan, issues computationally expensive challenges to traffic matching known bot patterns across the whole domain; it runs outside the Ruleset Engine, so a custom rule's *Skip* cannot exempt anything, and the options for a false positive are an IP Access rule that matches the client, turning it off, or upgrading. **Super Bot Fight Mode**, on Pro, Business and Enterprise without the add-on, lets you pick Block, Managed Challenge or Allow for **Definitely automated** (score 1) and **Verified bots** and, from Business, **Likely automated** (2-29); it runs in the `http_request_sbfm` phase after custom rules, so a custom rule with *Skip* carves out exceptions. **Bot Management for Enterprise** replaces both and scores every request 1-99 for path-specific custom rules.
go deeper
Recall the ladder: Bot Fight Mode on Free, Super Bot Fight Mode on Pro and Business, Bot Management as the Enterprise add-on, and that only the add-on exposes a per-request score.
Explain why Bot Fight Mode cannot be skipped while Super Bot Fight Mode can: one runs outside the Ruleset Engine, the other in the http_request_sbfm phase after custom rules.
Show you can predict breakage: Bot Fight Mode challenging your own API clients, Super Bot Fight Mode on Pro unable to touch Likely automated traffic, a tunnel failing when Definitely automated is not on Allow.
Frame the tier as a question of exceptions and visibility: what the team's own automation needs, what a false positive costs at checkout, and when per-path thresholds justify the Enterprise add-on.
## One detection engine, three levels of control Cloudflare sells bot protection in three tiers. **Bot Fight Mode** and **Super Bot Fight Mode** use the same underlying technology as **Bot Management for Enterprise**; what changes is how much of the verdict you can see and steer. The two Fight Modes protect an entire domain with no endpoint restrictions, and Cloudflare warns that they may challenge API or mobile app traffic. That is why the question that matters for a marketplace is less "which tier detects more" than "can I make an exception for my own automation". | | Bot Fight Mode | Super Bot Fight Mode | Bot Management for Enterprise | | --- | --- | --- | --- | | Plan | Free | Pro, Business, Enterprise without the add-on | Enterprise add-on | | Detects | Simple bots from cloud hosting providers, headless browsers | Pro: simple bots, headless browsers; Business adds many sophisticated bots | Simple and sophisticated bots, headless browsers, domain-specific anomalies | | Actions | A computationally expensive challenge | Block, Managed Challenge or Allow per group | Any custom rule action on a 1-99 score | | Scope | Whole domain | Whole domain | Any path, host, IP or other field | | Exceptions | No Skip; a matching IP Access rule | Custom rule with Skip; IP Access Allow | Custom rules on bot fields | | Analytics | Security Events | Bot Report (Pro), Bot Analytics (Business) | Bot Analytics, logs, Workers | ## Bot Fight Mode on the Free plan Bot Fight Mode is a single toggle under **Security Settings**, filtered by **Bot traffic**. Once on, it: - identifies traffic matching patterns of known bots; - issues computationally expensive challenges that make each automated request cost the client CPU time; - runs JavaScript Detections, which on this tier are on and cannot be turned off. Its limitation is structural. Bot Fight Mode does not run on the **Ruleset Engine**; it sits in a separate evaluation pipeline where the *Skip*, *Bypass* and *Allow* actions have no effect. A WAF custom rule cannot exempt the marketplace's uptime checker, its partner feed or its own API clients. An IP Access rule that matches a request first does keep Bot Fight Mode from triggering for it; beyond that, the choices are to turn the feature off or to move to Super Bot Fight Mode. Challenged requests appear in Security Events with **Bot Fight Mode** in the **Service** field. ## Super Bot Fight Mode on Pro and Business Super Bot Fight Mode groups traffic and lets you choose an action per group: - **Definitely automated** (bot score 1) on Pro, Business and Enterprise; - **Likely automated** (scores 2-29) on Business and Enterprise only; - **Verified bots**, the directory of known good crawlers and services, set to Allow or Block; - **Static resource protection**, **JavaScript detections** and **Optimize for WordPress** as extra switches. It runs in the `http_request_sbfm` phase, after WAF custom rules. A custom rule with the *Skip* action and the **All Super Bot Fight Mode rules** option therefore exempts exactly the traffic it matches, and an IP Access rule with Allow works too. Two operational cautions: updating Super Bot Fight Mode rules through the Rulesets API is no longer supported, and a zone that also runs a Cloudflare Tunnel should keep **Definitely automated** on Allow, or tunnel connections can fail with `websocket: bad handshake`. An Enterprise zone without the add-on gets the Business version. ## Bot Management for Enterprise The add-on gives every request a **bot score** from 1 to 99 and exposes it with other fields (`cf.bot_management.score`, `cf.bot_management.verified_bot`, `cf.bot_management.ja3_hash`, `cf.bot_management.ja4`, detection IDs and tags) to custom rules, Workers and logs. The **Definitely automated** and **Likely automated** toggles still give baseline protection, and custom rules add per-path thresholds: strict on checkout, relaxed on the blog. Buying it replaces and disables Bot Fight Mode and Super Bot Fight Mode, and the zone stops showing them. On other plans, Pro and above see traffic only in score groupings, never the per-request number. ## Choosing for the marketplace 1. On Free, Bot Fight Mode suits a site with no automation of its own. Once checkout APIs, monitors or partners are challenged, there is no rule-based exception. 2. On Pro or Business, Super Bot Fight Mode with **Verified bots** on Allow keeps crawlers in, a Skip rule covers your own automation, and Business is needed to act on Likely automated traffic. 3. On Enterprise, Bot Management earns its cost when you need different thresholds per path, fingerprints for your mobile app, or detection IDs. **Block AI bots**, AI Labyrinth and managed `robots.txt` directives are available on every tier and sit beside these choices.
- A Free-plan zone's uptime checker is challenged by Bot Fight Mode; what can the team do?No custom rule helps: Bot Fight Mode runs outside the Ruleset Engine and ignores *Skip*, *Bypass* and *Allow*. An IP Access rule that matches the checker's address stops Bot Fight Mode from triggering for those requests. Otherwise the team turns Bot Fight Mode off or moves to Super Bot Fight Mode, whose phase a custom rule with *Skip* can exempt.
- Why does it matter that WAF custom rules run before Super Bot Fight Mode?A custom rule that matches first decides the request's fate: a terminating action such as Block or Managed Challenge means it never reaches Super Bot Fight Mode, and a *Skip* rule can exempt it from the `http_request_sbfm` phase. It also means a custom rule you add takes priority over the bot settings for the traffic it matches.
- A WAF custom rule with Skip can exempt a monitoring service from Bot Fight Mode.
- Super Bot Fight Mode on Pro can act on Likely automated traffic.
- Free and Pro zones can write rules on the per-request 1-99 bot score.
- Buying Bot Management leaves Super Bot Fight Mode running underneath it.
- Bot Fight Mode never challenges API or mobile app traffic.