Home Lab Setup Checklist
This checklist guides you through building a home lab for practising networking, Linux, Windows Server and security skills. It is for students and early-career engineers who want hands-on practice without risking a real network. It covers goals, hardware, hypervisors, network design, the VMs to build, tools, safety and documentation. Follow the sections in order, keep vulnerable machines isolated, and take snapshots so you can break things and recover quickly.
How to use this checklist
- Set your goals. Decide what you want to practise, because that sets how much RAM, storage and how many VMs you need.
- Choose hardware and a hypervisor. Start with the computer you already have and a free hypervisor before buying anything.
- Design the network before building VMs. Plan isolated and NAT networks and IP ranges first so vulnerable machines never touch your home network.
- Build, snapshot and document. Build one VM at a time, take a clean snapshot, and record settings and passwords in your lab notes.
0 of 43 checked
Goals and planning
Hardware options
Hypervisor options
Network design
VMs to build
Tools
Safety and legality
Snapshots, backups and documentation
Frequently asked questions
How much RAM do I need for a home lab?
16 GB is a comfortable start for a firewall and two or three small VMs; 32 GB or more lets you run Windows Server and several clients together.
Which hypervisor should a beginner use?
VirtualBox or VMware Workstation Pro on your existing computer is easiest. Move to Proxmox VE when you have a spare machine to dedicate to the lab.
Is it safe to run Metasploitable or DVWA at home?
Only on an isolated internal or host-only network with no route to your home network or the internet. They are deliberately insecure and would be easy to compromise.
Can I build a lab on a Raspberry Pi?
Yes for Linux and network services, but it uses an ARM processor, so it cannot run standard x86 VMs such as Windows Server or most firewall distributions.