Self-hosting used to mean a Plex box and a Raspberry Pi running Pi-hole. In 2026 the list runs longer: developers are moving language models, password vaults, photo libraries, and build runners off rented infrastructure onto hardware they own. The reason is mostly arithmetic — a modest SaaS stack of notes, a password manager, photo storage, and a couple of API subscriptions runs $40 to $80 a month per person, and that figure keeps climbing. A used mini PC costs about what three months of that stack does.
mikeroyal's Self-Hosting Guide is the GitHub resource most people open when they start pricing that trade. We read through it to judge how well it works as a 2026 starting point.
What the Self-Hosting Guide actually covers
The repository is a single long README built as a table of contents — an index of tools and links, not a step-by-step manual. It groups self-hosting into the categories a year of the home-lab boom made familiar: home automation around Home Assistant, media servers like Jellyfin and Plex, private cloud storage with Nextcloud, network-wide ad blocking through Pi-hole, VPNs, container orchestration, backups, and monitoring. A separate section points at tooling for running AI models locally.
It is one of several guides the same maintainer keeps in this format, and breadth is the strength. If you don't yet know that Immich exists as a self-hosted photo library, or that Headscale is an open-source control server for Tailscale-style mesh networks, the guide surfaces those names fast — and the hard part of self-hosting is often knowing what to search for.
The weakness is the same coin flipped. A curated link list tells you what exists, not how the pieces fit or which combination earns your weekend. No opinion is baked in: Plex and Jellyfin sit side by side with nothing on the licensing and telemetry differences that push most developers toward one. Treat the guide as a map, not an itinerary.
A curated list is only as current as its last merge. Before committing to any tool you find here, open the linked project's own repository and check for recent activity. Self-hosting tooling moves fast, and the obvious pick from eighteen months ago may already have been overtaken.
Where self-hosting pays off
Two categories carry most of the value for developers right now: local language models and private networking.
Local LLMs are the headline. A model on your own GPU means no per-token billing, no rate limits, and no prompt data leaving the building — that last point matters the moment you paste proprietary code into a model. The guide lists the runtime layer (Ollama, llama.cpp, LM Studio, vLLM and similar) but skips the practical question of how much hardware you need. The rough numbers, using 4-bit quantized weights:
| Model size | Approx. VRAM (4-bit) | Realistic use |
|---|---|---|
| 7-8B | 5-6 GB | Autocomplete, summarization, simple agents |
| 13-14B | 9-11 GB | General chat, code review |
| 32-34B | 20-24 GB | Stronger reasoning, longer context |
| 70B | 40+ GB | Approaches hosted mid-tier quality |
A consumer GPU with 24 GB of VRAM runs the 32B class comfortably and reaches into 70B with aggressive quantization. That is the 2026 sweet spot — capable enough for daily coding help, expensive but not absurd.
Private networking is the quieter win. WireGuard, in the mainline Linux kernel since version 5.6, is the modern default the guide leans on. Its codebase is small enough to audit in an afternoon — the opposite of the configuration sprawl OpenVPN accumulated. Pair it with Tailscale or self-hosted Headscale and you get an encrypted mesh between your home server, your laptop, and a cheap VPS without exposing a single port to the public internet. That detail is the real security upgrade: most home-lab breaches are an exposed admin panel, not a broken cipher.
Not everything belongs on your own hardware, though. Email is the classic trap — self-hosting a mail server in 2026 means fighting deliverability, IP reputation, and spam filtering indefinitely, and a single misstep drops your mail into junk folders silently. The same logic covers anything whose value is uptime and reputation rather than the software itself. A newsletter fits there: what you pay for is reliable inbox delivery, a managed-service problem rather than a home-lab project.
A first build that doesn't eat your weekend
The guide's failure mode for beginners is the urge to stand up a dozen services at once. A self-hosted setup you abandon after a month because it demands constant attention costs more than the SaaS it replaced.
A more durable order:
- Start with one box. A used mini PC or a Raspberry Pi 5 is plenty — don't buy a rack.
- Install one service: Pi-hole or AdGuard Home. Network-wide ad blocking is the lowest-risk first win, since switching it off reverts cleanly if it breaks.
- Add WireGuard so you can reach the box from outside without forwarding ports.
- Only then add the heavier services — Nextcloud, Immich, a local model runtime — one at a time, with a backup in place before each.
Two costs the guide underplays. A server is only as safe as its last backup — self-hosted means you are now the one paged at 2 a.m., so budget for the 3-2-1 rule (three copies, two media types, one off-site) before anything irreplaceable lands on the box. And a GPU drawing 200-plus watts around the clock is a visible line on your power bill, so run models on demand rather than idling.
The discipline that makes self-hosting pay is restraint. Move the workloads where ownership genuinely beats renting — models, files, networking — and keep paying for the ones where a managed provider quietly absorbs a problem you would rather not own.
Originally published at pickuma.com. Subscribe to the RSS or follow @pickuma.bsky.social for new reviews.
