A homelab build planner built for real homelab constraints.
HomelabConfig keeps the interface clean and familiar — like PCPartPicker — while focusing the data model on what homelab builders actually need: parts, power draw, drive bays, networking, rack space, and room to grow.
Our approach
Homelab planning should be as straightforward as building a PC. The complexity is in the constraints — power budgets, rack space, noise levels — not in the interface. The homelab builder puts those constraints front and center.
Why HomelabConfig?
Existing tools either oversimplify (spreadsheets) or overcomplicate (enterprise DCIM). HomelabConfig is purpose-built for the homelab community — start with a starter template, browse the part categories, and build from there.
Frequently Asked Questions
What is HomelabConfig?
HomelabConfig is a homelab build planner — a PCPartPicker-style tool built specifically for homelab servers, NAS boxes, network gear, and rack builds. It covers compatibility checking, power budgeting, drive bay planning, and rack space so you can design the whole system before buying anything.
Is HomelabConfig like PCPartPicker for homelabs?
That is the closest comparison. PCPartPicker is focused on consumer desktop builds. HomelabConfig models the constraints that matter in a homelab: idle power draw, drive bay count, rack unit space, noise targets, VLAN-capable networking, and UPS sizing. The interface is intentionally familiar but the data model is built for homelab workloads.
What homelab builds does it support?
It covers the full range: single-board NAS builds, multi-drive ZFS servers, Proxmox virtualization nodes, pfSense or OPNsense network cores, and mixed racks with multiple systems. The builder scales from a single server and switch to a full rack with separate compute, storage, and network tiers.
Does it cover quiet builds?
Yes. The templates and planning categories include noise, airflow, and idle-power considerations from the start. The quiet rack guide covers how to check these constraints before buying rack hardware.
Can I use it for a small NAS or a full rack?
Both. The layout is meant to scale from a single server and switch to a multi-system rack with dedicated storage and backup tiers. Start with a template that matches your use case and expand from there.