Homelab
The services my family uses (a photo frame, a shared calendar, file sync, short links) on a Raspberry Pi and a repurposed laptop, behind one Cloudflare Tunnel and with zero open ports.
How traffic gets in
- Internet
- Cloudflare: TLS + Access
- Tunnel, the only way in
- Traefik on the Pi
- Containers on the Pi and a repurposed laptop
The problem
I wanted to host my own services at home without opening ports on the router, and without losing everything when a machine dies.
What I built
- One Cloudflare Tunnel is the only way in. Traefik routes each subdomain to the right container, and admin screens sit behind Cloudflare Access. Twelve routes, zero open ports.
- Deploy on push. GitHub Actions redeploys only the stacks that changed, using an Access service token instead of an open deploy webhook.
- Data lives outside the containers, secrets stay out of git, and encrypted backups go to GitHub automatically.
- Heavier services run on a repurposed laptop with an SSD instead of the Pi’s SD card, like Nextcloud for the family calendar.
Before the tunnel
I already hosted databases for classmates on my home server, and in January 2026 I gave that its own name and documentation site: “Max as a Service”. The first versions simply opened ports on my router. That taught me a lot about networking, and about how not to secure a database. Today nothing is opened: everything goes through the tunnel.
What went wrong
The Pi’s SD card died in the summer of 2026 and took the setup with it, so I rebuilt everything as code in git.
Status
Running, and used by my family and friends.