worker/) and a full Go callback server is built into the CLI (snare serve).
Why self-host?
- Air-gapped environments — internal servers, no outbound traffic to snare.sh
- Custom callback domains —
canary.yourcompany.internalinstead ofsnare.sh - Data sovereignty — events never leave your infrastructure
- On-premises compliance — financial services, healthcare, defense
snare serve
Access the dashboard
Authorization: Bearer <token> for API access.
With TLS (Let’s Encrypt)
Docker
Point the CLI at your server
Edit~/.snare/config.json after snare init:
Cloudflare Worker (managed backend alternative)
Theworker/ directory contains the full Cloudflare Worker source. Deploy your own:
callback_base in ~/.snare/config.json to point at your worker URL.
Verifying webhook signatures
WhenWEBHOOK_SIGNING_SECRET is configured, outbound webhooks include: