New to homelabs
Start here: building your first homelab
A homelab is the best classroom in technology: real equipment, real problems and nobody to blame but yourself. This page explains what a homelab is, how to begin without wasting money, and the order in which to read our guides.
Last updated
What a homelab is
A homelab is computing and network equipment that you own, run and control, usually at home, for learning and for running services yourself. It might be one old laptop running a hypervisor. It might be a closet of small PCs, a NAS and a managed switch. It might be a full rack in the basement. Size does not define it. What defines it is that it is yours: you choose what runs, you decide how it is built and you are free to break it.
Most homelabs grow into two things at once:
- A lab, where you experiment, learn new technologies and practice skills you can use at work.
- A small production environment, running services your household relies on, such as a photo library, file sharing, home automation and a password vault.
Keeping those two roles apart is one of the first lessons, and it shapes many of the recommendations on this site.
Why build one
- To learn by doing. Reading about VLANs, ZFS or automation is useful. Building them, breaking them and fixing them is how the knowledge sticks.
- To own your data. Photos, documents and notes on hardware you control, backed up the way you choose, rather than in services that change their terms.
- To build a career. A documented homelab is one of the most convincing things you can show an employer.
- Because it is fun. There is real satisfaction in a service you built running quietly for a year.
Principles to start with
These ideas run through every guide on this site. They come from years of running labs, and from mistakes we would rather you did not repeat.
- Fundamentals before tools. Learn addressing, DNS, the shell and storage basics; the tools change, the fundamentals do not. See Fundamentals Before Tools.
- Start small, grow with purpose. Add hardware when you can say what it is for.
- RAID is not a backup, and an untested backup is a hope. See Backup Strategy.
- Expose nothing you do not have to. Reach your lab through a VPN.
- Write it down as you go. Future you will be grateful.
What to buy first, and what not to
The best first server is usually one you already own. Before buying anything, try the hardware you have: an old desktop or laptop with 16 GB of memory runs a hypervisor and several services comfortably.
When you do buy, this order works well:
- A dedicated firewall. A small fanless box with two or more network ports. It lets you build proper networks and keeps the internet working when you break everything else.
- A managed switch with VLAN support. Eight ports is plenty to start.
- A hypervisor host with plenty of memory. A mini PC with 32 GB is our usual recommendation.
- Backup storage, before any service holds data you care about.
- Everything else when you need it, and not before.
Caution
Resist the free or cheap rack server until you have measured what it costs to run and heard how loud it is. Many people's first big purchase is the one they replace first. See The Real Cost of a Free Server.
Our Shelf Lab is a complete, quiet starter build along these lines, idling at about 50 W. For prices, running costs and whether self-hosting pays for itself, see Budgeting a Homelab.
Your first weekend
A focused first weekend gives you a working foundation instead of a pile of half-finished projects.
-
Plan
Write down two or three goals and an addressing plan. Choose the machine you will use.
Choosing hardware -
Install
Install a hypervisor, give it a reserved address and build a template VM.
Virtualization -
Run something
Deploy one service you will actually use, such as a DNS filter or file share.
Self-hosting -
Protect it
Back it up to a second device, restore a file to prove it works and write down what you did.
Backups
The first weekend checklist turns this into a list you can tick off. Prefer to skip the hypervisor and start with plain Linux and containers? Follow Your First Self-Hosting Weekend instead; Choosing a Platform explains the choice.
A reading path through our guides
Our guides are written to stand alone, but if you are starting from scratch, this order builds each idea on the last.
Stage 1: foundations
- Choosing Homelab Hardware
- Budgeting a Homelab
- Choosing a Platform
- Linux for the Homelab
- Virtualization
- Backup Strategy
Stage 2: the network
- Home Network Fundamentals
- Firewalls and Routing
- VLANs and Segmentation
- DNS, Domains and Certificates
- Remote Access and VPNs
Stage 3: storage and services
Stage 4: running it well
- Securing Your Homelab
- Monitoring and Logging
- Maintenance Routine
- Automation and Configuration
- Documentation and Technical Debt
- Troubleshooting
- Racks, Power and Cooling
- Out-of-Band Management
Mistakes almost everyone makes
- Buying too much, too soon. Hardware bought without a purpose becomes noise, heat and a power bill.
- Running everything on one box, including the firewall, so every reboot takes the household offline.
- Trusting data to a service before backing it up. Especially containers whose data location you never checked.
- Forwarding ports to admin pages and remote desktops "just for now".
- Copying commands without understanding them, then being unable to fix what they built.
- Not writing anything down. Every lab eventually needs to be rebuilt by someone who has forgotten how it works.
Every one of us has made most of these. The lab is the right place to make them, as long as you learn from them.
Where to go next
Browse all guides, pick a hands-on project, compare the three reference builds, keep the glossary open for unfamiliar terms, and check the FAQ for quick answers. Welcome to the hobby.