The Stack: five self-hosted services that actually pay rent

On July 1, Plex’s lifetime pass went to $749.99. Fourteen months earlier it cost $119.99, and in between the company put remote streaming of your own files behind a subscription. Your hardware didn’t change. Your media didn’t change. The terms changed, because with a hosted service the terms are the product, and you don’t set them.

That is the honest case for self-hosting: you’re buying back dependency risk and paying for it in your own ops time. The dishonest case is most of what gets published, which is a hobby in a trench coat — a dozen containers recommended to people who will quietly abandon eleven of them. The question that matters is the exchange rate. Hours in, risk out.

So here is the shortlist that survives that test for a normal technical household: five services plus the glue that connects them, each with a maintenance bill and the specific failure mode that would make us pull the pick. One disclosure, once: this piece synthesizes project documentation and release notes, the community’s documented breakage, and our own reading of the configurations. It is not a multi-year lab study, and no list like this honestly is.

Pi-hole: the cheapest chokepoint in the house

Pi-hole turns one small machine into a DNS resolver that blocks ads and trackers for every device behind your router. The project’s pitch is a single line: “Install Pi-hole in one place and your entire network is protected.” The value is in the places browser extensions can’t go: smart-TV telemetry, in-app ads on phones. It replaces a per-device patchwork with a single point of policy.

The cost is front-loaded. It runs in a container or on a spare single-board computer, and setup is an evening at most. The v6 release in February 2025 folded the web interface and API into the core daemon and dropped the lighttpd and PHP dependencies; the project warns the upgrade is “strictly a one-way operation,” so you back up first. Our read on steady-state maintenance: one to two hours a year.

The failure mode is structural. Pi-hole is your DNS now, and when it’s down, the internet is down for everyone in the house who never signed up for this. The mitigation is a second instance or a fallback resolver configured at the router. The un-recommend condition: routine updates that break name resolution more than rarely. The v6 transition produced a flurry of post-release fixes, but not that, and the record since has been quiet. Who shouldn’t bother: anyone who travels a lot and leaves nontechnical family behind a single resolver.

Vaultwarden: best exchange rate, sharpest edge

Vaultwarden is an unofficial server, written in Rust, that speaks the Bitwarden client API, which means the official Bitwarden apps on your phone and in your browser work against a box in your closet. The README is plain about its status: not associated with Bitwarden, Inc., HTTPS required, and the maintainers “cannot be held liable for any data loss” — which is documentation-speak for take backups seriously.

Money first, because the money argument is weak. Bitwarden’s hosted premium tier runs about ten dollars a year. Nobody self-hosts a password vault to save ten dollars. You do it so the vault never leaves your network and never depends on a vendor’s pricing committee.

The failure mode is client drift, and it is already on the record. In January, users found that updated Bitwarden Android clients (2025.12.1 and later) refused to log in to older Vaultwarden servers, failing with “Missing the required MasterPasswordUnlock data property”; the fix was upgrading the server to 1.35.2 or later. Note what that incident actually demonstrates: the installs that broke were the ones whose owners had stopped updating. If Vaultwarden’s compatibility lag ever routinely stretched to weeks, we’d pull this recommendation the same month. Our read on the bill: fifteen disciplined minutes a month for updates, plus a quarterly restore drill you actually run. Who shouldn’t bother: anyone unwilling to automate both. Pay the ten dollars.

Jellyfin, or: reread the first paragraph

Jellyfin is the media server. GPL-licensed, “free to download, now and always,” no tracking and no phone-home, per the project. It replaces Plex, and the replacement case has been writing itself for fourteen months. In April 2025, Plex put remote playback of personal media behind a paywall (a Plex Pass, or a new Remote Watch Pass at an introductory $1.99 a month) and raised the lifetime pass from $119.99 to $249.99. On July 1 the lifetime pass went to $749.99, a change first covered widely by 9to5Mac, with the company explaining:

“we’re keeping it available at a price that reflects the real, ongoing value of the software.”

Jellyfin’s counter-offer is a price that structurally cannot do that. Its bill arrives in hours instead: hardware-transcoding configuration is the real sink, and the TV-platform clients are rougher than Plex’s. Our read: an evening to stand up, a few hours a quarter after that. The un-recommend condition: client apps on major TV platforms breaking after OS updates and staying broken across releases. Who shouldn’t bother: a household that mostly streams remotely to relatives’ devices and expects streaming-service polish. For them, honestly, the $1.99 pass is fairly priced.

Syncthing just runs

Syncthing is continuous peer-to-peer file sync: no central server, TLS between explicitly approved devices, your data only ever on machines you own. It takes over the sync duties of Dropbox or iCloud Drive. Two sentences of honesty here. Sync is not backup, because deletions propagate too; Syncthing pairs with a real backup, it doesn’t replace one.

Maintenance is the closest to zero on this list, which is why the one warning light matters. In October 2024, a maintainer announced the discontinuation of the official Android app, citing “Google making Play publishing something between hard and impossible”; the final release shipped with the December 2024 version, and community forks carry the platform now. The core project’s release train has kept rolling since. If that stagnation ever reached the desktop core, we’d pull the pick. Who shouldn’t bother: iPhone households — there is no first-party iOS client, and that alone disqualifies it.

Home Assistant, the one that bills you monthly

Home Assistant is the local-first smart-home hub: more than 1,500 integrations, automations that run in the house rather than in a vendor cloud, governed by the nonprofit Open Home Foundation, which by design “can’t be sold or acquired.” It replaces a shelf of vendor apps and, more to the point, the risk that any one vendor sunsets the cloud your light switches depend on.

It is also the most expensive item here in hours, and the project doesn’t hide it: a new release every month (2026.7 shipped July 1), each with its own backward-incompatible-changes section in the notes. Our read: an evening a month if you stay current. Skipping months doesn’t save time; it compounds the eventual jump. The un-recommend condition: a breaking-change cadence that starts regularly reaching ordinary households’ core automations. The record so far is breakage that’s documented, scoped to specific integrations, and absorbable in that monthly evening. Who shouldn’t bother: any home where the tolerance for “the lights don’t work” is zero and nobody will read release notes.

The glue, and the total

Tailscale holds it together: a WireGuard-based mesh that makes every service above reachable from your phone anywhere, no ports forwarded, free on the Personal plan. Note the irony without flinching: it is itself a hosted dependency, its coordination server is Tailscale’s, and the committed can swap in the self-hosted Headscale. We think the trade is fine. The point of this stack was never purity.

Add it up, on our read: twenty-five to forty hours the first year, maybe half that after. What those hours buy is not savings, mostly. It’s that no email can arrive announcing what your own infrastructure now costs.

Plex’s lifetime pass went from $119.99 to $749.99 in fourteen months. Jellyfin’s price over the same stretch didn’t move. It can’t.