Integrations

Bot and VPN blocking integrations

One engine and one site policy. Put it at the edge, in your proxy, in WordPress or in your code.

Starts in monitor modeFails open after 1.5 s

All integrations

Pick where it runs

Closer to the visitor is better. One free account covers all of them.

At the edge

Your proxy

  • Traefik

    A middleware plugin you add to any router, Coolify included.

  • Caddy

    A module with its own Caddyfile directive, built in with xcaddy.

  • nginx, Apache, HAProxy

    One small container your proxy asks first. Works with Nginx Proxy Manager.

Your CMS

Your forms

  • Form gate

    One script tag on your form, one verify call on your server.

Your code

Your AI tools

  • MCP server

    Lets Claude, Cursor or VS Code look up IPs and verify crawlers.

Sites dashboard

Same policy everywhere

Allow, flag or block each traffic class once. The Worker, the proxies, the plugin and the form gate all follow it, with no redeploy.

  • New sites start in monitor mode and block nothing.
  • Verified search and AI crawlers always pass.
  • If IPScanner is slow or down, visitors get through.

Questions

Integrations FAQ

The one closest to your visitors. Behind Cloudflare, the Worker. On your own server, the integration for your proxy. On WordPress without either, the plugin.

Pick one and start in monitor mode

Create a key, add a site, read a week of traffic, then block.