Skip to content
Integrations

Connect Kairal to your stack.

Integrate at your CDN, reverse proxy or application. Choose where Kairal assesses requests and where your infrastructure applies the response.

Choose where protection runs.

Start with the layer you control. Edge and Core integrations connect Kairal to your existing request path. Use the API when you want to build the integration yourself.

Edge

At your CDN

Assess requests at the edge, before they reach your application. Apply the response through the CDN that already handles your traffic.

  • Connect at the edge of your infrastructure.
  • Choose the pages and endpoints to protect.
  • Apply access decisions before requests reach the origin.
Request pathEdge
Browser
EdgeIntegration point
Your application
Kairal assessment
Cloudflare
Akamai
AWS CloudFront
JavaScript

Add the browser side of the request.

The JavaScript collector adds device and browser information that an HTTP request alone cannot provide. Pair it with your Edge, Core or API integration to connect browser visits with server-side requests.

collector.kairal.io
Browser collector

Device and browser information

Server-side integration

Request and response

Collection happens in the browser. Access decisions are applied at your edge, proxy or server.

Start with visibility. Enable protection when you’re ready.

  1. 01

    Choose your integration

    Identify your CDN, proxy or application, and the pages you want to protect. We’ll confirm the setup for your environment.

  2. 02

    Review in Preview

    See requests and the decisions Kairal would apply, without blocking traffic. Check normal customer journeys alongside the unwanted requests.

  3. 03

    Enable enforcement

    Apply protection to the selected pages. Review challenges and blocks in the console, then adjust your policies as needed.

Keep requests moving if evaluation times out.

Enforcement fails open on an evaluation timeout: the request continues to your application. The timeout is configurable so you can set it around your request budget.

Before you integrate

Does the browser snippet block requests?

No. The browser collector gathers device and browser information. Your edge, proxy or server integration applies the response.

Do I need all three integration models?

No. Choose Edge, Core or API according to where you want to assess and handle requests. We’ll review the placement with you.

Can I start without blocking customers?

Yes. Start in Preview to review requests and intended decisions before enabling enforcement.

What should I share with your team?

Your CDN or proxy, application stack, the pages or endpoints you want to protect, and any request-timeout requirements. That gives us a starting point for your integration.

Bring your stack. We’ll work through the setup.

Tell us where your traffic enters, what sits in front of your application and which pages need protection.

Discuss your integration