pizz.dev

My homelab

This website is not rented from a hosting company: it runs on a few small computers in my home, together with my other projects. Looking after them myself is how I learn what it takes to keep a service online and safe.

How my homelab is put togetherVisitors connect to Cloudflare, which forwards each visit through a tunnel that each service opened from inside my home, so the router stays closed. The public services each run in their own box on a separate network, cut off from my home network by a firewall. Biblio-Bot has no tunnel: it only calls out to Telegram. I manage the servers only through a private network of my own devices. Everything runs on a cluster of three small computers, with checks, alerts and weekly backups.My home · the router stays closed: every link is opened from insidePublic network · internet onlyHome networkthe controlsmy own devicesfirewallThis websiteown boxTutorSlotown boxPiranhaown boxout to TelegramBiblio-Botown boxout to TelegramRacingown boxtunnelsComputer 1Computer 2Computer 3One cluster · the important boxes are copied to a second computersite checks · 5 minheartbeats · 1 minfrozen? restartsbackups · 4 weeksSafety nets · if something goes quiet, I get an emailencryptedYouCloudflare (security)MePrivate network

Hover over, tap or tab to a part of the picture to see what it does.

You
Your browser. It only ever talks to Cloudflare, over an encrypted connection: the padlock in the address bar.
Cloudflare
A security company that receives every visit first, blocks attacks and passes the rest on through the tunnels. Visitors never learn where my home is.
This website
Plain pages served by a small web server, in a box of its own, with its own tunnel.
TutorSlot
My booking site for private lessons, in its own box, with its own tunnel.
Piranha
The price search, on its way. Its box is ready, and the part that draws the pages cannot reach the internet at all, even if someone broke into it.
Biblio-Bot
The library bot needs no way in at all: it only calls out to Telegram. No tunnel, so nothing to knock on.
The public network
The network the public boxes live on. From it they can reach the internet, and nothing else.
The firewall
It stands between the networks. A public box cannot reach my home network, the controls or the other boxes, so a break-in stays inside one box.
My home network
Where the controls of the servers and my own devices are. Nothing from the internet reaches it.
Me
Looking after the servers, from home or from anywhere else.
Private network
A private, encrypted network between my own devices (Tailscale). It is the only way to the controls, and it never leads to the public boxes.
Three computers, one cluster
Three small computers working as one. The important boxes are copied to a second computer, so if one computer fails they can start again on another.
Safety nets
Every computer checks the public sites every five minutes, the services report in every minute, a frozen computer restarts itself, and every box is backed up each week, kept four weeks. If something goes quiet, I get an email.
My homelab
All of it sits in my home, and the router stays closed: every connection is opened from the inside.

How it works, in plain words

For the technically curious
Servers
Proxmox VE cluster of three nodes, ZFS replication for the guests that need it
Isolation
Each public service in its own LXC container or VM, on a segment of its own (Proxmox SDN, VXLAN) behind an OPNsense firewall: internet only, no home network, no other guests
Public access
One Cloudflare Tunnel per service, opened from inside; no open ports on the router
Administration
Tailscale only
Monitoring
Uptime checks from every node and service heartbeats on healthchecks.io, with email alerts; a hardware watchdog
Backups
Every guest, weekly, kept four weeks
This site
Astro, built to static files and served by Caddy, with a strict Content Security Policy