Deployment Options
Guard has to sit in the path of your traffic. Where it runs depends on your setup.
| Option | Runs in | Status |
|---|---|---|
| Self-hosted proxy | Your own infrastructure, in front of your web servers | Closed beta |
| Cloudflare Workers | Cloudflare’s edge network | Planned |
| Edge functions | Edge platforms such as Vercel or Netlify | Planned |
| Middleware | Your application, e.g. Express or Next.js | Planned |
| WordPress | Your WordPress site, as a plugin | Planned |
Which option fits?
- At the edge (Cloudflare Workers, edge functions): bots are stopped before they reach your infrastructure.
- Self-hosted proxy: all traffic stays in your own network.
- Middleware: protect specific routes without changing your infrastructure.
Planned options may still change. Need one of them? Contact us.
Last updated on