Bot Protection

Bot Protection in your dashboard

Filter common automated traffic from Projects → your project → Security. Enable it for a deployed static site or container project, and choose which path prefixes it covers.

Get started Read the guide

// 01 — bot-protection

Choose the paths to protect.

Enable Bot Protection, enter prefixes such as /login or /api, then save. An empty list applies filtering to every path. Test legitimate integrations after changing protection.

+ Independent from the Web Firewall toggle
+ Common-bot filtering; no guaranteed detection of every bot
+ APIs, crawlers, and other automated clients may be affected

// 02 — bot-protection

Review counts in the dashboard.

Matched requests shows aggregated blocked, allowed, and counted requests by rule for the selected time window. It does not show an individual request log or a visitor challenge history.

+ 1-hour, 6-hour, 24-hour, and 7-day windows
+ Refresh metrics on demand
+ Managed filtering does not promise an invisible browser challenge

// 03 — bot-protection

Review the price before enabling.

The project dashboard shows current access, protection and inspection rates before enablement. The access fee is charged once when either security product is enabled; product fees and custom rules are prorated by enabled time.

+ Protection requires an eligible deployed project
+ Blocked requests can still incur inspection or network usage

Current pricing

USD rates from the current billing catalog. Regional references vary with attributed usage.

Loading current rates…

Explore Bot Protection.

See the guide and current pricing before you start.

Get started Read the guide