Uptime + response + heartbeat monitoring
Know when your service
is really down.
Monitor public websites and APIs, add optional text or JSON response checks, and watch scheduled jobs with heartbeats. Choose Email, Telegram, Discord, or an eligible Slack connection for Down and recovery alerts.
Checks run from outside your service.
Private pilot · invite code required · 3 monitors per account · HTTP checks from every 10 minutes
Illustrative example
Status at a glance
API /health
HTTP monitorHTTP 200Expected: status = "ok"Received: status = "error"
Nightly backup
Heartbeat monitorResponse validation
200 OK doesn't
always mean OK.
Availability tells you the endpoint answered. A response check tells you whether it answered with the thing your app needs.
{
"status": "error",
"database": {
"connected": false
}
}database.connected = truedatabase.connected = falseAlert channels
Choose where alerts
reach you.
Connect a channel and explicitly turn its alerts on. Email is a familiar place to start; each option has its own connection steps.
Verify your account address, then enable alerts.
A familiar place to startTelegram
Connect the Pulse bot in a private chat.
Private chat onlyDiscord
Connect a webhook for a channel you manage.
Down and recovery alertsSlack
Connect through the Pulse operator's workspace.
External workspaces aren't open during the pilotHow it works
Start with a monitor.
Look for its first result.
Each path gives you a status before you choose whether to set up alerts.
Keep a quiet eye on it
Ship it. We'll
keep watch.
Start with your website, API, or background job.