Why I built a home server

Somewhere around the third streaming subscription, it stops being fine. Not dramatically. Just a steady drip — a bit more here, a bit more there, every month, forever. For content that gets pulled without warning. For libraries that shrink whenever two corporations fall out. For photo storage where the price goes up and the terms of service get longer and somehow vaguer every year.

That was the beginning of this.

It wasn’t some grand ideological stance. It was simpler and more embarrassing than that. I just got tired of paying for things I didn’t really own.

The idea

I’d been aware of home servers as a concept for a while — something people with server rooms and too much time on their hands did. A loud tower PC in a spare bedroom, cables everywhere, a project that would consume your weekends and never quite work properly.

That’s not what this is.

What actually changed my mind was learning about mini PCs. Small-form-factor machines, roughly the size of a thick paperback novel, that draw 10–15 W of power at idle and run completely silently. You stick one on a shelf and forget it’s there. It’s on 24/7 but your electricity bill barely notices.

You probably already have something that qualifies. A Raspberry Pi works. An old laptop works. The kind of surplus corporate hardware that IT departments dump on eBay for next to nothing — a ten-year-old business laptop or a compact desktop from some office refresh cycle — works fine for most home server tasks. If you end up using an old laptop, pull the battery out: it reduces heat and removes a minor long-term safety risk for something that runs permanently. The hardware I actually care about is the network connection; gigabit ethernet beats WiFi here every time.

What I personally went with is an Intel NUC — a compact thing with an Intel Celeron processor, 16 GB of RAM, and a 1 TB NVMe SSD. I spent a mildly embarrassing number of evenings reading comparison tables before landing on this. At the scale of a home file server, that level of research was almost certainly unnecessary. I know that now. The broader point is that you’re looking for something low-power, reasonably quiet, and with enough storage for what you’re planning. You don’t need a server rack. You need a shoebox — and you might already have something in a drawer that qualifies.

Debian Linux, headless

The operating system is Debian 12 — one of the most stable Linux distributions available, and genuinely boring in the best possible way. Boring means it doesn’t surprise you. Boring means it just works.

“Headless” means there’s no monitor, no keyboard, no mouse attached to the machine. It sits on a shelf. You manage it over SSH from your laptop, which sounds intimidating the first time and completely normal the tenth.

I’ll be honest: I’m not a sysadmin. I’m a guy who tinkers. I learned what I needed from guides and documentation and occasionally from making a mess of something and having to fix it. The Debian installation itself is guided and fairly straightforward. The headless part — configuring it so you can just SSH in and do everything remotely — takes an extra step or two but nothing catastrophic.

One thing I made sure to do during setup: full disk encryption using LUKS. The whole drive is encrypted at rest. If the machine ever walks out of my house — unlikely, but the world is what it is — whoever takes it gets a brick. Not my files, not my family’s photos, not anything useful. My threat model is probably not that sophisticated. But I sleep better.

Security basics that aren’t scary

A machine that’s always on and reachable on your local network deserves some basic hardening. Not paranoid-level hardening. Just sensible hygiene.

Three things make a significant difference without requiring expertise:

SSH key authentication instead of passwords. You generate a key pair, put the public key on the server, and from that point on logging in requires the key — not a password that someone could guess or brute-force.

A non-default SSH port. The default is 22, and automated scanners hammer it constantly. Move SSH to a different port and most of that noise disappears overnight.

UFW — the “uncomplicated firewall” — set up to allow traffic only on the ports your server actually uses. Everything else is blocked by default. It takes five minutes to configure and dramatically reduces your exposure.

That’s it. Three things, an evening’s work, and the server goes from naive to reasonably hardened. I’m not claiming it’s penetration-tested. I’m a dad with a Linux box, not a bank. But it’s not sitting there with the doors wide open, either. And if you route all remote access through Tailscale — which I’ll get to in the next post — you’re not forwarding any ports at all, which means the public attack surface becomes close to zero. The equation simplifies considerably.

The thing underneath all of this

I try not to be preachy about this, because it risks sounding like a manifesto and I don’t really have one.

But I’ve been noticing, for a while, how much of digital life is structured around access rather than ownership. Your photos are on someone else’s server. Your music disappears if you stop paying. Your film library depends on licensing agreements between companies that have no idea you exist.

I’m not saying this to alarm anyone. Most of it is fine and convenient and I still use plenty of cloud services. But there’s a version of this where you just quietly take back the bits that matter most — your family’s files, your media library, your private data — and put them on hardware you control, in your own home, under your own roof.

A home server is a manageable piece of that. It doesn’t fix everything. But it feels, if nothing else, like a small act of sanity in a landscape that increasingly doesn’t have room for them.

How it’s actually going

The server has been running for over two years. My maintenance routine is occasionally SSHing in, running a quick systemctl status on whatever I’m curious about, and doing the odd apt upgrade. That’s about it. The machine doesn’t demand attention. It just runs.

My wife uses it, and all she knows is that it was created by a wonderful man who’s a Linux enthusiast and a tinkerer — I may be editorialising on the ‘wonderful’ part, but the Linux bit is accurate — and that’s all she needs to know about it. The kids use it without knowing what a server is. What they see is a shared folder that works from any device in the house, and a streaming service that doesn’t have ads and never tells them “this content is not available in your region.”

It works well enough that I’ve put together a second one for family elsewhere — when a decent mini PC comes up at a good price, it’s hard to talk yourself out of it.

Total monthly cost: zero, beyond whatever the electricity works out to for a 10–15 W device running continuously. At most household electricity rates, that’s a few euros or dollars a month. Less than a single streaming service with ads.

No drama, no server room, no sysadmin background required. Just a small box, a free operating system, and a couple of weekends of following documentation. The goal was to build something I could stop thinking about.

That part worked.

If the setup itself sounds appealing, I wrote up the commands and decisions in the right order in a companion post — a rough guide rather than a comprehensive manual, but enough to get started.