Start in the browser.
The JavaScript collector, served from collector.kairal.io, provides device and interaction signals. Those signals help Kairal recognise repeat activity and understand how a visitor moves through your website.
Apply the response at the edge or server.
Your edge or server integration provides request context and applies the policy response at the protected route. This connects browser activity with the point where access is allowed, challenged or mitigated.
Choose the connection that fits your environment.
Integration options include API, Go and JavaScript, plus NGINX, Cloudflare, Akamai, AWS CloudFront and HAProxy. Other environments are considered on request. Share your stack so we can confirm the appropriate integration and configuration.
Connect collection, assessment and response.
First, identify the journeys you want to protect. Add the browser collector and connect the relevant edge or server component. Review the resulting activity with your team, then configure and validate the response for those routes.
The deployment should fit your existing security controls, including how they handle useful crawlers and legitimate customers.