Right alert,
right channel, right time.
Wire any threshold (CPU, memory, disk, agent uptime, container state, drift findings) to any channel (email, Telegram, Slack, Discord, WhatsApp, webhook). Cooldowns built in.
Notifications & Alerts
6 alert rules · 4 channels wired
- CPU > 90% on web-015 min sustainedTelegram, Email15 min
- Agent offline3 minPagerDuty, Slack5 min
- Disk > 85%anyEmail60 min
- Wallet < $20instantEmail, Telegram24 h
- Drift critical findings> 0Slack, PagerDuty15 min
- WAF blocked > 100/minrolling 1 minTelegram10 min
How it works
What happens under the hood.
- 01
Define a rule
Pick a metric, set a threshold + duration. "CPU > 90% for 5 minutes" or "agent offline for 3 minutes".
- 02
Wire a channel
Email, Telegram bot, Slack incoming webhook, Discord webhook, WhatsApp business API, or a generic webhook.
- 03
Threshold breached → fire
Notification posts to the channel(s) you wired. Cooldown window prevents storms.
- 04
Audit + ack
Every alert logs to the activity timeline. Acknowledge to silence cooldown; review for trends.
What you get
The capabilities that ship.
SMTP / Resend / SES. Per-rule recipient list.
5 chat platforms
Telegram, Slack, Discord, WhatsApp Business, Microsoft Teams (incoming-webhook compatible).
Generic webhook
POST JSON to any URL — wire to PagerDuty, Opsgenie, or your own incident pipeline.
Per-rule cooldown
No alert storms. Set "minimum 15 min between fires per rule".
Multi-channel routing
High-severity goes to phone (WhatsApp), low to email digest. Per-rule channel selection.
FAQ
Common questions.
Can I get phone calls for critical alerts?
Does it support paging schedules?
Your fleet deserves better.
Get started in minutes.
Deploy agents on your servers, connect securely, and take full control. Start free, upgrade when ready.
- 7-day free trial
- No credit card
- Cancel anytime
