Self-hosted homelab and AI rig dashboard in one Docker container with GPU VRAM attribution, power costs, SSH polling, and a read-only MCP server.
SikamikanikoBG created HomeLab Monitor after a home cluster grew from a few Linux boxes into a multi-GPU AI rig where standard dashboards could not explain which local model held VRAM or how much electricity each inference job burned. Written in Python and shipped as a single Docker container backed by SQLite, it unifies hardware telemetry, container controls, power accounting, and a read-only Model Context Protocol server without node agents.
Platforms like Datadog, New Relic, Paessler PRTG, and SolarWinds price tiers around host agents, sensor counts, or metric volume—models that punish operators running GPU workstations, NAS boxes, and Raspberry Pi nodes. Even when engineers assemble Prometheus and Grafana themselves, they still stitch together multiple exporters just to see which container or LLM process pins a graphics card. HomeLab Monitor replaces that stack with one container on port 9800 that polls Linux, Raspberry Pi, and Windows machines over SSH using Python 3 or PowerShell probes.
Its integrations target local AI and homelab operations rather than enterprise APM tracing. The hub recognizes over 30 model servers—including Ollama, vLLM, llama.cpp, and Automatic1111—attributing VRAM across multi-card rigs down to the active model and caller. A built-in read-only MCP server on port 9810 exposes 19 tools so Claude, Claude Code, or local agents can query host health, disk treemaps, and GPU load, while /metrics feeds Prometheus and alerts route to Discord, Telegram, and ntfy.sh.
9810, letting Claude Code or any MCP client diagnose VRAM pressure, runaway logs, or container RAM usage without write access.nvidia-smi throttle reasons, clocks, and fan speeds alongside Linux amdgpu sysfs metrics and Windows GPU counters, mapping VRAM across 30+ model servers.9800 nor the MCP endpoint on port 9810 includes user login, so the container must stay behind a trusted LAN, firewall, or VPN./var/run/docker.sock and the systemd socket read-write; read-only mode requires ENABLE_CONTROLS=0 and ALLOW_SELF_UPDATE=0.llama.cpp rigs who want VRAM fit benchmarks, watt-hour costs, and throttle visibility on one screen.Does HomeLab Monitor require installing agents on remote servers? No. You paste the hub's SSH public key onto each target Linux, Raspberry Pi, or Windows host, and the hub streams a Python 3 or PowerShell probe over SSH.
How does HomeLab Monitor compare to Datadog or Paessler PRTG? Datadog and Paessler PRTG target enterprise networks with per-host or per-sensor licensing, distributed APM, and SNMP polling. HomeLab Monitor is a free container built for GPU telemetry, local LLM servers, power costs, and MCP queries.
Does HomeLab Monitor work with AMD and Intel GPUs, or without a GPU?
Yes. GPU panels light up for NVIDIA via nvidia-smi, AMD on Linux via kernel amdgpu sysfs, and AMD or Intel on Windows, while staying hidden on CPU-only nodes.
HomeLab Monitor is a practical, zero-cost alternative to heavyweight observability stacks for developers running local AI models and home servers. Distributed under the MIT license and actively maintained through November 2026, it packs GPU diagnostics, power accounting, and an MCP server into one container. Keep it on a private VLAN or VPN, and add a log stack only if you need distributed tracing.
Go, gRPC and Protobuf done right, LLM agents in production, and the hard parts of shipping a first product.
Show that HomeLab Monitor is listed as an open-source alternative. Paste into your README: