docs
heartbeet is a silence monitor for scheduled jobs: your cron jobs, backups, and pipelines prove they're alive by sending heartbeats, and the beets page you when an expected heartbeat doesn't arrive. the classic name for this pattern is a dead-man's switch. no intervals to configure; the beets learn each job's rhythm on their own.
start here
- quickstartfrom zero to a monitored job in one curl.
- how it workswhat the beets actually learn, and when they decide to page.
- the APIheartbeats, tags, hints, pausing, and idempotent retries.
- for coding agentshow an AI agent sets up monitoring on its own, and hands the project to a human later.
guides
- monitor a backup scriptthe classic; know the night it stops running, not the day you need the backup.
- monitor a GitHub Actions schedulescheduled workflows get throttled and silently disabled; catch it.
comparisons
these tools are good, and you might want one of them instead.
- heartbeet vs Healthchecks.iothe open-source veteran with configured periods.
- heartbeet vs Cronitorthe polished observability suite.
- heartbeet vs Dead Man's Snitchthe minimal original.
the short version
- a job is anything that runs on a schedule and can send an http request when it finishes.
- a heartbeat is that request:
POST https://heartbeet.page/<job-name>with your API key. the first heartbeat creates the job; there is no registration step, ever. a new job is a name you invent, and it shows up on your live dashboard on its own. - the beets learn each job's rhythm and natural variability from its heartbeats, and page you by email when a job goes quiet for longer than its own usual rhythm allows.
- the free plan covers 2 projects with unlimited jobs and unlimited API keys; see pricing for the backer and team tiers.
- the beets never stop watching a live job; if a paid plan lapses, the limits come back but paging never stops.