Assembly manual
The Build Order
Every guide on this site, arranged as the 119 steps you'd actually take building a homelab from nothing. Start at step 1 and work down, or jump to the phase you're on — the page remembers what you've finished.
Jump to a phase
- 1Understand what you're building
- 2Plan & prep
- 3Install the base
- 4Create your first workloads
- 5Set up networking
- 6Reach it from anywhere
- 7Protect it
- 8Serve apps the right way
- 9See what it is doing
- 10Set up shared storage
- 11Run real services
- 12Build a media server
- 13Automate your media
- 14Remember what you built
- 15Go further
- 16New on the bench
Understand what you're building
Brand new? Start here — what a homelab actually is, and why it's worth building.
Plan & prep
Pick the right hardware, choose a switch, and make a bootable USB — before you touch a keyboard.
Install the base
Install Proxmox, lock it down, understand your storage options — and learn the storage failures to design against from day one.
Create your first workloads
Learn the difference between a container and a VM, then build one of each.
Set up networking
Configure container networking, set up network-wide DNS with Pi-hole, add a firewall, and wall off your IoT gadgets with VLANs.
Reach it from anywhere
Install Tailscale so you can manage the whole lab securely from any device, anywhere — then learn to debug the four ways homelab networks quietly break.
Protect it
Set up automated backups, measure how fast they actually restore, quiet the every-backup emails without losing failure alerts, add a UPS-triggered safe shutdown, and make sure backups reach offsite before you run services you care about.
Serve apps the right way
Run Docker, learn Compose once, keep your stacks updated and backed up, then put every service behind clean HTTPS URLs with a reverse proxy.
See what it is doing · I
Start with dead-simple up/down alerts, then add deep metrics and dashboards for the whole cluster — use that history to answer what happens when a node dies, fold every alert into one daily email you'll actually read, and keep the rescue runbook for the day a service does.
See what it is doing · II
Start with dead-simple up/down alerts, then add deep metrics and dashboards for the whole cluster — use that history to answer what happens when a node dies, fold every alert into one daily email you'll actually read, and keep the rescue runbook for the day a service does.
Set up shared storage
Give every service one central place to read and write files — the backbone your photos and media server depend on.
Run real services · I
The payoff — a smart-home hub, private photo backup, a knowledge base, password manager, local AI, and an autonomous agent. Then put it all on one dashboard.
Run real services · II
The payoff — a smart-home hub, private photo backup, a knowledge base, password manager, local AI, and an autonomous agent. Then put it all on one dashboard.
Build a media server
Pick Plex or Jellyfin, install it, keep playback smooth on modest hardware, keep the library tidy, and reach it from anywhere.
Automate your media
The *arr stack, then a request page for the whole house: someone taps Request and it downloads, files itself, and appears in your library — and keeps healing itself when it breaks.
Remember what you built · I
Document your homelab in a Git-backed knowledge base so you never solve the same problem twice — and so your AI tools can read it too.
Remember what you built · II
Document your homelab in a Git-backed knowledge base so you never solve the same problem twice — and so your AI tools can read it too.
Go further · I
Scale to a multi-node cluster, put it into code, run a game server, or build a native control app.
Go further · II
Scale to a multi-node cluster, put it into code, run a game server, or build a native control app.
New on the bench · I
Fresh guides that haven't been slotted into the roadmap yet — the newest builds land here first.
New on the bench · II
Fresh guides that haven't been slotted into the roadmap yet — the newest builds land here first.
END OF MANUAL
Rack's full. Now it evolves.
New field notes ship as the lab grows — and the copy-paste scripts for everything above live in the playbooks.