PULSEGUARD · PUBLIC TRIAL
Know when your monitor dies
Dead man switch monitoring / heartbeat watchdog for cron jobs and workers. Your jobs ping on a schedule; if heartbeats stop, Telegram alerts fire within minutes—so silence itself becomes the incident.
1. Create a probe
Get an auth token and timeout threshold.
2. Send heartbeats
curl / cron / your worker — Bearer token.
3. Get alerted
Miss the window → Telegram fires fast.
Learn more
- Dead man switch monitoring — when silence is the incident
- Heartbeat watchdog — Telegram alerts when jobs go quiet
- Docs — auth, interval, timeout, alerts, curl examples
Quick heartbeat
curl -X POST \ -H "Authorization: Bearer <token>" \ https://pulseguard.agentbuff.dev/api/heartbeat
FAQ
What is a dead man switch for monitoring?
A dead man switch (heartbeat watchdog) expects your jobs to check in on a schedule. If heartbeats stop, it treats silence as the incident and alerts you—usually before customers notice.
How is PulseGuard different from classic uptime monitoring?
Classic uptime pings your URL to see if it responds. PulseGuard Watchdog waits for your jobs to ping in; silence itself is the alert. Not classic uptime — a heartbeat when jobs go quiet.
How do Telegram alerts work?
Create a probe, send authenticated heartbeats on an interval, and set a timeout. When check-ins miss the window, PulseGuard notifies your Telegram chat within minutes.
Is there a paid plan?
The public trial is free. Use the Interested in paid pricing CTA on the site to leave your email for pricing updates.