Your bot can’t tell you it’s dead.

ClawBeat doesn't connect to your bot from the outside — your bot reaches out to us. A tiny heartbeat agent runs inside your bot's process and sends a POST request to our server every 60 seconds. If those requests stop, we know something's wrong. This works even if your bot binds to localhost with no open ports.

Almost nothing. Each heartbeat is an empty POST request with a bearer token — roughly 100 bytes. No logs, no prompts, no conversation data, no environment variables. Your platform and version are stored once at registration, not sent per heartbeat.

Both require your bot to expose an HTTP endpoint they can ping from the outside. Most Claw bots bind to localhost — there's nothing to ping. Uptime Kuma also needs you to self-host another service, which creates a recursive monitoring problem. ClawBeat uses push-based heartbeats, so it works with any bot regardless of network config.

3 minutes. Your bot sends a heartbeat every 60 seconds. If we don't hear from it for 3 consecutive minutes, you get an email. When the bot comes back online, you get a recovery notification too. There's a 5-minute grace period on new bots so you don't get false alerts during setup.