Alerts that reachthe person on call.
12 native channels: email, Slack, Discord, Telegram, Twilio SMS, Pushover, ntfy, Matrix, Rocket.Chat, PagerDuty, Microsoft Teams and webhooks. Routed per monitor, so the right person hears about it.
Where your team already looks.
Alerts are only useful where people read them. Chat teams get Slack, Discord, Teams, Rocket.Chat or Matrix. On-call rotations route through PagerDuty. Phones get Twilio SMS, Pushover or ntfy. Email and webhooks cover everything else.
All 12 are native integrations, PagerDuty and Teams included. No glue scripts to babysit.
- 12 native channels
- Chat, paging, SMS, push and email
- Webhooks for everything custom
Page the owner, not the whole team.
Blanket alerts train people to ignore alerts. In Checkmate, notifications are configured per monitor, so the database going down pages the database owner and the marketing site pages whoever owns that.
Group monitors by team and scope the noise to the people who can act on it.
- Per-monitor notification settings
- Ownership and team scoping
- Different channels for different services
Quiet during deploys, loud during outages.
Maintenance windows suppress alerts on a schedule, with grouped and recurring windows for routine work. Deploys stop paging people.
For flappy networks, n of m confirmation holds an alert until the last n of m checks agree the service is down. What gets through is worth waking up for.
- Maintenance windows, one-off or recurring
- n of m confirmation before alerts fire
- Test notifications before you rely on them
For whoever holds the pager this week.
On-call engineers
PagerDuty escalation for production, Slack for the rest. Route by severity so the pager only goes off for pager-worthy problems.
Small teams
No formal on-call rotation, one shared channel. Discord or Telegram alerts put monitoring where the team already talks.
Self-hosted purists
ntfy and Matrix support means the whole alerting path, monitor to phone, can run on infrastructure you control.
What it covers, and what it doesn't.
Covered
- Email, Slack, Discord, Telegram and Microsoft Teams
- Twilio SMS, Pushover and ntfy
- Matrix and Rocket.Chat
- PagerDuty with escalation policies
- Custom webhooks with your own payload
- Per-monitor recipients and channel routing
- Maintenance windows and n of m confirmation
Out of scope
- On-call schedules and rotations: route through PagerDuty when you need escalation logic
- Voice call alerts: SMS via Twilio is supported, phone calls are not
- A mobile app: alerts arrive through the channels above
For the technically curious.
Webhooks take any payload
The webhook channel fires an HTTP request you shape, so alerts can feed Opsgenie, a bot, an automation pipeline or anything with an endpoint. If it speaks HTTP, it can hear about your outage.
Authenticated ntfy
ntfy topics can require authentication and Checkmate supports it, so self-hosted push works on locked-down ntfy servers too.
PagerDuty, natively
Incidents route into a PagerDuty service and follow its escalation policy. Checkmate raises the incident, PagerDuty decides who wakes up.
Test before you trust
Send a test notification when configuring a channel, so the first real alert is not also the first delivery attempt.
Frequently askedquestions.
12: email, Slack, Discord, Telegram, Twilio SMS, Pushover, ntfy, Matrix, Rocket.Chat, PagerDuty, Microsoft Teams and custom webhooks. All native, including PagerDuty and Teams.
Yes. Notification settings are per monitor, so each service can page its owner on its own channels. Grouping monitors by team keeps a large setup manageable.
Set a maintenance window. Alerts are suppressed for its duration. Windows can be grouped or recurring for routine work like weekly deploys.
Use n of m confirmation: a monitor only changes status when the last n of m checks agree. Combined with per-monitor routing, what arrives is real and relevant.
Yes, through the webhook channel, which sends an HTTP payload you define to any endpoint. That covers Opsgenie, chat bots and home-grown automation.
Yes. Checkmate can send a test notification for a configured channel, so you know delivery works before you depend on it.
More to watch.
Uptime monitoring
Websites and APIs checked from 6 continents.
SSL monitoring
Certificate expiry caught before browsers complain.
Infrastructure monitoring
CPU, memory, disk and network via the Capture agent.
Docker monitoring
Container status, health checks and resource usage.
Game server monitoring
More than 100 game types over native protocols.
Status pages
Branded public pages served from your own instance.
All featuresEvery feature,no paywall.
Checkmate is open source under AGPL-3.0. Self-host it and this feature ships free, on your servers, with your data.