Homelab project · November 2026
Homelab Intelligence: Knowing What Runs, Where, and What Changed
A self-hosted platform that keeps a record of what runs in my homelab, where it runs, how it connects, what changed and what needs attention. It is read-only by design, so it cannot change the systems it watches.
A dashboard of links is not the same as knowing your lab.
Link launchers show what you remembered to add. They do not tell you what changed last week, which guest has no working backup, or what depends on what. This project keeps that record.
It is deliberately not a link launcher; for that, it recommends an existing tool.
A monitoring tool should not be able to break things.
It reads Proxmox with a dedicated account that can look but not change anything. A bug, or a stolen session, cannot start, stop or reconfigure a single machine.
Research first, then milestones with acceptance reports.
The first commit is a findings and proposal document, not code.
Authentication, database, migrations, CI and container.
A way to describe what should exist, separate from what is discovered.
Ran in shadow mode for a week before being trusted.
Change timeline, storage findings, drift, dependencies and a network map.
Backup checks with fix playbooks.
What it shows.
What changed, when, across the lab.
Storage use and problems worth attention.
Differences from the declared inventory, and what depends on what.
A network map built from Proxmox and the declared inventory.
The rack view highlights a machine only when its backups are failing, with a playbook to fix it.
Checked on every change.
Collectors for Pi-hole, TrueNAS and other systems are planned but not built yet.