Why I self host my servers and what I've recently learned

Original Article ↗ Hacker News Discussion ↗

Self‑hosting home servers remains attractive for privacy, control, cost savings, and as a learning tool, but commenters stress how quickly it becomes a critical dependency with real-world risks: succession planning if the operator dies, complex backups and restores, security, and dealing with flaky VPS providers or residential ISPs. Many describe a pragmatic middle ground—self‑hosting only some services, offloading “too critical” ones like email and password managers to reputable SaaS, and using tools like Proxmox, NixOS, containers, or turnkey GUIs to balance convenience with reproducibility. There is also a recurring theme that future growth will depend on more user‑friendly “indie hosting” platforms that make these benefits accessible to non‑experts without heavy command‑line or ops expertise.

Succession, responsibility, and family access

  • Several commenters emphasize a hidden risk: if the self-hoster dies or is incapacitated, family and friends may lose access to critical data and services.
  • People now plan “home succession”: rsync/USB copies to spouses’ laptops, printed instructions in safes, flash drives with key docs, and notes about what will break (email, domains).
  • Many note that most homelab data will never be accessed after death; focus should be on a short list of truly important documents and simple, non-technical recovery paths.

Critical services: what not to self-host

  • Multiple participants avoid self-hosting password managers and email, considering them too critical.
  • Others report outages on self-hosted vaultwarden that locked them out at bad times, prompting moves to hosted Bitwarden or 1Password.
  • Offline backups/exports of password vaults are suggested as a compromise.

Containers vs NixOS/Guix and packaging philosophy

  • Big subthread debates Docker vs NixOS/Guix System.
  • Pro-Nix side: declarative configs, reproducibility, per-app dependencies, low overhead, one-line service enables (e.g., services.uptime-kuma.enable = true).
  • Skeptical side: Nix is opinionated, has a learning curve, and containers remain easier since most self-hosted apps ship Docker images; containers also act as an “escape hatch” when no Nix package exists.
  • Some run NixOS but still use containers (podman/systemd) for awkward software.

Economics and practicality of self-hosting

  • Mixed views: some find cloud storage (e.g., GCS, Google Drive) surprisingly expensive or cheap depending on workload.
  • One example: moving Prometheus object storage from GCS to self-hosted MinIO on a VM cut a cloud bill by ~70%.
  • Others stress that for homelabs the real cost is time, power, hardware depreciation, UPS, and cooling—worth it only if learning or control are primary goals.
  • “True” self-hosting is debated: some say only on-prem counts, VPS is not; others see that distinction as unimportant.

Ease-of-use, “indie hosting”, and non-technical users

  • Thread predicts a split between hobbyist “kit-car” self-hosters and a future “indie hosting” world: turnkey, GUI-first, privacy-respecting, minimal tech knowledge.
  • Non-technical users ask for solutions without command line; suggestions include NAS GUIs, /r/selfhosted resources, Yunohost, FreedomBox, Caddy, and GUI-oriented distros.
  • Some are building simpler web servers or tunneling services to make exposing home services as easy as installing an app and clicking through OAuth.

Security, email, and exposure

  • Self-hosted email is described as increasingly difficult: residential IP blocks, port 25 filtering, reverse DNS requirements, SPF/DMARC/DKIM, and spam blacklists that often distrust home or cloud IP ranges.
  • Advice: start on a reputable VPS, use distro packages with unattended security updates, or avoid directly exposing home networks and instead use VPN/overlays like Tailscale.

Home hardware, Proxmox, and infrastructure

  • Hardware stacks discussed include Proxmox clusters, ZFS with HBAs, Pi 5s, repurposed laptops, and low-power thin clients (e.g., Wyse 5070).
  • Proxmox + ZFS is popular but can be write-heavy on SSDs; tuning logging and ZFS caching can reduce wear.
  • VLANs, privoxy, OpenWRT on Mikrotik/Zyxel, and ad-blocking proxies are cited as major quality-of-life milestones.
  • Some question using a full three-node Proxmox cluster and off-site object storage (Wasabi) for relatively simple home workloads.

Government and public data on private platforms

  • Concern that local governments publish “public” documents via Google Drive, YouTube, or Facebook, forcing residents into big-tech ecosystems or complex DNS blocking exceptions.
  • Others argue bureaucratic friction for official web publishing pushes staff toward quick consumer tools.
  • Related worries about DMVs and courts outsourcing identity/document handling to private vendors (e.g., ID verification services).

Power, UPS, and reliability

  • UPS behavior is discussed; in some environments UPS failures caused more outages than utility power.
  • Lithium (especially LiFePO4) vs lead-acid vs emerging sodium-ion batteries are compared: lithium and sodium promising far longer life and cycle counts, but sodium adoption perceived as slow.
  • For homelabs, simple Li-ion UPS units are seen as attractive but real-world experience is limited in the thread.

Miscellaneous tools and tips

  • Recommended self-hosted apps and patterns: Paperless-ngx for documents, Komga (also for ebooks), calibre-web, vaultwarden, KeePassXC synced via Syncthing, Caddy for auto-TLS, Tailscale for secure remote access.
  • Some praise OpenBSD’s integrated services and detailed upgrade FAQs as particularly self-host-friendly.
  • VPS-based “dedicated servers” are suggested as a sweet spot: much cheaper than hyperscale cloud, with less ops burden than full on-prem.
  • Several report poor reliability and support from specific budget VPS providers, prompting migrations to more reputable hosts.