How to get started building a Homelab server in 2026

Look, if you’ve been lurking on r/homelab or watching YouTube videos of people with full server racks in their basements, I get it. It looks intimidating. Expensive. Like you need an IT degree and a dedicated room in your house just to get started.

You don’t. I built my first homelab server for under $200 with a used PC from Facebook Marketplace, and it ran everything I threw at it. This post is the guide I wish I had when I started - no $2,000 server rack required, no enterprise networking degree, just a cheap used PC and some curiosity.

Why did I start building a Homelab?

It started with my Synology NAS choking. I kept adding Docker containers to it - a media server here, a download manager there - and eventually the little NAS was gasping for air. The CPU was pegged at 100% and the 2GB of RAM was a joke. Every time I wanted to try a new service, something else would crash.

I realized I had two options: buy an expensive new NAS with better specs, or get a proper server and let the NAS do what it’s good at - storing files. The server won.

What I actually wanted out of this thing

Before I started browsing hardware, I wrote down what mattered to me:

• Cheap. Under $200. I didn’t know if I’d stick with this hobby, so I wasn’t about to drop serious money on it.
• Run all my containers. I had about 15 services I wanted to run, and the server needed to handle them without breaking a sweat.
• Upgradeable. I wanted to be able to add RAM or swap drives later without buying a whole new machine.
• Docker and container friendly. This was non-negotiable.
• Low power draw. I didn’t want my electricity bill to double.
• RAID support. Some level of redundancy for my data.

Start small. Seriously.

Here’s the best advice I can give you: don’t overthink your first homelab. You don’t need a rack-mounted Dell R730 (I eventually got two of those, but that came later). You don’t need 10G networking. You don’t need ECC RAM.

You need a used PC with a decent CPU and enough RAM to run some containers. That’s it.

Picking hardware for a homelab on a budget

Not everyone needs the same thing, and your living situation matters more than you’d think. A rack server in an apartment is going to make your partner hate you (ask me how I know). Here’s how I’d think about hardware tiers for beginners:

Tier 1: Just learn the basics ($0-75)

An old laptop or a Raspberry Pi. If you’ve got an old laptop collecting dust, install Ubuntu Server or Debian on it, throw Docker on top, and start playing. A Raspberry Pi 5 (about $60-80) works too. You won’t run 20 containers on these, but you can run Pi-hole, a small media server, and a few other things. The point is to learn Linux, Docker, and networking basics without spending real money.

Best for: People who aren’t sure they’ll stick with it, apartment dwellers with zero space, students.

Tier 2: Mini PCs ($100-250)

Beelink, Intel NUC, or Minisforum mini PCs. This is the quiet homelab sweet spot. These things idle at 10-25W (your electricity bill won’t even notice), they’re dead silent, and they fit on a bookshelf. A used Intel NUC or a Beelink Mini S with 16GB RAM and a small SSD will run 10-15 containers comfortably.

Best for: Apartments, shared living spaces, anyone who values quiet over raw power.

Tier 3: Used office PCs ($50-200)

Dell OptiPlex, HP EliteDesk, Lenovo ThinkCentre. This is what I’d recommend for most people starting out. Businesses cycle these out every 3-5 years by the thousands, and they end up on eBay and Facebook Marketplace for almost nothing. An OptiPlex 7040 or ThinkCentre M920 with an i5, 16-32GB RAM, and an SSD will handle pretty much anything a beginner throws at it.

Best for: The best balance of price, performance, and upgradeability. My recommendation for most beginners.

Tier 4: Used enterprise servers ($200-500+)

Dell PowerEdge, HP Proliant, Lenovo ThinkServer. This is what I started with, and it’s overkill for most beginners. These have Xeon CPUs, tons of RAM slots, and hardware RAID controllers. But they’re also loud (small high-RPM fans), power-hungry (100-200W idle for older models), and heavy. Don’t start here unless you have a basement, garage, or attic to put it in.

Best for: People with dedicated space who know they want to go deep into virtualization and containers.

A note about noise and power

This is the thing nobody tells you before your first server arrives. Rack servers sound like a jet engine when they boot up. Tower servers and mini PCs are fine, but anything designed for a data center rack is going to be loud.

Power is the other thing. Here’s what different setups actually cost to run 24/7 (at average US electricity rates of ~$0.12/kWh):

Hardware	Idle Wattage	Monthly Cost	Annual Cost
Raspberry Pi 5	3-5W	~$0.50	~$5
Mini PC (NUC/Beelink)	10-25W	$1-3	$10-25
Used office PC (OptiPlex/ThinkCentre)	40-80W	$4-8	$40-85
My ThinkServer (Xeon E3)	~80W	~$7	~$85
Enterprise rack server (R730, etc.)	100-200W	$10-20+	$100-200+
Two enterprise servers (my current setup)	250-400W	$22-35	$260-420

My ThinkServer idled at around 80W, which worked out to roughly $7-8/month. That’s not bad. But when I later upgraded to two Dell R730s, the power bill jumped to over $25/month. Rule of thumb: multiply your idle wattage by 0.73 to get your rough monthly cost at average US rates.

Where to buy used hardware

• Facebook Marketplace - Local businesses dump old office PCs here constantly. I’ve seen perfectly good machines for $50-150.
• eBay - Great for specific models. Search for “Dell OptiPlex” or “Lenovo ThinkCentre” and sort by price.
• Craigslist - Hit or miss, but you can find deals.
• r/homelabsales - The subreddit where homelab people sell their old gear when they upgrade.
• Local e-waste recyclers - Some will sell you old business PCs for next to nothing.

What to look for in any used hardware:

• CPU: Any Intel i5/i7 from the last 8-10 years, or a Xeon E3/E5. These are more than enough for a starter homelab.
• RAM: 16GB minimum, 32GB is the sweet spot. RAM is usually the first bottleneck.
• Storage: Doesn’t matter as much if you have a NAS. A single SSD for the OS works fine.

Buying my first server

I found a used Lenovo ThinkServer on Facebook Marketplace that some local business was getting rid of. $150.

The specs:

• CPU: Intel Xeon E3-1226 v3 @ 3.30GHz (4 cores)
• Storage: 2TB HDD
• RAM: 32GB

For $150, this was a steal. The Xeon CPU handles virtualization like a champ, 32GB of RAM is plenty for running 15-20 containers, and the 2TB drive gave me room for local storage while my NAS handled the bulk media files.

The thing about buying used enterprise hardware is that it was built to run 24/7 in a server closet. These machines are tanks. My ThinkServer had been running for years in some office before I got it, and it didn’t skip a beat.

Picking an operating system

I almost went with Ubuntu since it’s what I knew. Throw Docker on top, maybe Portainer for a web UI, and call it a day. But I kept reading about Proxmox and decided to give it a shot.

I’m glad I did. Here’s what sold me:

Proxmox is built for exactly this. It’s a free, open-source virtualization platform that supports both full VMs (via KVM) and lightweight containers (via LXC). Ubuntu can do containerization, sure, but Proxmox was designed for it.

The web UI is great. You get a full management interface out of the box. Create containers, manage storage, monitor resources, take snapshots - all from your browser. No SSHing into the machine for every little thing.

Snapshots and backups are built in. Before I make any changes to a container, I take a snapshot. If I break something (and I break things constantly), I roll back in 30 seconds. This alone makes Proxmox worth it for a homelab.

ZFS support. If you want RAID or data integrity checking, Proxmox has tight ZFS integration. I ended up not using ZFS on my first build (it needs extra RAM to manage), but it’s there when you need it.

It grows with you. When I eventually added a second server, Proxmox clustering made it easy to manage both from one interface. Try doing that with bare Ubuntu and Docker.

Other OS options worth knowing about

Proxmox is my pick, but it’s not the only option:

• Unraid - Paid ($59+), but has a really polished UI and a built-in app store. Great if you want something that “just works” and don’t mind paying for it. Particularly good for NAS + containers on the same box.
• TrueNAS Scale - Free, Linux-based, strong on storage and ZFS. Better if your primary use case is NAS with some containers on the side.
• CasaOS - Free, runs on top of any Debian/Ubuntu install. The simplest option - basically an app store for self-hosted services. No virtualization support, but for pure Docker containers it’s hard to beat for ease of use.
• Ubuntu/Debian + Docker - The DIY option. No web UI out of the box (add Portainer for that), but maximum flexibility and the most online tutorials.

If you’re brand new and just want to run Docker containers, CasaOS or Unraid are the lowest friction options. If you want to learn virtualization and have more control, Proxmox is the way to go.

The Proxmox forum has a good beginner tutorial for getting your first VM set up.

What to run first on your homelab

When you’ve got your server running, it’s tempting to install everything. Resist the urge. Start with services that give you immediate, tangible value so you actually use the thing instead of just admiring your container list.

My recommended day-one stack:

1. Pi-hole - Network-wide ad blocking. Set this as your DNS server and every device on your network stops seeing ads. Your family will notice this one immediately.
2. Jellyfin or Plex - A media server. Throw your movies and music on it and you’ve got your own private streaming service.
3. Homepage or Homarr - A dashboard that shows all your services in one place. Makes your homelab feel real.
4. Uptime Kuma - Monitors whether your services are up. You’ll be surprised how addictive this dashboard becomes.

That’s a solid afternoon project. Once those are running and you’re comfortable, branch out to the full list below.

The containers I run

The Community Scripts project (formerly the tteck Proxmox Helper Scripts) has one-liner install scripts for most popular homelab services. It makes setup almost embarrassingly easy.

Media Management

I use the TRaSH Guides to configure all of my Arr apps and media downloaders. If you’re setting up a media stack, start there.

• Plex - My original media server. Still works, but I’ve lost some confidence in where the project is headed.
• Jellyfin - The open-source alternative I’ve been testing. Running both side by side in separate containers is one of the nice things about Proxmox. (If you’re into music specifically, I wrote about why self-hosted music still sucks - the video side is way more mature.)
• Tautulli - Monitors Plex usage. Tells me exactly who’s streaming what and when.
• Seerr - Request management and media discovery. Friends and family can request movies and shows through a nice web UI.
• Radarr / Sonarr - Automated movie and TV show management, integrated with Usenet and BitTorrent.
• Prowlarr - Indexer manager for all the Arr apps.
• Readarr - Manages ebooks and audiobooks.
• Audiobookshelf - A dedicated server for audiobooks and podcasts.
• Bazarr - Automated subtitle downloads.
• Tdarr - Transcoding and health checking for media files.
• qBittorrent - Torrenting (legal content, obviously).
• SABnzbd - Usenet downloads.

Everything Else

• Pi-Hole - Network-wide ad blocking. I moved this off a Raspberry Pi and onto Proxmox. Way more reliable.
• Octoprint - Remote control for my 3D printer.
• MagicMirror - Moved my smart mirror project to Proxmox for centralized management.
• Grocy - Grocery and household management. My partner actually uses this one, which is the ultimate test of any self-hosted app.
• Minecraft server - Because of course I run a Minecraft server.

For a much bigger list of self-hosted apps, check out Awesome Self-Hosted on GitHub. It’s the definitive catalog.

How I architect containers

My approach is simple: one service per container. Every app gets its own isolated LXC container in Proxmox. This sounds like overkill until the first time you update one service and it breaks another one’s dependencies. With isolated containers, that never happens.

The benefits are practical:

You can update Sonarr without worrying about breaking Radarr. You can snapshot a container before making changes and roll back if something goes wrong. If one service goes haywire and eats all its allocated RAM, everything else keeps running. And when you want to try a new service, you spin up a fresh container in about 30 seconds.

I use lightweight Debian images for all my containers. I was already comfortable with Ubuntu, and Debian is Ubuntu’s parent distro, so the learning curve was minimal.

Using the NAS as shared storage

The Synology NAS is the backbone of my media setup. Instead of storing media files on the Proxmox server itself, I mount the NAS as a network drive inside each container that needs access to media. This means Plex, Sonarr, Radarr, and qBittorrent all read and write to the same NAS storage. No data duplication, no wasted local disk space.

                    +-----------+
                    |  Clients  |
                    | (Desktop, |
                    |  Mobile)  |
                    +-----+-----+
                          |
                    +-----+-----+
                    |   Nginx   |
                    |  Reverse  |
                    |   Proxy   |
                    +-----+-----+
                          |
         +----------------+----------------+
         |                                 |
+--------+--------+             +---------+---------+
|  Proxmox Server  |             |   Synology NAS    |
|                  |    NFS     |                   |
|  +------------+  |<---------->|  /volume1/data    |
|  |    Plex    |  |   mount    |  (Movies, TV,     |
|  +------------+  |            |   Music, Books)   |
|  |  Jellyfin  |  |            +-------------------+
|  +------------+  |
|  |   Sonarr   |  |
|  +------------+  |
|  |   Radarr   |  |
|  +------------+  |
|  |   Seerr    |  |
|  +------------+  |
|  | qBittorrent|  |
|  +------------+  |
|  |  Pi-hole   |  |
|  +------------+  |
|  | Minecraft  |  |
|  +------------+  |
|  |   + more   |  |
|  +------------+  |
+------------------+

How to mount a NAS inside Proxmox containers

If you’re using a Synology NAS (or any NFS-capable NAS), mounting it in your Proxmox containers is straightforward. Here’s how:

First, update packages and install NFS support:

sudo apt update && sudo apt install nfs-common -y

Create a mount point:

mkdir /nas

Edit your filesystem table to add the NAS mount:

nano /etc/fstab

Add this line (replace with your NAS IP and share path):

192.168.0.100:/volume1/data /nas nfs defaults 0 0

Reload system daemons and mount:

systemctl daemon-reload
mount /nas

That’s it. Your NAS storage is now available at /nas inside the container, and it’ll automatically mount on reboot.

Mistakes I made so you don’t have to

After running this setup for a while (and eventually scaling to a full rack with two Dell R730s), here are the things I wish someone had told me:

Don’t overcommit RAM

It’s tempting to give every container 4GB of RAM “just in case.” Don’t. Most services need way less than you think. Start with 512MB or 1GB per container and bump it up only if you see actual memory pressure. Use htop inside your containers to monitor real usage.

Don’t install everything at once

I know the awesome-selfhosted list is exciting. But deploying 30 containers you’ll never actually use is a waste of resources and a maintenance headache. Install what you’ll actually use this week, not what sounds cool.

Set up static IPs early

I didn’t do this at first and it was a nightmare. Every time my router reassigned an IP, half my services would break because they referenced each other by IP address. Assign static IPs to your server and containers from day one, or use your router’s DHCP reservation feature.

Take snapshots before you change anything

Proxmox snapshots are free and fast. Before updating a container, changing a config, or trying something new - take a snapshot. I can’t count the number of times this has saved me from a full reinstall.

Use VLANs if you’re exposing anything to the internet

If you’re planning to make any services publicly accessible (and you probably will eventually), segment your network. Put your public-facing services on a separate VLAN from your home network. Proxmox’s built-in firewall makes this manageable.

Containers over VMs (usually)

LXC containers share the host kernel and use way fewer resources than full VMs. For most homelab services, containers are the right choice. I only use full VMs for things that need a separate kernel (like a Windows gaming VM or a firewall appliance).

Automate your backups

Set up automated backups to a separate disk or your NAS. Proxmox has built-in scheduled backup support. Don’t be the person who loses their entire setup because a drive died. The 3-2-1 backup rule is worth reading about: 3 copies of your data, on 2 different types of media, with 1 offsite.

Document what you do

Future you will not remember why you changed that config file at 11 PM on a Tuesday. Keep notes. A simple markdown file in a git repo works great. When something breaks six months later, you’ll thank yourself.

Where to go from here

The beauty of a homelab is that it grows with you. My setup started as a single $150 ThinkServer running 15 containers. Two years later, it’s two Dell R730s with dual NVIDIA GPUs, 10G networking, VLANs, 60+ containers, and a full Home Assistant smart home setup. You can read about that evolution in My Homelab Two Years Later: From Desktop Tower to Server Rack.

But none of that would have happened if I’d waited until I could afford the “right” hardware. I started with what I could get cheap, learned as I went, and upgraded when I hit actual limitations - not imagined ones.

Some natural next steps once you’re comfortable:

• Set up a reverse proxy (Nginx Proxy Manager or Caddy) to give your services clean URLs. I wrote about how to set up custom domain names on your internal network using Nginx Proxy Manager and Pi-Hole.
• Add a VPN (WireGuard or Tailscale) for secure remote access to your homelab.
• Try Home Assistant if you have any smart home devices. I initially kept it off my server for security reasons, but it eventually became the most important thing in my entire setup. I wrote a getting started guide for Home Assistant and later documented replacing Alexa with a privacy-focused setup.
• Add GPU passthrough if you want hardware-accelerated transcoding in Plex/Jellyfin or want to run a gaming VM. I used GPU passthrough to build a subtitle generator with Whisper - that’s the kind of project a GPU-enabled homelab unlocks.

Resources for homelab beginners

When I was starting out, these communities and resources were invaluable:

• r/homelab - The main subreddit. Great for inspiration and troubleshooting. Read the wiki before posting.
• r/selfhosted - Focused specifically on self-hosted apps and services.
• Self-Hosted podcast - Chris and Alex cover new self-hosted apps, hardware, and homelab news every two weeks.
• Awesome Self-Hosted - A curated list of self-hosted software. This is where you go to discover what’s possible.
• ServeTheHome - Hardware reviews focused on servers and homelab gear. Their mini PC reviews are particularly useful.
• Proxmox community forums - For Proxmox-specific troubleshooting.
• TRaSH Guides - If you’re setting up a media stack, these guides are the gold standard.
• Community Scripts for Proxmox - One-liner install scripts that make Proxmox setup painless.

Frequently asked questions

How much does a homelab cost to run?

Hardware cost is a one-time thing ($50-500 depending on what you buy). Ongoing electricity is the real cost. A mini PC idles at 10-25W and costs about $1-3/month. A used office tower idles at 40-80W and costs about $4-8/month. A full rack server idles at 100-200W and costs $10-20+/month. My single ThinkServer added about $7/month to my electricity bill.

Can I run a homelab in an apartment?

Yes. A mini PC (Beelink, Intel NUC, Minisforum) is completely silent, smaller than a book, and uses less power than a light bulb. You can run Pi-hole, Jellyfin, Home Assistant, and a dozen other services on one. Just don’t buy a rack server for an apartment - your neighbors will hear it.

Is a homelab worth it in 2026?

If you want to learn Linux, Docker, and networking - yes. If you want to self-host your own services instead of paying for cloud subscriptions - yes. If you just want a Plex server and nothing else - maybe just use a Raspberry Pi. The real value of a homelab is that it teaches you things you can’t learn any other way, and it compounds over time.

What if I break something?

You will break something. That’s the whole point. Proxmox snapshots make it easy to roll back, and the worst case scenario is you reinstall a container (which takes about 2 minutes). Nothing you do on a homelab is going to damage your hardware or your home network permanently. Give yourself permission to experiment.

Do I need to know Linux?

Not to start. Proxmox and Unraid both have web UIs that handle most things. But you’ll naturally pick up Linux commands as you go, and that’s one of the most valuable skills a homelab gives you.

Wrap up

Don’t wait for the perfect hardware or the perfect time. Grab a used PC for $100-200, install Proxmox, and start spinning up containers. You’ll break things, you’ll learn a ton, and you’ll wonder why you didn’t start sooner. The homelab community is one of the most helpful communities in tech - hit up r/homelab, the Proxmox forums, or the Self-Hosted podcast when you get stuck.

Your first homelab doesn’t need to be impressive. It just needs to exist.