Homelab / Guide

Building your homelab: where to start

What a homelab is, what you can do with one, three ways to get started depending on your needs and space, what people often forget, and the rules for keeping things simple.

Homelab Guide Beginner Published October 20, 2026 Translated November 20, 2026 10 min read Version française
A rack of network equipment lit up in a dark room
Photo: Tyler on Unsplash

A homelab is a "laboratory at home": one or more machines running at your place to learn, test and host your own services. It can be anything from a Raspberry Pi sitting behind the internet router to a server rack in the garage.

You don't need new hardware to get started. This guide helps you choose a suitable starting point, and avoid the mistakes that waste time or electricity.

1. What is a homelab for?

Three reasons come up most often, and they combine very well:

  • Learning: installing a hypervisor, building a network, breaking things and fixing them, with no risk to a production environment.
  • Taking back control of your data: photos, files and passwords hosted at home rather than with a cloud giant.
  • Being useful at home: blocking ads across the whole network, centralising films, automating the smart home.

2. What you can do with it

Some of the most popular services, all free and open source:

Need Service What it replaces
Backing up and sorting photos Immich Google Photos, iCloud Photos
Films, series and music Jellyfin Plex, a drive plugged into the TV
The family's passwords Vaultwarden (Bitwarden-compatible) An online password manager
Files, calendar, contacts Nextcloud Google Drive, Dropbox
Home automation Home Assistant Each manufacturer's app
Blocking ads across the whole network Pi-hole or AdGuard Home A blocker on every device
Checking that everything is working Uptime Kuma Usually nothing

Most of them install in a few minutes as containers (Docker or Podman): one configuration file, one command, and the service is running. See rootless containers with Podman and Quadlet for a clean method.

3. Three ways to get started

Small Intermediate Ambitious
Typical hardware Raspberry Pi 5, or an old laptop Mini PC (Intel N100 or equivalent), plus a NAS if needed Refurbished tower or rack server, or several machines
Idle power About 3 W 6 to 15 W 50 to 150 W, sometimes more
Noise and heat Silent Silent to quiet Audible fans, a dedicated room recommended
Space A shelf A shelf A cupboard, a garage or a rack
What it can run A few light services (ad blocker, home automation, small apps) A hypervisor with several VMs and a dozen containers A real cluster, many VMs, enterprise-style tests
For whom Discovering with no risk Most people, including professionals who want a serious lab Those who want to reproduce an enterprise environment

The best first homelab may be asleep in a cupboard

An old laptop or desktop PC sleeping in a cupboard is enough to learn. Add memory and an SSD if needed (see choosing an SSD), and you'll quickly find out what you really lack before buying anything.

The intermediate option is the best compromise for most people: a recent mini PC uses as much power as an internet router, makes no noise and easily runs a hypervisor such as Proxmox VE with several virtual machines.

4. What people often forget

Power consumption

A homelab runs 24 hours a day: idle consumption matters far more than maximum power. The energy used over a year is calculated like this:

consumption in W × 8,760 hours ÷ 1,000 = kWh per year

Orders of magnitude measured at idle:

Machine At idle Per year
Raspberry Pi 5 3 W 26 kWh
Intel N100 mini PC 7 W 61 kWh
Old small-form-factor desktop PC (8th-generation Core i5) 15 W 131 kWh
Small tower server 70 W 613 kWh
Refurbished rack server, disks included 100 W 876 kWh

Consumption rises when the machine is working, and each hard drive adds about 5 W. To find out what your machine uses, plug it into a plug-in power meter for a day.

Warning

At idle, a refurbished enterprise server uses up to 20 times more power than a mini PC, and it does so all the time. Measure its real consumption before making it your lab's main machine.

Heat and noise

A rack server is designed for an air-conditioned room, not a living room: you can hear its fans through a door. A mini PC goes unnoticed.

Time

Each service you install needs updates, backups and a little monitoring. Three well-maintained services are better than fifteen abandoned ones.

5. The 5 golden rules

  1. Start small. One service at a time, which you understand before moving on to the next.
  2. Back up from day one. A homelab is for breaking things: your data mustn't break. Apply the 3-2-1 rule, for example with restic.
  3. Expose nothing to the internet at first. No port forwarding on the router until you've mastered security. To reach your lab from outside, a VPN such as WireGuard is the safe solution.
  4. Keep the lab separate from the family network. A dedicated VLAN stops a failed experiment from cutting off the internet for the whole house (see understanding VLANs).
  5. Document everything. IP addresses, passwords (in a manager), what each machine does: in six months, you'll have forgotten.

6. The roadmap

A progression that works, step by step:

  1. Choose the machine: start from what you already have, or a mini PC.
  2. Install the base: a hypervisor (Proxmox VE) if you want several virtual machines, or Debian directly to keep it simple. The essential Linux commands are enough to get started.
  3. Secure access: accounts, updates and key-based SSH access.
  4. Install a first useful service, for example an ad blocker for the whole house.
  5. Set up backups, and only then add the next services.

The guides and tutorials for each step are in the Homelab and Virtualization themes.

Key points

  • A homelab can start with an old PC: learn first, buy later.
  • A low-power mini PC is the best compromise for most people.
  • Idle consumption matters more than power: from 3 W to over 100 W depending on the machine, 24 hours a day.
  • Back up from day one, expose nothing to the internet at first, and document everything.

Read next