Know what's lurking in your lab.
Local-first homelab inventory
LabRat reads what your network and hypervisors already know, then lets you place every device in a real location, area, and rack. Nothing moves until you say so.
- UniFi Network
- Proxmox VE
- NUT UPS servers
- MikroTik MNDP
See your lab the way it is cabled
Every screenshot is from an invented demo lab.
Read-only by design
It only reads
The collector never changes a controller's settings, logs in to a device to change it, or sends a UPS a command.
It stays in bounds
It contacts the controllers you connect and, beyond them, only the networks you allow in Settings.
Secrets stay put
Credentials live in a local config file, never in the database.
You decide where things go
What a scan finds stays separate from your inventory until you place it or link it.
What it reads
| Source | What LabRat gets | What it needs |
|---|---|---|
| UniFi Network | Switches, gateways, access points; ports, PoE, link state, and cables; clients, networks, Wi-Fi, firewall zones; WAN and VPN status | A read-only API key |
| Proxmox VE | Nodes, NICs, bonds, bridges, VLANs; guests; storage, drives, and Ceph; live load and memory | A read-only API token |
| Pi-hole | Queries, blocking state, history, and top domains and clients | An application password |
| Network UPS Tools | UPS status, load, battery, and runtime | Permission to scan their networks |
| SNMPv3 | NIC link state for Proxmox nodes | A read-only SNMPv3 user |
| MikroTik MNDP | MikroTik devices on the local segment | Nothing: it only listens |
Quick start
With Docker and Compose:
git clone https://github.com/dlenwell/labrat labrat && cd labrat
mkdir -p deploy/data deploy/config
export LABRAT_UID=$(id -u) LABRAT_GID=$(id -g)
LABRAT_ALLOWED_HOSTS=labrat.example.lan \
docker compose -f deploy/compose.yaml up -d --build
docker compose -f deploy/compose.yaml logs web | grep "setup code"
Open http://<host>:8000, choose First-time setup, enter the code from the log, then connect your controllers under Settings → Integrations. The setup guide covers running from a checkout, HTTPS, and upgrades.