Alerts
Your site changed. Your team already knows.
Add a rule once. When a real visitor's browser reports the change, the message is already in the channel that owns that page.
Fires on ingest
Not a nightly sweep
Six destinations
Chat, email or webhook
Routed per site
And per team
No agent
One response header
Triggers
What's worth interrupting someone for.
Six things a rule can watch for, on any page you point it at.
A new origin appears
A script loaded from a host you have never seen. Most client-side attacks open exactly here.
A script changed
A file you execute no longer matches yesterday's hash. Your build did it, or somebody else did.
Something touched a payment page
Card-data pages get their own rules, because PCI DSS 11.6.1 asks you to alert on changes to them.
A known CVE turns up
A library you load has a published advisory. You hear it with the version and the CVE id.
Reports spike
Violations jumped after the 4pm deploy. Something broke at scale, and the browsers said so first.
A silent signal wakes up
A directive that reported nothing all quarter started talking. Worth a look before it is worth an incident.
Channels
This is what an alert looks like.
The same rule, reaching three teams where they already work. Every rule picks its own destination, so a checkout incident and a marketing-site warning never land in the same thread.
Every destination a rule can reach
Slack
Microsoft Teams
Google Chat
Telegram
- Webhooks
FAQ
Frequently asked questions
Channels, speed, noise and compliance, answered.
Set one rule today. Forget about it until it matters.
Add the header, connect a channel, pick the change worth a message. 14-day free trial, no agent to deploy.
