DEV Community

How to Plan Homelab Hardware in 2026, Role by Role

Originally published at woitzik.dev

Disclosure: This post contains Amazon affiliate links (marked with *). As an Amazon Associate I earn from qualifying purchases. Buying through them costs you nothing extra.

This page is the planning layer above my buying guides. Each section answers one question for one role in the homelab, then points to the single article that does the detailed comparison. Product tables and spec lists live in those guides, not here.

View the complete homelab infrastructure source on GitHub

The Order That Matters

Plan in this order, not cheapest first. Compute without a network you control is a box on a flat LAN, and storage without a backup target is a single point of failure with extra steps.

  • Compute host (where VMs and containers run)
  • Network (router and firewall; retrofitting VLANs onto a flat network later is real work)
  • Backup target (before you have data worth losing)
  • Storage/NAS (once compute and network are settled)
  • Edge/DNS redundancy (once enough depends on name resolution that an outage hurts)
  • Power, cooling and rack (cheap, and the layer that decides whether everything above stays up)

Compute Host

Start with one mini PC running Proxmox. An Intel N100 box covers containers and a few light VMs; step up to a Ryzen mobile chip if you plan to run k3s with several nodes or local LLM inference.

Budget more attention for the SSD and RAM than for the CPU: those are what limit a single-host homelab first.

The model-by-model comparison, prices and NIC details are in Best Mini PC for Homelab 2026.

Storage and Backup

Buy the backup target first, even if it is only an external USB drive, and add a NAS later when you need shared storage with real redundancy. A drive attached to the same host protects against software mistakes and a dead SSD, not against losing the site, so plan an offsite copy as well.

The 2-bay NAS comparison is in Best NAS for Home Backup 2026, and the backup layering is in 3-2-1 Backup in Practice.

Network

Pick a router that can do VLANs and a default-drop firewall, and that you can manage as code if infrastructure-as-code is part of the point. For a homelab I would stretch the budget for the MikroTik RB5009* even at the starter level, because rebuilding a flat network into segmented VLANs later costs more time than the price difference.

The full comparison against Ubiquiti is in MikroTik vs Ubiquiti for Home Network 2026.

Edge and DNS

Once every service depends on local DNS, one resolver is a single point of failure for the whole network. Two small boards running the same resolver with Keepalived failover fix that cheaply, and they should stay on light, read-mostly duties because SD cards wear out under heavy writes.

The board comparison is in Raspberry Pi 5 Alternatives Compared 2026; the setup itself is in HA DNS for Homelab.

Power, Cooling and Rack

Check that the power supply can feed the host at full load, and measure wall draw with a plug-in meter such as the TP-Link Tapo P110* before blaming software for freezes. A closed rack needs exhaust airflow, and a small 10-inch rack is enough for a mini PC, a router and two Pis.

The rack, PDU and fans I use are covered in the hardware tour.

What I Run and Why

My whole homelab runs on one BMAX B5A Pro mini PC (Ryzen 7 5825U) as the Proxmox host, a MikroTik RB5009 as router and firewall, two Raspberry Pi 4B units for DNS, and a Seagate 2TB external HDD* as the backup and archive disk.

Every choice above comes from something that went wrong on that hardware:

  • The boot NVMe is a DRAM-less consumer drive. With no onboard cache, every write burst hits raw flash. That ruled out etcd, ZFS on the boot pool and Longhorn on this host, which is why the cluster storage moved to NFS (Longhorn to NFS) and why simultaneous guest boots had to be staggered (Staggered VM Boot). If you buy a mini PC, check whether the bundled SSD has DRAM before you trust it with VM disks.
  • The external power adapter was marginal. Under combined load it sagged, the CPU throttled, and ZFS deadlocked the whole host. The full chain is in The ZFS ARC Freeze. This is the reason power sits in the planning order above.
  • The USB port matters. The archive HDD reads at about 60 MB/s on a USB-3 port. On a USB-2 port it fell to roughly 3 to 13 MB/s, which turns a backup window into an all-night job. Check which ports on a mini PC are actually USB-3 before deciding where the backup disk goes.
  • One DNS resolver was not enough. The two Pis share a virtual IP via Keepalived, and stopping DNS on the standby during a recovery test had no effect on name resolution. Keeping them alive unattended is covered in Hardening Unattended Raspberry Pi Edge Nodes.

Budget Tiers

These tiers describe scope, not a fixed shopping list. Current prices are in each linked guide.

  • Starter: one N100 mini PC, a VLAN-capable router, and an external drive as backup target. This is already a useful homelab.
  • Serious: a Ryzen mini PC with enough RAM for k3s, a 2-bay NAS, and a second DNS node for failover.
  • Full rack: everything above in a closed rack with exhaust fans, a PDU, a power meter, and an offsite backup copy.

Where to Go Next

Role Detailed guide
Compute host Best Mini PC for Homelab 2026
Storage/NAS Best NAS for Home Backup 2026
Network MikroTik vs Ubiquiti for Home Network 2026
Edge/DNS Raspberry Pi 5 Alternatives Compared 2026
Rack, power, cooling Inside My Homelab: The Hardware Tour

For the Terraform, Ansible and Kubernetes configuration that turns this hardware into a working homelab, the full source is on GitHub, and the architecture writeup covers how the Ansible layer ties it together.

Frequently Asked Questions

Do I need a full rack to have a real homelab?

No. One mini PC, a router you understand and a backup drive is a working homelab. Racks, fans and redundant DNS solve problems you only notice once enough services depend on the setup.

What is the highest-value upgrade after the starter setup?

A second DNS node with Keepalived failover. When a single resolver goes down, name resolution for the whole network goes with it, and a second small board costs little compared to anything else on this list.

Should I buy used mini PCs or NAS units?

Used mini PCs are usually fine if you can check the SSD's wear and health data and replace the thermal paste. A used NAS is riskier because you inherit the drives' unknown history along with the enclosure, so I would buy that new.

Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.