Catch the job that silently stopped.
Before the data goes stale.
Reverse monitoring for cron jobs, batch pipelines and workers. Have them ping a unique URL on each run, we alert the moment a run is missed or finishes outside its expected window.
Nightly Backup
Monitoring that listens, not just polls.
Cron jobs and workers don't expose an endpoint you can check. Instead, flip the model: let your jobs report in, and get alerted the moment one goes quiet.
Passive check-ins
Every heartbeat monitor gets a unique ping URL. Append a single curl call to your cron job or script and we track every run. No agent to install, no inbound firewall rules, no polling from our side.
- A unique URL per job
- No agent or inbound access needed
- Works for cron, workers, ETL, backups
Stale-heartbeat detection
Set an expected interval and a grace period. If a job hasn't checked in by the deadline, we open an incident: whether it crashed silently, got stuck, or was never scheduled in the first place.
- Alert when a job misses its window
- Configurable grace periods
- Per-job expected intervals
Schedule Overview
Incident on miss
A missed heartbeat opens a real incident, not just an email. Route it to the team that owns the job, escalate if no one acknowledges, and auto-resolve the moment the next ping arrives.
- Trigger incidents on missed runs
- Route to the owning team
- Auto-resolve when the next ping arrives
Never discover a dead cron job from a customer.
Add a heartbeat in under a minute.
Create Your First Monitor