u/suoinguon

ClawPing: dead-man-switch monitoring for mini lab boxes without port forwarding

I built this around a failure mode that shows up a lot on small home lab boxes: the thing watching the machine often lives on the same LAN, or on the same machine, so when the box disappears the monitor disappears too.

ClawPing takes a narrower approach:

small Go agent on the mini PC / NAS / server
outbound HTTPS heartbeats only, so no public IP or inbound port exposure
Cloudflare Worker control plane with D1 for state, Durable Objects for alert dedupe, and Queues for Telegram delivery

It is not trying to be a full metrics stack. It is closer to a dead-man switch for private machines: missed heartbeats, stale backup markers, disk issues, and dead Docker containers go to Telegram.

Repo: https://github.com/cschanhniem/clawping

The design choice I am still tuning is where policy belongs. Right now the agent stays dumb and the control plane decides when silence becomes an alert. For people running tiny lab nodes, would you keep that split or push more logic back onto the box?

reddit.com

u/suoinguon — 11 hours ago

▲ 43 r/TelegramBots+4 crossposts

ClawPing - Cloudflare Workers watchdog for home servers, no public IP required

ClawPing is a Cloudflare Workers-first Telegram watchdog for home servers, mini PCs, NAS boxes, and self-hosted apps.

A tiny Go agent runs on your machine and pushes outbound heartbeats. If your server stops checking in, a backup goes stale, a disk fills up, or a Docker container dies, ClawPing alerts you through Telegram.

No public IP. No open ports. No self-hosted dashboard required, though there is a dashboard if you want it.

Stack: Cloudflare Worker + D1 + Durable Objects + Queues + Go agent.

GitHub: https://github.com/cschanhniem/clawping

Open source under MIT. Feedback welcome.

u/suoinguon — 2 days ago