Do we need to replace our current protection?

No. Centinel works alongside your existing stack, with integrations for Cloudflare Workers and Lambda@Edge.

Why is browser-side verification necessary?

Sophisticated crawlers can use real browsers and realistic fingerprints. Browser-side verification checks whether the visit behaves like a genuine reader before protected content is served.

Will readers see a CAPTCHA?

No. The browser check runs automatically without a CAPTCHA or puzzle, and it does not repeat during the visit.

Is Centinel GDPR-compliant?

Yes. Centinel minimizes personal data and uses request and browser signals only to separate automated traffic from genuine readers.

Stop the crawlers your WAF can't see

Centinel detects real-browser automation, residential proxies, and AI scraper APIs so you can see who is accessing your content and decide what to allow.

Request a site audit

Centinel dashboard showing human, crawler, unknown, and blocked traffic — Live traffic classificationHuman, identified, unknown, and blocked traffic in one view

Featured by publishers and industry bodies

The scraper gap

Tell real readers from scrapers that look like them

Your CDN and WAF are built for DDoS and known crawlers. A sophisticated crawler that runs a real browser and behaves like a reader slips past them. Centinel closes that gap.

How the layers fit together

Your CDN and WAF

Absorb DDoS attacks
Block known crawlers and bots
Filter high-volume abuse

plus

Centinel adds

Catch stealth crawlers, not just bots
Read behavior across the session
Allow or block per crawler

How it works

It runs in the stack you already have.

Centinel is a call your edge makes before it serves a page. Cloudflare, CloudFront, Akamai and Fastly each hook it in their own way, and none of them needs anything new in front of your site.

View integrations See what it decides

Other platforms

01Downloadnpm package
@centinel/cloudflare-worker
02Set your keyWrangler secret
CENTINEL_SECRET_KEY
03Deploy
wrangler deploy

Cloudflare Workers guide

Not running one of those four?

It is the same one call from a reverse proxy, an application, or a CMS.

All 15 integration guides

Detection breadth

Detection across the crawler spectrum

Declared crawlers

Verify known identities and set policy per crawler.

Basic scripted clients

Identify request automation that does not behave like a browser.

Spoofed and headless automation

Detect automation that copies browser fingerprints and runtime traits.

Browser-like scraping services

Separate managed browser scraping from genuine reader sessions.

Security & privacy

Security and privacy, documented

Trust Center

ISO/IEC 27001 certified

Our information security is certified to the ISO/IEC 27001 standard.

GDPR-compliant

We minimize the data used for detection in line with the GDPR.

No reader profiling

Detection classifies automated traffic; it does not build reader profiles.

EU data storage

Data is stored in the EU.

Free site audit

See who's crawling your site

No card. No login. No code to change.

Research

Understand the crawlers hitting your site

Crawler verification

FAQ

Common questions

What publishers ask before deployment.

See what your current protection is missing