Homelab
The household runs its own services: files, passwords, code, plans, chat, recipes and a game server for friends. They live on a small rack at home and on rented servers, joined by a private mesh network.
Hardware
- Two Proxmox VE nodes for containers and virtual machines.
- A NAS for files and the first copy of every backup.
- A Cisco router and two Cisco switches.
- UniFi access points, with a separate network for guests.
- Rented virtual servers in Germany for everything that has to be reachable from outside.
What runs on it
- Code hosting with its own CI runners.
- File sync, calendars and contacts.
- A password manager for the family.
- Project planning on a self-hosted board.
- A chat server with bridges to other messengers.
- Speech to text for the household's recordings.
- Private web search, a PDF toolbox and a recipe collection.
- A Minecraft server for friends.
Network and access
- The network is split into segments by trust: servers, family devices, smart home, guests, and a DMZ for the game server.
- A WireGuard mesh (NetBird) joins home and the rented servers, so nothing at home needs an open port.
- One sign-in (single sign-on) for the services that support it.
- Who may talk to whom is written down as code in one policy file, and a zone-based firewall is being phased in from it.
- DNS filtering for every device in the house.
Backups
- Nightly encrypted borg archives go to the NAS, from the rented servers first and the machines at home next.
- An encrypted off-site copy of the NAS with restic is being built.
- Restore tests come before any of it counts as done, because a backup is only proven once it has been restored.
Watching it
- Uptime Kuma checks every service from inside and outside, and alerts arrive as chat messages.
- Beszel collects the metrics of each host.
- Every backup reports when it ends, so a silent night is an alarm too.
How it is run
- One Git repository holds the inventory, the network configuration, the runbooks and the scripts that apply them.
- Work is planned on a self-hosted board, one item at a time, and every change lands as a commit.
- Fedora wherever possible, to keep one dialect of Linux.