What to actually run on your home lab

You have a hypervisor running and a couple of virtual machines. Now what?

The answer that teaches you most is: run things people in your house actually use. Real users create real pressure, and that is where the learning is.

Here is a sensible order.

Start with something the household wants

1. Pi-hole or AdGuard Home

A network-wide ad blocker. Every device in the house benefits, including phones and smart TVs, with nothing installed on them.

Why start here: it is quick, the benefit is immediate and obvious to everybody, and it teaches you DNS, which is the single most useful networking topic there is. It also means the household notices when your lab goes down, which is exactly the pressure you want.

2. A media server

Jellyfin (free and open source) or Plex. Serves your own films, music and photos to televisions and phones around the house.

Teaches storage, transcoding, permissions and remote access. Popular with families, which buys goodwill for the noisy experiments later.

3. File storage

Samba shares, or something like Nextcloud if you want a full self-hosted alternative to Google Drive.

Teaches file systems, permissions and user management, and it gives you a genuine reason to care about backups.

Then the things that teach infrastructure

4. Docker and containers

Move from one virtual machine per service to containers. This is how most modern infrastructure is actually deployed, and it is the biggest single step in professional relevance.

Start by moving something you already run into a container.

5. A reverse proxy

Nginx Proxy Manager, Traefik or Caddy. Puts everything behind one entry point with proper names and HTTPS certificates instead of remembering port numbers.

Teaches DNS, certificates and how web traffic is actually routed. Genuinely useful professional knowledge.

6. Monitoring

Uptime Kuma is the easy start. Prometheus and Grafana are the professional version.

Then set up alerting so you find out something has broken before somebody in the house tells you. That transition, from being told to knowing first, is the whole difference between an amateur and a professional operator.

7. Backups, and a tested restore

Proxmox Backup Server, or restic to somewhere off the machine.

Then actually restore something. Delete a virtual machine and bring it back. Most people never test this, including in real workplaces, which is precisely why it is worth being the person who has.

Then the networking

8. Your own DNS server

Beyond Pi-hole. Real internal names for your machines.

9. VLANs and firewall rules

Segment the lab from the family network so an experiment cannot take down the house. Write rules that actually block something, then test that they do.

This is the topic that most separates people in interviews, and almost nobody self-taught has done it.

10. A VPN into your own network

WireGuard is the current answer. Reach your lab from outside without exposing anything directly to the internet.

Teaches encryption, routing and, importantly, why exposing services directly is a bad idea.

Then the interesting extras

11. Version control and automation

Gitea for your own Git server. Then Ansible to configure machines automatically rather than by hand.

The moment you can rebuild a machine from a script rather than from memory, you are working the way the industry works.

12. A local AI model

Ollama, running a language model entirely on your own hardware with nothing leaving the house.

Currently the most interesting thing to put on a lab. It teaches you what these systems actually are rather than what the marketing says, and it is genuinely private, which matters given what should not be pasted into a cloud chatbot.

The rule that matters more than the list

Run things people depend on.

A lab nobody uses is a sandbox, and you can rebuild it whenever you like with no consequences. That is comfortable and it teaches you far less.

The moment your sister cannot watch anything because you were tinkering, or the whole house loses internet because you broke DNS at nine on a Tuesday, you are learning the actual job: change management, rollback plans, maintenance windows, and communicating with users who are not interested in your explanation.

That is what the interview questions are about.

And document it

Keep a text file, a wiki, or a repository. What you built, why, what broke, what you changed.

Two reasons: you will forget, and it becomes the portfolio you talk about when applying for a first role.

If you get stuck

The step people most often stall on is the jump from running things to running them properly, with monitoring, backups and a network that is actually segmented.

That is where the home lab sessions are most useful, because it is the part with no obvious tutorial and the part employers ask about.