[ pulse ]
heartbeats in, status out · history nobody can edit
NEW STATUS PAGE
monitoring, inverted: nothing here probes your machines. your cron jobs, backups and services curl a private heartbeat URL into the enclave on their own schedule — the page turns red when the beats stop.
- each monitor gets a beat URL only you hold — end a cron line with one curl and it's monitored
- status derives from arrival times alone: waiting → up → late → down; grace covers slow runs
- the beat log lives in attested code and enclave RAM — nobody, including whoever hosts this page, can backfill a missed beat or edit history
- fits the enclave exactly: beats come in, nothing dials out; a page dies after 30 idle days
PAGE IS UP
the public status page — share it freely, it never shows beat URLs:
your owner link — the part after # is the only way to add monitors and read beat URLs back. keep it private:
connecting…
#……
owner link invalid — showing the public view.
owner view — beat URLs are readable below. keep this link private.
ADD A MONITOR
the new monitor's beat URL — put this at the end of your cron job / backup script:
NOTHING HERE
this status page never existed, or went 30 days with no beat, no edit and no viewer, and was swept. the server can't tell you which — pages leave nothing behind.