Decision Guide
These are starting points, not rules. If you already know why you want something else, go with that.
What should I buy?
Section titled “What should I buy?”- Do you have a spare PC or laptop? Start there and spend nothing. An old laptop even has a built-in battery backup.
- Do you mainly want quiet and low power bills? Get a used or new mini PC.
- Do you need lots of drives or PCIe cards? Build a custom tower.
- Do you need lots of RAM, remote management or real server hardware, and can you tolerate noise? Get a used server, and work out the power cost first.
- Do you only need it a few hours a month? Use a cloud lab or a nested lab on your desktop.
Which hypervisor should I run?
Section titled “Which hypervisor should I run?”- Does your job use a specific platform? Learn that one, if you can get it licensed.
- Are you only running containers? You may not need a hypervisor. Use a plain Linux server with Docker or Podman.
- Do you want the safe default? Use Proxmox VE.
- Are you coming from VMware or Citrix, and want a similar model? Try XCP-ng.
- Are you staying on your desktop? Use the desktop hypervisor for your OS.
More detail: Choosing a hypervisor.
Where should my data live?
Section titled “Where should my data live?”- One host, and just lab data? Use local NVMe.
- Family photos or other data you can’t replace? Keep it on a NAS or a separate pool with backups, away from lab experiments.
- Want to learn shared storage or migrate VMs between hosts? Add an NFS or iSCSI box, or use ZFS replication.
- Have three or more nodes and fast networking? Try Ceph or another hyper-converged option.
Do I need a rack?
Section titled “Do I need a rack?”Probably not. If everything you own fits on a shelf, use a shelf. Consider a rack when you have rack-mount gear or enough cabling to justify one. Small 10-inch racks suit mini PC labs well.
Should I open a port to the internet?
Section titled “Should I open a port to the internet?”No. Use a private VPN or mesh network instead. If something truly has to be public, read Securing a Homelab first.