Dee's Builds
Live Testing Lab

Hands-on notes from the bench — Linux, gadgets, 3D printing, and self-hosting, tested and written up as I actually build them.

// add your photo here
Browse by topic
Linux Privacy Raspberry Pi Home Labs Home Assistant 3D Printing Retro Gaming AI Tools Gadgets

What actually is a "home lab"?

What actually is a "home lab"?

Strip away the intimidating name and a home lab is just this: a computer at your house running services that normally live on someone else's server. Instead of paying Google to store your photos, streaming music through Spotify, or trusting a random cloud app with your files, you run your own version of that thing on your own hardware, in your own home.

That's it. No server room, no rack of blinking lights required (though plenty of people go that far for fun). For most beginners it starts as a single small box quietly sitting on a shelf, doing jobs a subscription service used to do.

Okay, but what does it actually do?

Depends entirely on what you point it at. Some common starting projects people build in their first home lab:

  • A media server - stream your own movies, TV and music library to any device in the house, no subscription
  • A photo library - back up and browse your phone photos without handing them to a big tech company
  • Network-wide ad blocking - block ads and trackers for every device on your wifi at once, not just your browser
  • File storage - a private network drive for backups, documents, whatever you don't want living only on one device
  • A dashboard - one page that shows the status of everything else you're running
  • Home automation - control lights, sensors and smart home gear without routing it through someone else's cloud

Most people don't set out to build all of that on day one. You pick one annoyance - usually "I don't want to pay for this anymore" or "I don't want this company having my data" - and solve it. Then you catch the bug and keep adding more.

What hardware do you actually need?

Less than you'd think, and you very likely don't need to buy anything new to try it out:

  • An old laptop or desktop gathering dust - genuinely the easiest way to start, costs nothing
  • A Raspberry Pi - small, cheap, low power, sips electricity 24/7 without you noticing on the power bill
  • A mini PC - secondhand office machines (the tiny ones) are a favourite in the community, cheap and surprisingly capable
  • A proper NAS enclosure - a purpose-built box for hard drives, more of a "once you know you're keeping this up" purchase

For software, the usual pattern is a lightweight Linux operating system plus Docker, which lets you run each service in its own tidy little "container" - self-contained, easy to add, easy to remove, and they don't interfere with each other.

Do I need to know how to code?

No. Genuinely, no. I don't either - I'm a copy-paste tinkerer, not a developer, and that describes most of this hobby. The vast majority of self-hosted apps come as a ready-made Docker "recipe" (called a compose file) that you paste into a simple web dashboard and click a button. You're assembling, not programming.

You do need patience for the odd error message and a willingness to Google things - but that's true of literally any new hobby involving a computer.

A peek at my own setup

To make this less abstract - here's what's actually running in mine right now. It's a Raspberry Pi 5 with a couple of USB hard drives attached, running OpenMediaVault to manage the storage and Docker to run everything. On top of that sits:

  • Navidrome - my own music streaming server, pointed at a folder of my own music files
  • Jellyfin - same idea but for movies and shows
  • Immich - a self-hosted photo library, set to manual upload since I'm not a heavy photo-taker
  • Pi-hole - blocks ads and trackers for every device on the home network, and gives all the above friendly local names instead of remembering IP addresses

Nothing exotic, nothing expensive, and importantly - none of it is exposed to the wider internet. It's all local-network-only for now, which is exactly where I'd recommend any beginner starts. Get comfortable running things at home first before you even think about opening anything up to the outside world.

Where to go next

Once the bug bites, these are the places worth bookmarking:

  • r/homelab and r/selfhosted on Reddit - active communities, endless setup inspiration
  • Awesome-Selfhosted - a huge curated list of self-hostable apps for basically anything you can think of
  • The Self-Hosted podcast - good background listening while you tinker

The takeaway

A home lab isn't a destination, it's a habit that grows one small project at a time. Grab whatever spare hardware you've got lying around, pick one annoyance to solve - a subscription you're sick of paying, a company you're sick of trusting with your data - and go build that one thing. Everything else comes later.

What's the first thing you'd self-host if you started tonight? Let me know in the comments.