What Is a Homelab? The Beginner's Guide (What It Is, What You Need, and Your First Five Projects)

CodexFuse Team · 2026-11-03T05:47:41.346Z · 13 min read min read

A homelab is a computer lab at home for learning servers, networking, and self-hosting. Here's what you need, real 2026 costs, and your first five projects.

What Is a Homelab, Exactly?

A homelab is a small computer lab you run in your own home: one or more machines you control, where you install servers, experiment with software, break things on purpose, and learn how infrastructure actually works. It can be a single old laptop in a closet, a used mini PC behind your TV, or a quiet rack in the basement — the defining feature is not the hardware, it is that you can experiment, document the result, and recover when something breaks.

Most people build a homelab for one of four reasons: to learn Linux, networking, and virtualization hands-on; to self-host services (media, files, backups, automation) instead of renting them; to take back privacy by keeping data at home; or to sharpen skills that matter in an IT career. If you are mapping the whole idea out before buying anything, our Self-Host Planner walks you through picking apps and checking server fit.

Why Do People Build a Homelab?

The short answer: production is expensive, but learning in production is more expensive. A homelab is a sandbox where the consequences of a mistake are zero — delete the wrong VM, misconfigure DNS, let a backup job run wild — and you just restore and learn. That freedom to break things is the entire point.

The practical answer is control. Every month you pay for cloud storage, a password-manager subscription, a photo-backup plan, or a media service, you are renting back access to your own data. A homelab moves those workloads onto hardware you own. Nobody changes the terms of service on your basement server.

The career answer is reps. Reading about VLANs, Docker, or reverse proxies is not the same as configuring them at 11 p.m. with a real switch and real logs. Employers cannot verify your reading; they can see a working stack you built, documented, and maintain. A homelab complements production experience — it never replaces it — but it is the closest thing to it you can own.

And the honest answer: it is fun. There is a specific satisfaction in opening a dashboard you run yourself and watching your own uptime graph climb.

What Do You Actually Need to Start?

Far less than the internet makes it look. A homelab does not have to be a rack of loud enterprise gear; the community consensus is to start with hardware you already own. The classic beginner setup is one spare machine, a wired network connection (Ethernet beats Wi-Fi for servers), and an evening to install Linux on it.

Before buying anything, inventory what you have: an old laptop, a retired desktop, even an external drive for backups. The only real requirements for a starter lab are a machine you can reinstall without panic, enough RAM to run a few services (8 GB is comfortable), and storage that does not already hold the only copy of your family photos.

Here is the honest budget ladder, from free to serious, with the 2026 price bands our researchers verified this month:

Two warnings from the current market. First, Raspberry Pi 5 prices are volatile: after a fourth price hike in November 2026, the 16 GB model lists at $385 — a used mini PC is often cheaper and faster. Second, Intel discontinued the NUC line in 2023 (ASUS continues it), so used NUCs are bargains, but buy from sellers with return policies.

Old Laptop vs Used Mini PC vs Raspberry Pi: Which Should You Pick?

The three starter machines each win at something different. Here is how they compare for a first homelab:

Power is worth a moment because it is the cost nobody budgets. A used business mini PC idles around 11–15 watts; an old desktop tower can draw 60–150 watts or more running all day. At one watt of continuous draw equaling about 8.76 kWh per year, the gap between a 12 W mini PC and a 70 W tower is real money on your electricity bill every month.

The rule of thumb: start on the old laptop, upgrade to a used mini PC when you outgrow it. The used business mini PC (ThinkCentre Tiny, OptiPlex Micro, EliteDesk Mini, HP ProDesk) is the homelab community's default recommendation for a reason — cheap, quiet, low-power, and strong enough to run a hypervisor with several virtual machines.

Proxmox, Docker, or a Simple Server OS? Pick Your Software Layer

Hardware is the easy half. The real decision is the software layer you run on it — and it mostly comes down to how you like to learn:

Proxmox VE is the homelab world's default hypervisor. It is free and open source (AGPLv3), installs from a downloadable ISO, and the current release is Proxmox VE 9.2 (released May 2026, built on Debian 13). It runs virtual machines and containers side by side from one web interface, with built-in snapshots — which means you can experiment, roll back, and experiment again. If virtualization is the skill you are after, this is the tool.

Docker is the fastest route to running real services. You define a service and its settings in a small Compose YAML file, and Docker runs it isolated from everything else. If you are new to containers, our Docker beginner guide walks the first stack start to finish.

Cosmos Cloud and CasaOS are the friendly on-ramps: a server dashboard with an app store, reverse proxy with automatic HTTPS, and (in Cosmos's case) SSO and a VPN built in. Cosmos installs as a single Docker container and offers a free tier; CasaOS is fully open source and installs with a one-liner. If the idea of a hypervisor feels heavy, start here — our Cosmos beginner guide covers the first install.

The approaches are not mutually exclusive. A common mature setup is Proxmox on the hardware, with a Linux VM running Docker inside it for services — the best of both worlds.

Your First Five Projects (In This Order)

Beginners fail by installing twenty services on day one and debugging them all at once. The community's hard-won lesson is: one project at a time, each one teaching the next. Treat this section as your homelab starter guide — the ladder is ordered so every step builds a skill the next step needs, and these are the first homelab projects most people wish they had run in order:

1. A media server (Jellyfin). Turn your movies and music into your own private streaming service. Jellyfin is free and open source — "no fees, no tracking, no hidden agenda" — and teaches you storage, shares, and basic service setup. Our Jellyfin beginner guide covers the first library.
2. Network-wide ad blocking (Pi-hole or AdGuard Home). Point your router's DNS at a Pi-hole and ads vanish on every device on your network — phones, TVs, tablets — with no app installed anywhere. This project teaches DNS, the single most important networking skill, and both options are free and open source.
3. Real backups (Borg or restic — or Proxmox Backup Server). Before your lab holds anything precious, back it up. Borg and restic are free, open-source tools that make encrypted, deduplicated backups; if you run Proxmox, its official Backup Server dedupes everything server-side. Rule of the lab: a service without a backup is a toy.
4. Uptime monitoring (Uptime Kuma). A free, self-hosted monitor that watches your services and alerts you when one dies — with a public status page if you want one. This teaches you HTTP checks, notifications, and the habit of knowing your lab's state at a glance.
5. A reverse proxy with HTTPS (Nginx Proxy Manager). One entry point that gives every service a proper name and a free Let's Encrypt certificate instead of raw IP-and-port addresses. This is the project that makes your lab feel professional — and it is the gateway to the security rules below.

After these five, the natural extensions are a photo backup (Immich is the free, open-source Google Photos alternative, now past its v3 release), a password manager (Vaultwarden), and document sync (Nextcloud).

Homelab vs VPS: When Should You Rent Instead?

A homelab and a VPS (virtual private server) solve different halves of the same itch. A homelab is hardware you own, behind your own router, on your own power bill — it is private, it is yours, and it keeps running when your ISP hiccups. A VPS is a slice of someone else's datacenter: reachable from anywhere, backed by enterprise power and networking, costing a few dollars a month.

The honest split: learn and experiment in the homelab; serve the public from the VPS. A homelab is a sandbox, not a production environment — your home uplink, dynamic IP, and a power outage during a storm are not how you want to host a public site. Conversely, renting a VPS to learn Linux basics is paying monthly for homework you could do free on an old laptop.

Many people run both: the homelab for media, backups, and learning; a cheap VPS as the always-on public face. If you are weighing the rented side, our what is VPS hosting guide explains the model, the costs, and what to check before buying.

The Security Rules: Read This Before You Expose Anything

Every homelab reaches the same dangerous moment: you want to reach your services from outside your home. Do it wrong and automated scanners will find your open port within hours. Do it right and your lab is safer than most corporate networks. The community's rules, verified against current homelab security guides:

• VPN first, always. Reach your lab over a mesh VPN like Tailscale (WireGuard-based; its free Personal plan covers up to 6 users with unlimited devices) instead of forwarding ports on your router. No open inbound ports, no scanners, no problem.
• Close router inbound ports and disable UPnP. If you must expose something publicly, do it through a reverse proxy with authentication — never a raw service port.
• SSH keys, never passwords. Disable password login on every machine, and put the lab behind a default-deny host firewall.
• Never open DNS (port 53) to the internet. Your Pi-hole is for your network only.
• Isolate IoT devices on a guest network or VLAN — cheap cameras and plugs are the weakest machines in most homes.

One sharp trap to know: in Tailscale, serve keeps a service private to your tailnet while funnel publishes it to the public internet — one word apart, opposite meanings. Always double-check which one you clicked.

What Will You Actually Learn?

A homelab is a curriculum disguised as a hobby. The skills people consistently report picking up, in roughly the order the five projects teach them:

• Linux — the operating system of the server world, learned by living in it.
• Networking — DNS, DHCP, VLANs, subnets, and how packets actually move, learned by debugging them.
• Virtualization — VMs, containers, snapshots, and resource allocation.
• Containers — Docker Compose files that deploy entire stacks in one command.
• Backups and recovery — the unglamorous skill that separates professionals from hobbyists.

The resume angle is real but keep it honest: a homelab complements production experience, it never replaces it. Nobody will hire you as a senior SRE because you run Jellyfin — but "I run a 4-service homelab with automated backups and WireGuard remote access, documented on GitHub" is a genuine signal of curiosity and follow-through, and for junior roles it stands out.

How to Plan Your Homelab Without Wasting Money

The most common beginner mistake is buying before planning: a server too weak for the plan, or a rack of gear with no idea what runs on it. Every good homelab for beginners starts the same way — spend the planning hour first. Decide your first three projects, list what each needs (CPU, RAM, storage), then buy — or don't, if the old laptop already covers it.

For a concrete planning pass, our free Self-Host Planner lets you pick apps, check server fit, and follow a setup checklist. And the community is enormous when you get stuck: r/homelab alone has around a million members posting daily, alongside siblings like r/selfhosted for software questions and r/HomeServer for absolute beginners.

Sources

Hardware price bands: Hacker Public Radio (hpr4148, Oct 2026); systemliquidation.com; pricehistory.app (OptiPlex 7050 Micro); paulsprogrammingnotes.com (Oct 2026); computingforgeeks.com (Oct 2026); howtogeek.com; epicdetect.io. Raspberry Pi 5 pricing: pbxscience.com. Idle-power figures: dev.to (jvancedev idle-watts roundup); xpbargain.com. Proxmox VE 9.2: pve.proxmox.com (Roadmap, FAQ). Docker Engine 29: smenode-labs.com. Jellyfin: official jellyfin.org listing. Pi-hole: pi-hole.net; Wikipedia (v6.4). AdGuard Home: hub.docker.com; privacygear.nl. Uptime Kuma: railway.com. Nginx Proxy Manager: dev.to/deploylark. Tailscale: ssdnodes.com; theproofdesk.com. Immich: contabo.com; coolcuration.com. Cosmos Cloud: cosmos-cloud.io; xda-developers.com. CasaOS: hysenlabs.com. Proxmox Backup Server: proxmox.com; pbs.proxmox.com. Borg: borgbackup.org. restic: restic.net. Security guidance: readthemanual.co.uk; freedzhost.cloud. Community: leadsrover.io (r/homelab). Intent research: howtogeek.com; wiobyrne.com; petri.com; homelabaddiction.com.

Frequently Asked Questions

What is a homelab server?

A homelab server is simply the machine (or virtual machine) inside your homelab that hosts your services, containers, or VMs. In a one-machine lab, the machine itself is the homelab server; in bigger setups, one box might run Proxmox while others provide storage.

How much does a homelab cost to start?

Anywhere from $0 to about $300. An old laptop you already own costs nothing. A used 6th–7th gen business mini PC — the community's default starter — runs roughly $80–$210; 8th–10th gen machines land around $100–$300. Expect a few dollars a month in electricity: a mini PC idles at about 11–15 watts.

Can I run a homelab on an old laptop?

Yes — and it is the recommended way to start. Install Linux or Proxmox, run a couple of containers, and learn the ropes. The built-in battery doubles as a free UPS during power blips. Upgrade to a used mini PC only when you actually outgrow the laptop's RAM or CPU.

Homelab vs VPS — which should a beginner start with?

Start with the homelab for learning: it is free (or nearly), private, and breaking things costs nothing. Rent a VPS later for anything the public internet must reach reliably, like a personal website. Many enthusiasts eventually run both.

Is a homelab worth it for an IT career?

As a complement to real experience, yes. It gives you hands-on reps with Linux, networking, virtualization, and backups — and a documented lab is a genuine signal of curiosity to employers. It does not replace production experience, so frame it honestly on your resume.