On this page
Building a homelab on Proxmox VE can feel like standing in front of a wall of disconnected tutorials — one for installing, one for networking, twelve for whatever an LXC is — with no sense of which comes first or why. This guide is the map. It walks the whole journey in the order you should actually do it — from choosing hardware to running your first self-hosted services — and links each step to a full, standalone walkthrough. You’ll never be told “just do X” without a guide that shows you how.
Think of it as a table of contents for an entire homelab. Read it top to bottom the first time to see the shape of the whole thing; come back to it later as the hub you navigate from.
I built the lab this describes one wrong turn at a time — this map is the one I wish someone had handed me. Today it’s four mini PCs running everything my household and my work actually depend on, but the sequence below is deliberately the order that would have saved me the most backtracking. If you take one thing from it: get a single node stable and backed up before you let the clustering rabbit hole pull you in.
The homelab, in three layers
Every durable homelab is built the same way: a foundation you install once and rarely touch, a core platform that makes it safe and reachable, and the services — the actual reason you built any of it. Each layer rests on the one below it.
The rest of this guide follows those layers from the bottom up.
Layer 1 — Foundation
This is what you set up once. Get it right and stable, and everything above it just works.
Start with the why. If you’re not sure what a homelab even is or whether you need one, read What Is a Homelab? first — it frames the whole project so you buy and build for your goals instead of copying someone else’s rack.
Pick hardware to match. You don’t need a server. A single mini PC with 16–32 GB of RAM runs a remarkable amount. The Homelab Hardware Guide covers what actually matters (RAM, cores, NIC, power draw) and what to ignore, and the Homelab Network Switch Guide covers the one piece of networking gear worth thinking about early.
Install Proxmox. Write the ISO to a Ventoy USB and follow Installing Proxmox VE from USB to first login. From there you’ll decide how to carve up the machine — the VM vs LXC guide explains the single most common choice you’ll make, and Creating Your First LXC Container and Creating Your First VM are the two hands-on starting points.
Cluster only when you have a reason. One node is a complete homelab. If you later want live migration or zero-downtime maintenance, Proxmox Cluster Setup walks through quorum and node joining, and Building a 4-Node Cluster on HP EliteDesk Mini PCs is a real-world build.
The most common beginner mistake is buying a cluster’s worth of hardware before running a single service. Get one node solid, run something real on it, and let your actual usage — not a YouTube rack tour — decide what you add next.
Layer 2 — Core platform
This layer turns “a machine running Proxmox” into a homelab that’s reachable, safe, and recoverable.
Networking. Give your containers and VMs stable, predictable addresses. Proxmox LXC Networking covers bridges, VLANs, and static IPs — the plumbing every service sits on. Add Pi-hole for network-wide DNS and ad blocking, which also lets you resolve your own services by name.
Storage. Decide where data lives before you fill it. The Proxmox Storage Guide compares LVM, ZFS, NFS, and Ceph, and Homelab NAS with Samba Shares sets up a central file server that every other service can read from.
Security. Lock down access before you expose anything. Proxmox Security Hardening raises the bar without making admin painful, and the Proxmox Firewall Guide adds rules and zone isolation. Store the credentials you generate along the way in your own Vaultwarden password manager.
Backups — do this early. Proxmox Backup Server gives you deduplicated, incremental, automated backups of every VM and container. Set it up before you depend on anything, and test a restore so you know it works.
It’s a hopeful guess. The only way to know your backups work is to restore one. Do it once, on purpose, while nothing is on fire — so that when something is, you already know the drill.
Layer 3 — What you actually run
With a stable foundation and a safe platform underneath, the fun part is almost anticlimactic — services become quick to add, because all the hard questions (where does data live? how do I reach it? what happens if it breaks?) were answered a layer ago. Pick whichever cluster of services matches why you built the lab in the first place.
Media. Automate a full media library: the Arr stack explained, deployed with Docker Compose, automated end to end, and made bulletproof in The Self-Healing Arr Stack. Serve it with Plex or Jellyfin, and back up your photos with Immich.
Monitoring. Know when something breaks. Start with Uptime Kuma for instant up/down alerts, then add deep metrics with Prometheus and Grafana and node/PVE exporters. Pull it all onto one screen with a Homepage dashboard.
Remote access. Reach your lab from anywhere without opening ports, using a Tailscale Subnet Router or an exit node. Put public-facing services behind Traefik with Let’s Encrypt for clean HTTPS.
Apps and AI. Run Home Assistant for smart-home control, a self-hosted LLM cluster with Ollama behind Open WebUI, or even your own Hermes AI agent. New to containers? Your First Docker Compose Stack is the pattern nearly all of these use.
How to use this guide
You don’t have to build every layer before you get value — you need each layer below whatever you’re adding. Want a media server this weekend? You still need a node (Layer 1) and somewhere to put the files (Layer 2 storage) first. This ordering is why the guide is shaped the way it is: every service you’ll ever add already has its prerequisites sitting underneath it.
Bookmark this page and treat it as home base. Each linked guide stands on its own, but they all fit into this one map.
Related posts:
- What Is a Homelab? — the “why” before the “how”
- Installing Proxmox VE — the foundation everything else builds on
- Proxmox VM vs LXC: When to Use Each — the choice you’ll make for every workload
- Proxmox Backup Server — the safety net to set up early
- The Self-Healing Arr Stack — a flagship example of a service done right
- Proxmox Monitoring with Prometheus and Grafana — know when something breaks
- Tailscale Subnet Router — reach the whole lab from anywhere
Sources: Proxmox VE Administration Guide, Proxmox VE documentation, Proxmox Backup Server documentation.
Comments
Comments are powered by GitHub Discussions — sign in with a GitHub account to join the conversation.