Self-hosting 101: what's worth running on your own hardware in 2026

Toolkit Blog · July 14, 2026 · Hardware & local AI · 9 min read

Self-hosting means running the software behind your photos, files, media and smart home on a computer you own, instead of renting it from a subscription service. In 2026 the barrier to entry has quietly collapsed: a mini PC the size of a paperback and one piece of software called Docker will comfortably run everything most households need. This is the honest beginner's map — what the hardware really costs, the one concept that makes it manageable, the handful of apps genuinely worth the effort, and the parts nobody warns you about.

What self-hosting is, and when it's actually worth it

Every service that "just works" from your phone — photo backup, streaming, notes, password sync — runs on someone else's computer, under their terms, at their price. Self-hosting flips that: you run the server, on hardware in your house, and the data stays on a disk you can hold. The payoff is real ownership and no monthly meter. The cost is that you are now the IT department.

The trigger for a lot of people in 2026 is watching a service they relied on change the deal. The clearest example is Plex, the popular media server: in April 2025 it started charging for remote streaming of your own media and raised its lifetime pass from $119.99 to $249.99^[2] — then on July 1, 2026 that lifetime price jumped again to $749.99^[3]. Nothing about the software you'd installed changed; the terms did. Self-hosting is the bet that you'd rather own the arrangement outright.

Be honest about when it isn't worth it, though. If a free or cheap cloud service does the job and you'd rather never think about backups, updates or uptime, keep using it — self-hosting trades a subscription for your own time and attention. The sweet spot is a service you use constantly, care about the privacy of, or are tired of paying a rising rent on.

The hardware: far less than you think

The single biggest misconception is that you need a rack of servers. You don't. For a first home server you have three sensible options, in rough order of cost:

• A computer you already own. Any desktop or laptop from the last decade — even an old one gathering dust — will run a starter stack. It's the free way to find out whether you enjoy this before spending anything.
• A Raspberry Pi 5. The current Pi is a genuine little computer: a quad-core Arm Cortex-A76 running at 2.4 GHz, up to three times faster than the previous generation, in RAM sizes from 1 GB to 16 GB, with a PCIe 2.0 lane for an M.2 SSD and gigabit Ethernet^[8]. It sips power and is ideal for lighter always-on jobs.
• A mini PC. The value champion of 2026. A small Intel N100 box — a four-core, roughly 6-watt chip — with 16 GB of RAM and an NVMe SSD draws only about 8–12 watts running a typical homelab, yet community testing shows it happily running 15–20 containerised services at once and hardware-transcoding 4K video for a media server via Intel Quick Sync^[9]. For well under the price of Plex's new lifetime pass, it will run your whole stack 24/7 for a few dollars of electricity a year.

Notice what's missing: an expensive GPU. Unlike running local AI models — where memory bandwidth is the bottleneck (see our companion piece on running LLMs on your own hardware) — ordinary self-hosted apps are light. RAM and a decent SSD matter far more than raw compute. Start with 8–16 GB of RAM and grow only if you actually run out.

Docker: the one concept that makes it manageable

If you take one idea from this piece, take this one. In the old days, installing self-hosted software meant wrestling each app's dependencies into your operating system, where they'd conflict and rot. Docker replaced that with containers: each app ships as a self-contained package with everything it needs, isolated from the others and from the host. You "run" an app in one command, and "remove" it just as cleanly, leaving nothing behind.

In practice you'll write a short docker-compose.yml file per app — a few lines declaring the image, its storage folder and its network port — and bring the whole thing up with docker compose up -d. Updating is pulling a new image and restarting. This is why a modest N100 box can juggle twenty services: containers are cheap, and Compose files make a stack reproducible and easy to back up. Learn Docker Compose first; every app below is distributed as a container, and once the pattern clicks the rest is copy-paste-and-adjust.

What's genuinely worth running

Ignore the "awesome-selfhosted" lists with a thousand entries; most people are well served by a handful of mature, actively maintained apps. As of mid-2026 these are the safe starting bets:

• Immich — photo backup. The app that talks the most people into their first server. It's a self-hosted photo and video manager with polished iOS and Android apps that back up your camera roll in the background, plus face recognition and natural-language "CLIP" search that run entirely on your hardware^[4]. With over 108,000 GitHub stars it's among the fastest-growing self-hosted projects ever^[4] — a credible replacement for Google Photos for most households. One caveat straight from its authors: it moves fast, so follow a real backup plan and read upgrade notes before updating^[4].
• Jellyfin — media streaming. Your movies, shows and music, streamed to any screen. Jellyfin bills itself as "The Free Software Media System," GPL-licensed, with — in its own words — "no premium licenses or features, and no hidden agendas," and "no tracking, phone-home, or central servers"^[1]. That last part is the contrast with Plex, which authenticates through its own cloud. If you want zero subscription risk, this is the pick.
• Home Assistant — smart home. The hub that ties your lights, sensors and plugs together and keeps them working when the internet is down. It describes itself as "open source home automation that puts local control and privacy first," processing everything locally with 1,500+ device integrations, and it's governed by a non-profit that structurally "can't be sold or acquired"^[5]. It's the antidote to smart-home gadgets that brick when a startup folds.
• Vaultwarden — password manager. A lightweight, Rust-built server that speaks the Bitwarden API and works with the official Bitwarden apps and browser extensions, purpose-built for self-hosting where the full official server would be "resource-heavy"^[6]. Your vault syncs across devices, but the encrypted database lives on your box. (It's an unofficial project, not affiliated with Bitwarden — keep backups^[6].)
• Nextcloud — files and more. "A safe home for all your data": your own Dropbox-style file sync plus calendar, contacts and mail, on a server of your choosing, AGPLv3-licensed^[7]. It's heavier than the others, so add it once you're comfortable.

Two honourable mentions: Pi-hole, the network-wide ad blocker that's the perfect first project — we have a full follow-along build in block ads on your whole network with a Raspberry Pi — and a dashboard like Homepage to see all your services in one place once you've got a few running.

The parts nobody tells beginners

The apps are the easy 20%. The unglamorous 80% is what separates a hobby that lasts from a pile of e-waste. Four things to internalise before you depend on any of this:

1. Backups are not optional. A single server is a single point of failure, and a self-hosted photo library with no backup is more dangerous than the cloud you left. Follow the 3-2-1 rule — three copies, two kinds of media, one off-site — which Immich's own authors put in bold at the top of their project^[4]. Automate it; a backup you have to remember isn't one.
2. Updates need a rhythm. Self-hosted software gets security fixes constantly. Set aside a little time monthly to pull new container images, and read release notes for anything storing data you care about — some projects ship breaking changes in minor releases^[4].
3. Remote access is where people get burned. Do not forward ports and expose these apps raw to the internet. Reach your services from outside with a VPN back to your network (WireGuard or Tailscale) or a properly configured reverse proxy with HTTPS. When in doubt, keep everything LAN-only and use the VPN.
4. Security hygiene. Unique strong passwords on every service, two-factor where offered, and keep the host operating system patched. A vault you host is only as safe as the machine under it.

Where to actually start

Don't try to build the whole stack in a weekend. A realistic path: install Docker on a computer you already own, stand up one low-stakes service — Pi-hole or Immich are ideal first projects — and live with it for a few weeks. Get comfortable with Compose files, updates and a backup routine on something that won't hurt if it breaks. Only then buy dedicated hardware, and only then add the services you'll actually depend on, like a password vault or your main photo library.

And know when to stop. Self-hosting is a genuine commitment of attention, not a way to save money in the short term; the mini PC and your time both cost something. If a service is critical, has no good backup story, and you can't tolerate a weekend of downtime while you fix it, leaving that one in the cloud is a perfectly rational choice. The goal isn't to host everything — it's to own the handful of things you care about most, on terms nobody can change out from under you.

Sources

1. Jellyfin — official repository (README), accessed July 2026
2. 9to5Mac — Plex announces Plex Pass price increase and paywall for remote streaming, accessed July 2026
3. Gadget Hacks (Cord Cutters) — Plex Lifetime Pass price increase, effective July 1, 2026, accessed July 2026
4. Immich — official repository (README), accessed July 2026
5. Home Assistant — official site, accessed July 2026
6. Vaultwarden — official repository (README), accessed July 2026
7. Nextcloud — server repository (README), accessed July 2026
8. Raspberry Pi — Raspberry Pi 5 product page, accessed July 2026
9. HomeLab Starter — Intel N100 mini PC builds: measured power and transcoding, accessed July 2026

Related: Running AI on your own hardware: local LLMs explained · Block ads on your whole network with a Raspberry Pi · Why Toolkit runs entirely in your browser