How to start a homelab: a beginner's roadmap

A homelab is just your own small, always-on computer running the kinds of services you’d otherwise rent from someone else — a media server, a website, a backup target, a private AI model, a dashboard that tells you your house is fine. That’s the whole idea. It isn’t a rack of screaming servers in a closet, it doesn’t require a networking certification, and it doesn’t have to cost more than a decent pair of headphones to begin.

The thing that stops most people isn’t the technology — it’s not knowing the order. There’s a hundred guides for individual pieces and almost none that say “do this, then this, then this.” So this is the map: what a homelab is, the one machine to start on, and the exact sequence to build one up without getting overwhelmed or overspending. Every step links to a full walkthrough, so treat this page as the hub you come back to.

The short version: buy one small, quiet mini-PC (a fanless N100 box is the sweet spot). Install Proxmox on it — that turns the one machine into a place to run many things. Run one useful service so you get a win. Then add more, roughly in this order: make it reliable → put it behind a proper login → self-host real apps → play with local AI. You can be at your first working service by Sunday afternoon, for well under $150 of hardware.

What you’ll read here

• What a homelab actually is (and isn’t)
• Why bother — the honest reasons
• The one machine to start on
• The roadmap: what to add, in the right order
• How to actually start this weekend
• The mistakes that stall beginners
• FAQ
• Where to go next

What a homelab actually is (and isn’t)

A homelab is a computer you own and control that runs services for you — usually more than one at a time, usually left on. “Lab” is the honest word for it: it’s a place to run useful things and a place to learn by breaking things safely. The two goals live together, and that’s the point.

I’ll be straight about my own setup, because a homelab is rarely a tidy monoculture and I don’t want to sell you a fantasy of one. Most of my machines run Proxmox — the free platform that lets one box run a dozen separate services in their own tidy compartments. Alongside it I keep one machine on Unraid for bulk storage and a couple of Raspberry Pis for small always-on odd jobs. It grew a piece at a time; none of it arrived as a plan. Yours will be a mix too, and that’s completely normal.

Here’s what a homelab is not, because the myths do more to scare people off than the reality ever would:

• Not a rack in a closet. Mine started as a single mini-PC on a shelf. Most stay that way happily.
• Not expensive. The entry ticket is one small computer. You can start with a machine you already own.
• Not a job requirement. It’s a hobby that happens to teach you genuinely useful skills as a side effect.
• Not fragile. Rebuilding is a feature — when it’s your lab, wiping it and starting over is a ten-minute learning exercise, not a disaster.

Why bother — the honest reasons

Four reasons hold up, and I’ll skip the ones that don’t:

• You stop renting things you could own. Photo storage, a notes app, a password manager, a website — each is a small monthly fee that never ends. A homelab lets you run your own copies, on hardware you paid for once.
• Your data stays yours. What you self-host doesn’t get mined, sold, or discontinued when a startup folds. For some things — family photos, documents — that peace of mind is the whole reward.
• You learn by doing, on stakes that are real but forgiving. Nothing teaches you how computers, networks, and services actually fit together like running a few of your own. It’s the best sandbox there is.
• It’s fun. That’s allowed to be the reason. Watching your first service boot and realizing you run it now is a small, genuine thrill.

No moral crusade here — you don’t have to “de-Google your life” or host everything yourself to count. Run one thing you find useful, keep the rest in the cloud, and you’re already doing it right.

The one machine to start on

You need one computer to dedicate to this. The sensible, boring, correct answer for a first homelab is a fanless N100 mini-PC — a palm-sized box that sips power, makes no noise, costs less than a nice dinner out, and will run a first lab’s worth of services without breaking a sweat. It’s the class of hardware nearly every guide on this site assumes, precisely because it’s the right place to begin.

You don’t have to buy anything at all to start, though. An old laptop or a spare desktop works fine for learning — any 64-bit machine with a bit of RAM will do. Start with what you have, and buy deliberately once you know what you actually want to run. (A dedicated “your first home server: what to buy” guide is coming next, with real numbers from the boxes I actually run — I’d rather measure my own hardware than recite a spec sheet.)

What you should not do is buy a rack, a used enterprise server, or anything with the word “Xeon” in it for your first build. They’re loud, power-hungry, and they’ll teach you to hate the hobby before you’ve run a single service. Small and quiet first. You can always grow.

The roadmap: what to add, in the right order

This is the part nobody lays out plainly. A homelab grows in four natural stages. Do them in order — each one rests on the one before it — and don’t rush ahead. There is no prize for tier four; there’s a working, reliable, useful lab, which is better.

Tier 1 — Get it running (your first weekend)

The goal here is simply to have a platform and one thing running on it.

1. Pick your machine (a mini-PC, or that spare PC).
2. Install Proxmox — this is the twenty-minute job that turns one computer into a place to run many services, each in its own box. This is the first guide to read.
3. Create your first container and start it. That’s your first win.

Once you’re comfortable clicking through installs, you can automate the whole thing into a flash-and-walk-away setup so rebuilding is painless. And if your shiny new mini-PC ever freezes at random for no obvious reason, that’s a known N100/N5105 quirk with a one-line fix — don’t panic, and don’t return the hardware.

Tier 2 — Make it useful and reliable

Now you make the lab pleasant to live with: you want to know when something’s down, and you want to fix the ordinary breakages without a three-hour rabbit hole.

• A self-hosted status page with Uptime Kuma — a friendly first “real” service that watches everything else and tells you at a glance what’s up.
• Linked but no IP: a network detective story — the single most useful troubleshooting mindset in the hobby, for the day a device is connected but stubbornly won’t talk.
• When your iPhone won’t AirPrint — a small, satisfying win that turns a cheap printer into one your whole household can print to.

Two more Tier-2 pieces — a proper 3-2-1 backup routine and a plain-English home-networking primer — are on the way. Backups especially: start thinking about them now, before you’re hosting anything you’d be sad to lose.

Tier 3 — Run real services safely (my actual stack)

This is where a homelab stops being a toy and starts being infrastructure. The theme is doing it properly: a real login in front of your apps, protection from the noise of the internet, and visibility into what’s going wrong.

• SSO for any app with Authentik + Traefik — put one proper login screen in front of everything, instead of a dozen weak passwords.
• CrowdSec IPS in front of Traefik — automatically block the bots and bad actors that knock on every internet-facing door.
• Self-hosted error tracking with GlitchTip — see your apps’ errors before your users do.
• Self-hosting Supabase in a Proxmox LXC — run a real application backend (database, auth, storage) entirely on your own hardware.

Coming in this tier: getting your email deliverability right (SPF/DKIM/DMARC), hardening a small-office stack, and deploying a static or Node site to cPanel. These are the boundary skills where a homelab hobby quietly becomes professional competence.

Tier 4 — The fun frontier: local AI

Once the fundamentals are solid, the most fun you can have in a homelab right now is running AI models on your own hardware — no subscription, no data leaving the house.

• Running 30B-parameter LLMs on a Ryzen iGPU — proof that you don’t need a $2,000 graphics card to run a genuinely capable model locally.

A gentler “run your first local LLM” entry point and a look at the AI-specific hardware worth buying are both on the roadmap. But you’ll get more out of them once tiers one to three are second nature.

How to actually start this weekend

Enough map — here’s the concrete first move:

1. Saturday morning: find a machine (mini-PC, old laptop, spare desktop) and a spare USB stick.
2. Saturday afternoon: follow the install-Proxmox guide start to finish. Budget an hour; most of it is waiting for downloads.
3. Saturday evening: create your first Linux container and start it. Stop there and enjoy it.
4. Sunday: stand up a status page so you can watch your new lab watching itself.

That’s a complete, real homelab in a weekend. Everything after that is just adding pieces at whatever pace you enjoy.

The mistakes that stall beginners

The people who bounce off this hobby almost always hit one of these. None of them are about intelligence — they’re about order and expectations.

• Buying too much hardware first. A rack and a Xeon will teach you to resent the noise and the power bill. Start with one small quiet box.
• Skipping the static IP. A lab host that changes its own address every few days is one you can never find again. Set a fixed IP on day one (the install guide walks you through it).
• Exposing things to the internet too early. Get it working on your own network first. Opening ports to the world is a Tier-3 skill, done deliberately and behind a proper login — not a Tier-1 shortcut.
• No backups. The saddest homelab story is “I lost the config I spent a month on.” Decide on a backup routine before you host anything you’d miss.
• Chasing perfection. Your first setup will be a bit messy. That’s fine — rebuilding is a feature. A running-but-imperfect lab beats a perfect one that only exists in your browser tabs.

FAQ

How much does it cost to start? As little as $0 if you use a machine you already own, or roughly $120–$150 for a new fanless N100 mini-PC — a one-time cost, not a subscription. Everything I write about runs on free, open-source software.

Do I need to be a Linux expert? No. Proxmox gives you a clean web interface, so most of what you do is clicking, not typing. You’ll pick up the command line naturally as you go — you don’t need it to start.

Is it safe? Will I get hacked? On your own home network, running services just for yourself, it’s very safe. Risk only enters when you deliberately expose something to the internet — and that’s a later, deliberate step done properly (a real login and an IPS in front), never an accident.

Will it wreck my power bill? A mini-PC draws roughly what a couple of LED bulbs do — a few dollars a year. This is exactly why we start small and fanless rather than with old server hardware, which really can cost you.

Is a Raspberry Pi enough? For a first always-on service or two, yes, and it’s a lovely low-power option. But a Pi can’t comfortably run the many-services-at-once, Proxmox-style lab this roadmap builds toward — so I’d point a beginner at a small x86 mini-PC as the main machine and keep a Pi for side jobs.

Homelab or just use the cloud? Both, honestly. Use the cloud for things that must never go down; use your homelab for everything you’d like to own, learn from, or stop paying monthly for. It’s not a competition — most of us run a bit of each.

Where to go next

You now have the map. The single next step is the same for everyone: install Proxmox on your first machine — it’s a twenty-minute job and the foundation everything else rests on. From there, follow the tiers at your own pace: make it reliable, put it behind a proper login, and eventually run AI on your own hardware.

Bookmark this page and come back to it whenever you’re not sure what to build next. Take it slowly, break things freely, and remember the whole thing is meant to be fun — it’s your lab.