Website: homebutler.dev
HomeButler is a single Go binary that keeps a snapshot of a home server and, on the next run, reports only what changed: a container that vanished, a new one that appeared, a port now answered by a different process, a disk that moved. Most homelab dashboards show the current state and leave the judgement to us; six containers before and six after is not “no change” when one of them is a different container. HomeButler exists for that gap. It needs no daemon and no database, and nothing runs on the machines it watches between runs — the binary is put there once and called over SSH.
It sits beside the tools already in a homelab rather than replacing them. Uptime Kuma answers “is it up”, Netdata or Beszel draws the graph, Dozzle shows the logs; HomeButler answers what is different since last time and whether it matters. Every change line names the kind of change, the thing it happened to and what happened, and the same words appear in the JSON output, so cron jobs and agents can branch on them without parsing prose. Run homebutler serve --demo to see the dashboard filled with sample servers.
inventory scan maps containers, app ports and system ports, links Docker-published ports back to their container, and exports a Mermaid diagram for docs or an agent.--strict makes it usable from cron.MIT. That is an OSI-approved permissive licence: use, modify and redistribute the code, including commercially, as long as the copyright notice is kept. The project states there is no account, no paid tier and no AI service required — the judgement rules are written down and the same input produces the same report.