Built by homelabbers,
for homelabbers

labwatch started because we wanted a monitoring tool that actually understands homelabs — not a watered-down enterprise solution.

Why labwatch exists

Enterprise monitoring tools assume you have a team, a budget, and homogeneous infrastructure. Homelabs are the opposite — a mix of Proxmox nodes, Docker containers, Raspberry Pis, and whatever hardware you found on eBay last week.

We built labwatch to be the monitoring tool we wished existed: a single lightweight agent that collects everything, a natural language interface so you can just ask what's wrong, and status pages you can actually share.

What we believe in

Open source first

The agent (MIT) and server (AGPL-3.0) are fully open source. Self-host for free, forever. No telemetry, no tracking, no vendor lock-in.

Simple by default

One binary, one command. No YAML configs to write, no dashboards to build, no queries to learn. Install it and it works.

Privacy respected

Your data stays on your infrastructure when self-hosted. Our managed service retains metrics for 48 hours only. We don't sell data.

Homelabs are real infra

Whether you're running media servers, game servers, or production workloads from home — your infrastructure deserves proper monitoring.

Tech stack

labwatch is built with boring, reliable technology.

Go (agent) Python / Starlette (server) SQLite (database) Chart.js (charts) Claude (NLQ engine) Vanilla JS (no framework)

Open source

labwatch is fully open source. The code is on GitHub — star it, fork it, contribute, or just read it to see how things work.

View on GitHub