Cron jobs · backups · pipelines · reports
Know when your events stop firing
Register expected events, POST a heartbeat when they succeed, and get emailed when something misses its window — before users notice.
# After your job succeeds
curl -X POST https://gonewatch.com/api/heartbeat/YOUR_TOKENNo agent. No SDK. One URL in your script.
Built for solo devs & small teams
See it in action
A missed heartbeat becomes an overdue window, then a Down alert — before your users notice anything broke.
What happens when a job slips
Production DB backup
Daily at 8:00 PM · Eastern
Last heartbeat · 2 minutes ago
Up → Overdue → Down → Alert
Your dashboard at a glance
Monitors
Track heartbeats from cron jobs, backups, and pipelines.
- Down
Production DB backup
No pings yet·Daily at 8:00 PM · Eastern
- Overdue
Weekly revenue report
45 minutes ago·Mon at 9:00 AM · Eastern
- Up
Stripe subscription sync
3 minutes ago·Every 15 minutes
- Up
Search index rebuild
6 hours ago·Daily at 3:00 AM · UTC
Questions before you sign up? Read the FAQ on pricing
Simple heartbeats
POST when your job finishes. One URL per monitor — no agent required.
Fixed time of day or rolling interval
Daily at 8 PM, weekly on Monday, or every N minutes — plus a grace window after each expected window.
Email alerts
One email when a monitor goes Down. Another when it recovers.
Built for developers
cURL, Node, and Python snippets on every monitor. Dashboard stays out of the way.
How it works
From zero to your first alert in minutes.
- 1Create a monitor — fixed time of day or rolling interval
- 2Copy the heartbeat URL into your script or cron
- 3POST when the event completes successfully
- 4Get emailed if the heartbeat stops arriving
Stop finding out from users
Silent cron failures are expensive. Gonewatch tells you when expected work didn't happen.
Get started free