Separate application-layer bot floods from volumetric DDoS
Aggressive crawlers and distributed automation can consume application capacity. Centinel complements rather than replaces volumetric DDoS protection.
Request a site auditBot floods and volumetric DDoS need different controls
Network-layer protection absorbs volumetric attacks. Bot management evaluates application requests that reach valid routes and resemble usable traffic. Centinel's validation path fails open when unavailable, so it is not an availability boundary.
Read the researchWhat the traffic looks like
No coordination required
A traffic spike can come from one aggressive scraper or from several unrelated crawlers whose requests happen to overlap.
Retries that make it worse
Automated clients may retry slow or rejected requests. Without a bounded retry policy, that behavior can add load during an existing spike.
Traffic spread across clients
Requests distributed across many IPs and sessions can be harder to separate from legitimate demand using a single threshold.
What runs against this traffic
Separate automation from volume
Centinel evaluates supported automation evidence while the CDN or network service continues to handle volumetric traffic controls.
Each layer can act on the problem it is designed to observe instead of treating every spike as the same event.
Read more: Separate automation from volumeApply policy before the origin
Only integrations that enforce at the edge can apply supported responses before the request reaches the application.
The origin receives fewer requests that the site's automation policy has already rejected.
Read more: Apply policy before the originKeep the existing network layer
Centinel does not replace volumetric DDoS protection, capacity planning, or application resilience.
Teams retain their availability controls and add a separate policy for supported application-layer automation.
Read more: Keep the existing network layer
Want to see what reaches your site?
Start with a free scraping audit: tested tools, exposed pages, and fixes to consider, reviewed by hand and emailed to you. This checks scraping exposure, not every abuse pattern or all production traffic. Discuss broader workflow coverage in a demo.