Skip to main content
← Back to journal

Published on July 29, 2026

My homelab: what I self-host at home

One machine, containers, and most of my services under my own roof. A tour of my homelab, and why I keep a hand on my data.

My homelab: what I self-host at home

I host at home a good share of the services most people hand over to Google or Dropbox. Not out of stated principle, more out of reasoned mistrust: working in software long enough, you end up wondering where your files really land. Keeping control avoids depending on a service that shuts down, changes its pricing or reads what you store on it. And it happens to be a learning ground that is hard to beat. Here is what runs, and how it fits together.

One machine, containers

The architecture fits in a sentence: everything runs in Docker containers on a single machine, orchestrated with Docker Compose. Each service in its own container, with its volumes for persistence. No cluster, no Kubernetes, no high availability. It is enough for personal use, and above all it stays simple to diagnose when something breaks.

The entry point is Nginx Proxy Manager. Each service has its own subdomain, and the proxy routes to the right container while handling HTTPS certificates through Let's Encrypt, automatic renewal included. The interface is graphical, which spares me editing Nginx files by hand: to get started with a reverse proxy, it is the most accessible option.

Access from the outside goes through WireGuard, my personal VPN, rather than exposing the services directly on the internet. When I am away and want to open one of my services, I bring up the tunnel and find the local network again as if I were home. The protocol is fast and light, clearly more so than older solutions like OpenVPN. To keep an eye on the machine, Prometheus collects the metrics (CPU, memory, disk, container status) and Grafana displays them.

Replacing Google, piece by piece

The core of the setup is about taking back control of personal data that, by default, would go to third parties.

Immich stands in for Google Photos: a timeline, face recognition, a mobile app that backs up the camera roll automatically. What matters to me is that the recognition and the machine learning run locally, with no photo passing through an external server. The trade-off is heavy memory use, and a project that moves fast: it is better to read the changelog before each update.

Nextcloud acts as a personal Drive, mostly to sync folders between my desktop and my phone and to share the occasional link. The platform is heavy and covers far more cases than I use, but for reliable storage and syncing it does the job. Vaultwarden, finally, handles my passwords: a Rust reimplementation of Bitwarden, lighter than the official server and compatible with every Bitwarden app. That one I recommend without reservation: minimal memory footprint, stable, the kind of service you end up forgetting because it never causes trouble.

Paper, and the rest of the everyday

Two quieter services settle everyday chores. Paperless-ngx manages the scans of my documents: invoices, administrative letters, all the paper that piles up. It runs OCR on each file and indexes the content, which lets me find any document through a full-text search. The detail that changes everything is the automation: a scanned document is dropped on a network location, a worker picks it up, analyses it and files it without my touching anything. Movary keeps the list of films I have watched. Nothing vital, but I forget quickly what I have seen, and a dated record beats a failing memory.

Backups, the real safety net

A homelab without backups is just an outage waiting to happen. Everything goes to Infomaniak, through their Swiss Backup offer combined with Restic. Restic encrypts the data on the client side before sending it: the files leave the machine already encrypted, and stay hosted in Switzerland. Even if the house burns down, I recover all my documents and photos. It is the kind of scenario you never think about until it happens.

None of this is set in stone, and the configuration keeps evolving. But the infrastructure is mine, from the hardware to the backups, and that is what counts.