If you’re just venturing into self-hosting or rebuilding your server — it’s useful to check what people are actually running in home labs in 2026. I’ve assembled a current “stack of defaults” by category: not a top-for-top list, but a working set that’s easy to pick from. Where appropriate, with alternatives and sober assessments.
Reverse proxy and container management
The entry point for everything else. For beginners — Nginx Proxy Manager (web UI, Let’s Encrypt in a couple of clicks). For those who’ve got the hang of it — Caddy (automatic HTTPS right in the config) or Traefik (dynamic routing for Docker). Container management: Docker Compose as the base and Portainer for the UI; if you’ve outgrown a single host — look toward K3s (lightweight Kubernetes).
Media
Here the practical standard is Jellyfin: fully open, no subscriptions, and in the last year the plugin ecosystem has closed the feature gap with Plex. In the stack it’s paired with an arr-set: Sonarr/Radarr (TV/movies) and Prowlarr (indexers) for library automation.
Photos
Immich — a replacement for Google Photos with ML features (face recognition, object search), actively developed, mobile apps with auto-backup. Practically the default choice in 2026.
Files and productivity
Nextcloud remains a Swiss Army knife (file sync, office suite, calendar, contacts, video calls). For a wiki — BookStack (for family/personal) or Outline (team knowledge bases).
Dashboards, monitoring, backups
The infrastructure start page — Homepage or Dashy. Monitoring: Uptime Kuma for “up/down” and alerts, Grafana + Prometheus for deep metrics; for resource-saving — VictoriaMetrics as a lighter replacement for Prometheus. Backups — a mandatory but often overlooked layer: without them the whole stack is “until it burns.”
AI and automation
The trend of the year is local AI as part of the stack: Ollama to run LLMs and Open WebUI as a ChatGPT-like interface on top. More and more ML features are integrated directly into services (the same Immich).
VPN and access
WireGuard has finally displaced OpenVPN as the standard. For mesh access — Tailscale (or self-hosted Headscale if you don’t want to rely on a third-party coordinator). Single entry point — Authentik (SSO/OIDC before your services).
Notable trend: “lighter” replacements for heavy ones
Another 2026 trend is moving to lighter alternatives: Vaultwarden instead of Bitwarden, Gitea (or Forgejo) instead of GitLab, VictoriaMetrics instead of Prometheus. Less resource-hungry, easier to operate on home hardware.
Sobering assessment
- This is a guide, not dogma. “What’s popular” ≠ “what you need.” Don’t carry the whole list — tailor it to your tasks, or you’ll end up with a zoo that no one will maintain.
- The collection reflects the mainstream, not the absolute truth: each item has worthy alternatives (Plex, Seafile, Grafana stack itself, etc.), and the choice is often taste-driven.
- The main open point for most is backups and updates. A pretty dashboard without a recovery strategy is an illusion of reliability.
- More services = larger attack surface. Each exposed service is a potential hole; hence the importance of a reverse proxy, SSO (Authentik) and minimal public ports.
What to do
- Start with the foundation: Docker Compose + reverse proxy (NPM/Caddy) + one or two services that you actually need, not “everything at once.”
- Right away bake in three things everyone postpones: backups, monitoring (at least Uptime Kuma) and a single sign-on/minimum public ports.
- Local AI (Ollama + Open WebUI) add when there’s a free GPU/memory — it’s nice, but not the top priority.
- Don’t chase trends: lightweight alternatives (Vaultwarden, Gitea) are often more fitting for home hardware than “grown-up” counterparts.
Sources
- The 2026 Homelab Stack — what self-hosters are actually running (elest.io)
- Awesome-Selfhosted — large catalog of self-hosted software
What in your stack is immutable, and what did you recently swap for something lighter? And how are you doing with backups — honestly?