Home-network monitor

Every business system earned a health dashboard. The one thing all of that remote work actually depends on, my home network, did not have one. When the connection got flaky I was guessing, power-cycling, and hoping. So I pointed the same instinct at it. Instrument the thing, publish the read.

How it works

I aimed the existing monitoring pattern at UniFi. A scheduled read pulls network health from the UniFi controller and renders it into a dashboard on the identical build-and-publish rails as everything else. Python build, Cloudflare-hosted page, scheduled on the mini. It is the same shape as the performance and housekeeping dashboards, with a different data source plugged into the front.

Where it stands

Live, and low-stakes by design. It exists mostly to prove that "instrument it and publish the read" has become a reflex instead of a project. Something I do in an afternoon, not something I scope for a week.

This is the whole bet in miniature. Once the road is built (an always-on host, a publish pipeline, a dashboard convention), a new monitor is a data source and an afternoon, not a hire. An org chart grows by headcount. This one grows by config, which is exactly why one owner can keep adding seats without adding people.