Rules you control
Decide what counts as an alert for each asset. A built-in change-detection rule is on from day one and doesn’t use up a rule slot.
Alerts that reach the right people, when it matters.
Set rules like “abuse score above 70” or “DNS changed”, then send them where your team already works: email, Slack, Microsoft Teams, webhooks or the REST API.
demo · fictional data
org: northwind.example
Interactive demo, 3/4 · Get alerted when something changes
assets
4
open_alerts
2
security_score
76/100
09:14CRITRDP (3389) open on 203.0.113.24
08:02WARNTLS certificate expires in 12 days
06:40INFODNS A record changed → 198.51.100.17
Sent to Slack
# security-alerts
TLINK PRO APP 09:14
CRITICAL · RDP (3389) open on 203.0.113.24
vpn.northwind.example · rule: risky port opened
View alert →
Use ← → or the buttons to move between steps. All data is fictional.
What you get
Slack and Microsoft TeamsPro
Post alerts to a channel with the asset, severity and a link back to the details.
Webhooks, API and quiet hours
Push alerts to your own tools with webhooks or pull them from the REST API. Quiet hours hold back non-urgent email overnight.
Why it matters
An alert nobody sees is just a log line
Small teams don’t sit in front of a SOC console. Alerts need to land where people already are, and stay quiet when nothing important has happened.
- Email alerts on every plan
- Slack and Teams on Pro
- Webhooks and REST API on every plan
Get your first alert in minutes
Add a domain, keep the default rule, and connect the channel you use.