Integrations
Use the setup you already have.
Centinel runs at the spot where visitors first reach your pages. That might be your CDN, your server, or your CMS. Pick your setup below. The rest of your stack stays the same.
How it works
How does Centinel fit in?
Your integration sends protected requests to Centinel for a decision and applies the response. Browser collection, enforcement location, and failure handling depend on the platform you choose.
- 01
Pick the pages to protect
Choose what to guard: paid content, search pages, login, and checkout.
- 02
Check each visitor
The integration sends request context for validation. Browser collection adds session evidence where that integration supports it.
- 03
Act on it
Allow, block, or check the visitor, based on your rules. It happens right where the request arrives.
Guides
Which platform do you use?
There is a guide for each one below. Pick yours and follow the steps.
Edge and CDN
Reverse proxy and server
Application and CMS
Plan the evaluation
What should you prepare before rollout?
Start with one affected workflow and a testable outcome. A public article, login form, and direct API client need different evidence and response handling.
1. Map the traffic path
Identify the hosts and routes to protect, where requests reach your stack, and which approved crawlers or integrations need access.
2. Test the full workflow
Include normal users, approved automation, and the abusive sequence you want to control. Check responses, latency, session continuity, and what happens when a dependency fails.
3. Agree ownership and rollback
Name the people responsible for integration changes, policy decisions, and unexpected blocks. Review results before expanding protection to more routes.
Implementation questions
Bring the right inputs to a technical review.
What determines the rollout schedule?
Scope the integration point, protected routes, access policy, and test traffic first. Allow time for legitimate-user checks, failure handling, and rollback. Confirm a schedule with the team once those requirements are clear.
Who should be involved in the evaluation?
Bring someone who can configure your CDN, reverse proxy, or application, plus the owner of the affected workflow. Agree who reviews unexpected blocks, approves policy changes, and handles rollback.
Can we keep our current CDN and WAF?
Yes. Choose the integration for your current stack and check which traffic it can observe and control. The available browser evidence and response handling depend on that integration.