Every job has a pulse.
Silence is the signal.

A dead-man's switch for cron jobs, workers, backups and sweeps. Each job proves it's alive by pinging on a schedule. Beet learns the cadence, and the moment a beat goes missing, the monitor flatlines and Beet pages you. Nothing to install: just curl.

How it works

a beat blips · silence flatlines

learningcheckout-api≤30s · no beatsprod

send a beat

# from your cron job, every run
curl -X POST https://heartbeet.page/backup-runner \
  -H "Authorization: <api-key>"

The underlined name is your service. The first ping creates it.

announce a planned interruption

# before a deploy or planned shutdown
curl -X POST https://heartbeet.page/backup-runner?pause&wait=10m \
  -H "Authorization: <api-key>"

Send this before a deploy so the silence is expected. A crash can't send one, so it still pages you.

What a dashboard looks like

synthetic · one service per state

7 monitored← 1m52s · now · 1m8s →

alivethe-healthy-one~11s · 7s agoprodweb

alivea-busy-one~8s · 6s agoprodapi

alive · mutedthe-muted-one~20s · 8s agotest

alivethe-late-one~12s · 6s agoprod

latethe-failure~16s · 29s agoprod

alivethe-paused-one~15s · 3s agoprod

pausedthe-deploying-one~13s · paused (35s left of 1m)prodapi

Real services · live

Jørnal →