Skip to content
ProHomeLab
RU

Self-Hosting

How to Start a Homelab - Hardware, Hypervisor, and Your First Service

Stilicho2011Updated 6 min read72 views

Also available in: RU

Part 8 of 24 in the series Self-Hosting
  1. Pros and Cons of Fedora Server 42
  2. Linkwarden Overview - A Modern Self-Hosted Bookmark Manager
  3. PostgreSQL and pgAdmin in Docker - Beginner Setup Guide
  4. Mealie Recipe Manager - Self-Hosted Meal Planning on Docker
  5. Vaultwarden in Docker - Your Own Password Vault, Not Bitwarden's
  6. Diun - Get Notified When Your Docker Images Have Updates
  7. How to Upgrade Linux Server Distributions
  8. How to Start a Homelab - Hardware, Hypervisor, and Your First Service
  9. The Best Self-Hosted Apps of 2025 - A Personal Roundup
  10. Best Bookmark Manager - Linkwarden or Karakeep
  11. BookLore - A Self-Hosted Library and Reader for Your Book Collection
  12. Grimmory - A Self-Hosted Library and Reader for Your Book Collection
  13. Pangolin Tunnel Setup - Expose Homelab Services Without Ports
  14. NetBird Self-Hosted - Mesh VPN Without Port Forwarding
  15. Postiz - Trying to Automate YouTube, VK, and RuTube, and Why Only One Out of Three Actually Works
  16. Connecting Applications to a Shared PostgreSQL and Learning Basic Maintenance - Part 2
  17. Dozzle - A Convenient Real-Time Log Viewer for Docker Containers
  18. Docker Hit Its Network Limit - How I Diagnosed and Fixed It with default-address-pools
  19. Gotify - Your Own Push Notification Server for the Hypervisor and Beyond
  20. Forgejo + Komodo - Turning Docker Compose into GitOps
  21. GitOps for Homelab - Deploying Forgejo and Komodo From Scratch
  22. GitLab, Gitea, and Forgejo. A Comparison for Grown-Ups - What Actually Fits Your Homelab
  23. Auto-Updating Docker Containers - Renovate + Forgejo + Komodo
  24. Matrix Synapse - Setting Up Your Own Server for Decentralized Chat
Contents

What is a homelab?

A homelab is your own small-scale infrastructure at home: one or more servers, a network, and a set of services you deploy, configure, and babysit yourself. Think of it as a scaled-down version of a company server room that lives in your closet, on a shelf, or under your desk. Homelabbing is the act of building it - and then tinkering with it forever.

It usually starts with one old computer and one service. Where it ends is a question nobody has answered yet.

Why bother?

Everyone has their own reasons, but three come up again and again:

  1. Learning by doing. Reading about VLANs, reverse proxies, or clustering is one thing. Setting them up and then fixing them after you broke them yourself is something else entirely. A homelab is where a mistake costs you an evening, not the whole company's workday.
  2. Your own services instead of someone else's cloud and subscriptions. Password manager, file storage, photos, media library, smart home - all of it can live on your hardware. Your data stays yours, and a stack of monthly subscriptions gets replaced by hardware you may already own.
  3. Experience you can actually show. If you work in IT or DevOps, a homelab is hands-on infrastructure experience you can talk about in an interview in real detail - not just a "familiar with Docker" line on your resume.

Actually starting - a first-homelab checklist

Reading about homelabs and starting one are two different things, and the gap between them is usually just a handful of decisions. Here's the order I'd make them in:

  1. Use the hardware you already have, first. An old laptop, a retired office PC, anything with 8+ GB of RAM will run a real homelab. Don't buy anything until you've hit a wall with what you've got. The one thing to keep in mind from day one is power: a server runs 24/7, and an old tower PC can easily draw several times more than a modern mini-PC even when it's doing nothing. When you do go shopping, a low-power mini-PC or SBC is plenty for one or two people's worth of services (I've reviewed one such box, the ZimaBoard 2, power draw included).
  2. Put a hypervisor on it, not a desktop OS. Proxmox VE is the default recommendation for a reason: it's free, runs VMs and lightweight LXC containers side by side, and lets you tear down and rebuild a test environment in minutes instead of reinstalling an OS. There are alternatives too - XCP-ng, for example (I run it on a separate test box and used it in my Vinchin review). VMware ESXi is a much rarer pick for home use these days: since Broadcom bought VMware, the terms for the free version have changed more than once. And VirtualBox and friends are desktop virtualization - fine on your laptop, not what you want on a box that runs around the clock.
  3. Pick one service you actually want, not ten. The classic failure mode is spinning up a dozen containers over a weekend and never touching half of them again. A password manager you'll use daily - Vaultwarden, for instance - is a better first project than a media server you might open twice a month, precisely because you'll notice immediately if it breaks. Plain Docker is enough to start with; once you get curious how it stacks up against Podman and Kubernetes, I've got a separate comparison.
  4. Back it up from day one, not "later". If your first service is a password manager, losing it isn't "my experiment broke" - it's "I'm locked out of everything". A VM snapshot on the same disk is not a backup: when the disk dies, the snapshots die with it. The bare minimum is a regular copy of your data on a different drive, and ideally the 3-2-1 rule (three copies, on two different types of media, one of them off-site). There's no shortage of tools: Proxmox Backup Server for whole VMs and containers, Zerobyte or Duplicati for files.
  5. Don't expose services to the internet by forwarding ports. The most common - and most dangerous - beginner mistake is opening a port on the router so you can reach a service from outside. Scanners find those ports within hours. The simpler and safer way to reach your stuff from anywhere is a private network between your devices - NetBird, for example - without publishing anything at all. And if something genuinely has to face the internet, put it behind a reverse proxy with authentication (Traefik plus Authentik) and something like CrowdSec watching the door.
  6. Expect to break something, on purpose or not. The whole point of a homelab is that breaking a container, a network config, or an entire VM costs you an evening, not your job. Snapshot before you touch anything important, then go poke at it without the fear you'd have on a production system.
  7. Only then start layering on the rest - a second host, network segmentation, monitoring. You'll want all of it eventually, but none of it is what turns a pile of hardware into a homelab. The one service you actually use every day is.

What my homelab looks like today

To give you an idea of where all this can lead, here's what my homelab is made of right now:

  • Network. A router running OPNsense on dedicated hardware, with GeoIP blocking, FireHOL blocklists, and CrowdSec, and the network split into VLAN segments. I've also written up the pros and cons of virtualizing your router.
  • Virtualization. A Proxmox VE cluster, plus a few standalone hosts for workloads I'd rather keep away from the main cluster.
  • Getting in. Traefik in its own LXC container and its own VLAN as the single entry point, and Authentik for single sign-on across services.
  • Deployment. Every service's compose file lives in git, and Forgejo and Komodo roll changes out to the right hosts on every git push.
  • Storage and backups. A self-built NAS on OpenZFS and Proxmox Backup Server.
  • Notifications. Every infrastructure event - backups, CrowdSec bans, services going down - lands in Gotify, well away from my personal messengers.

Where to go next

If your first service is up and you're itching for more, these are the logical next reads on the site:

  • a Proxmox cluster - for when one host stops being enough;
  • Traefik in LXC and Authentik - for when you have more services than ports and passwords you're willing to remember;
  • OPNsense - for when you want to take control of the home network itself;
  • Forgejo and Komodo - for when you're tired of editing compose files by hand on the server.