A home server is just a computer in your house that stays on and does one job around the clock instead of being used directly like a laptop or desktop. Instead of you sitting in front of it, other devices on your network — your phone, your TV, your laptop — connect to it over Wi-Fi to get something from it: a movie, a photo library, a blocked ad, a synced file. That's it. There's no special hardware requirement to call something a "home server" — people run them on everything from a repurposed 10-year-old laptop to a $2,000 rack-mounted machine.
This guide is the starting point for the whole site. If you've heard terms like "self-hosting," "homelab," or "NAS" thrown around and want to understand what they actually mean before spending any money, start here — or jump straight to our full home server glossary if you just need a quick definition.
Self-hosting, in one sentence
Self-hosting means running software on hardware you own and control, instead of paying a company to run it for you in the cloud. When you upload photos to Google Photos, Google's servers store and serve them. When you self-host with a tool like Immich, your own home server does that job instead — same basic experience, but the data lives on a drive in your house, and there's no monthly bill.
What people actually use a home server for
Nobody buys a home server just to "have a server." It's almost always to replace a specific paid subscription or to get a capability the cloud doesn't offer. The most common starting points are:
- Media streaming — running Jellyfin or Plex so you can stream your own movie and TV collection to any device, the way you'd use Netflix, but with content you own.
- Photo backup — running Immich or Nextcloud so your phone automatically backs up photos to a drive in your house instead of Google Photos or iCloud.
- File sync and storage — a personal Dropbox replacement that syncs documents between your devices without a per-gigabyte subscription.
- Network-wide ad blocking — running Pi-hole so every device on your Wi-Fi, not just one browser, has ads and trackers blocked at the network level.
- Smart home control — running Home Assistant so your smart bulbs, plugs, and sensors work through automations you control, instead of depending on a manufacturer's cloud app.
- Personal projects — a private game server, a password manager, a document scanner, a bookmark manager — thousands of free, open-source apps are built to run on a home server.
Most people start with exactly one of these — usually photos or media — get comfortable, and add more services over the following months. That's the normal path, and it's the one this site is built around.
Do you need special hardware?
No. Three types of hardware work as a first home server, in order of how common they are for beginners:
| Hardware | Good for | Rough cost |
|---|---|---|
| A used mini PC (e.g. Dell OptiPlex Micro, Lenovo ThinkCentre Tiny) | Most beginners — quiet, low power, plenty of CPU for several apps at once | $60–$180 used |
| An old laptop or desktop you already own | Testing the waters at $0 before buying anything | $0 |
| A dedicated NAS (Synology, QNAP, or a self-built one) | People whose main goal is large-scale file storage or a media library from day one | $200–$600+ |
For most beginners, we recommend starting with either a machine you already own or a cheap used mini PC — see our full mini PC buying guide for specific picks and what specs actually matter.
What software runs on it?
A bare computer doesn't do anything useful on its own — you need to install an operating system built for running server software, and then install the actual apps on top of it. There are two layers to understand:
1. The server operating system
Instead of Windows or standard desktop Linux, most home servers run a purpose-built OS such as:
- Proxmox VE — turns your machine into a mini data center where each app runs in its own isolated virtual machine or container.
- TrueNAS — built primarily around storing and protecting files, with apps layered on top.
- Unraid — a paid, beginner-friendly OS that blends flexible storage with an easy app store.
- Plain Ubuntu Server + Docker — a lighter-weight, more manual option many experienced self-hosters prefer.
We compare these directly in Proxmox vs TrueNAS vs Unraid — that's the natural next read after this one.
2. The apps themselves
On top of that OS, you install the actual applications — Jellyfin for media, Immich for photos, Pi-hole for ad blocking, Home Assistant for smart home. Almost all modern self-hosted apps are distributed as Docker containers, a packaging format that bundles an app with everything it needs to run, so installation is usually a matter of pasting a short configuration file rather than manually installing dependencies. See our full Docker for Beginners guide for exactly how that works.
What does it cost to run?
Three cost categories to plan for:
- Hardware, one-time — $0 if you reuse an old machine, $60–$180 for a good used mini PC, more if you add storage drives.
- Electricity, ongoing — a typical small mini PC draws 10–25 watts at idle, which works out to roughly $1–$4 a month depending on your local electricity rate. This is the detail that surprises people most: a home server is far cheaper to run than most expect.
- Storage drives, as needed — only relevant once you're storing a large media or photo library; a single machine's built-in drive is enough to start.
Compare that to $10–$20/month for a Google One or Dropbox plan, or $15–$25/month for a streaming bundle, and a basic home server often pays for its own hardware within the first year. For the full electricity math and a wider look at whether the trade-off is worth it for you, see our detailed cost breakdown and Is Self-Hosting Worth It?
Is it hard to maintain?
It requires more ongoing attention than a phone app that updates itself silently — you'll occasionally update software, and you are responsible for backing up your own data (nobody else will). But it does not require constant babysitting. Once a service like Jellyfin or Pi-hole is set up, it typically runs unattended for months. The honest tradeoff is: you get control and no subscription fee, in exchange for being the one responsible when something breaks.
A realistic first project
If you're not sure where to start, here's the path most beginners take, roughly in order:
- Install a server OS (Proxmox, TrueNAS, or plain Ubuntu + Docker) on whatever machine you're starting with.
- Get one simple, useful service running — Pi-hole is a popular first project because it's low-risk and the payoff (network-wide ad blocking) is immediate.
- Add a media server (Jellyfin) or photo backup (Immich) once you're comfortable.
- Set up an actual backup routine for anything you'd be upset to lose — self-hosting does not automatically mean your data is safe.
- Keep going one service at a time. Most homelabs grow slowly over months, not all at once.