One line in your script — that's the setup
Each job gets a unique ping URL. Add `curl -fsS <url>` (or one PowerShell line) at the end of your backup script and you are done. Works with robocopy, rsync, pg_dump, cron, scheduled tasks — anything that can hit a URL.
The dead man's switch
You tell us how often the job runs (hourly to monthly, plus a grace window). If the ping does not arrive on time, we alarm — the check runs every 10 minutes, so a dead server or a disabled task is caught the same morning, not next quarter.
Explicit failures, with the reason
Your script can report a failure with its message ("disk full", "VSS error") — that alerts immediately. When the job reports OK again, you get the recovery notice too.
Duration, size and 90 days of history
Hit /start first and we measure how long each run takes; report bytes via the API and see backup sizes. Every job shows a 90-day strip — green, red or silent — so trends jump out at you.
API that registers jobs by itself
POST a run report and if the job does not exist yet, it is created on the spot — deploy a new script and it shows up watched. Plus signed webhooks (missed/failed/recovered) for Zapier, n8n or your own automation.
Same platform, same polish
Branded email alerts, Telegram, team roles (give your tech backups-only access), your public status page shows backup health, and it is included in the weekly report with everything else.