Automation, Build Logs

Why I Built HexMap

July 6, 2026

The lab outgrew static diagrams and scattered dashboards, so HexMap became the live, agentless infrastructure map that shows what exists, where it runs, and what depends on what.

Original work date

July

The problem

The homelab reached the point where a service list was not enough. Infrastructure truth was spread across Proxmox, k3s, DNS, routes, backups, monitoring, storage, manifests, and notes. A dashboard could show what was red. A diagram could show what used to be true. A command could show one slice of reality. None of that showed the whole system.

The environment

What failed

None of the existing tools showed the whole system or stayed current as the environment changed.

The fix

HexMap was built to make the lab visible as a connected environment: hosts, VMs, containers, Kubernetes services, storage, tunnels, monitoring, and dependency paths in one live view. The important part is that it does not require agents or installs on tracked systems. It builds from live infrastructure sources so the map can stay current as the environment changes.

Final state

What I learned

If I have to check six places to understand one service, the map is already broken.

Useful commands / config

paste commands here