Homelab platform — Proxmox, GPU, and a dozen services

What this is

My homelab is where I turn “I know how this works in theory” into “I’ve run it for months.” It’s a Proxmox setup with a GPU node for local model inference, and a growing fleet of services — task tracking, family scheduling, calendar sync, chore automation wired into Home Assistant — each living in its own LXC container, each running as a systemd service.

The physical layer is DIY down to the rack: the server rack and the PC test bench are both 3D-printed, because when you build the furniture your infrastructure lives in, you stop being afraid of it.

How it’s exposed

Nothing here binds a raw port to the public internet. Every service that needs to be reachable from outside goes through a Cloudflare Tunnel: outbound-only, so there’s no open port to scan, no NAT hairpin to maintain, and DNS plus TLS plus basic WAF handled at the edge. Public traffic lands on a *.wliered.com subdomain and is routed to the right container on the inside.

Why it matters

Running your own infrastructure is the fastest way to stop hand-waving about “production.” Deployments, backups, TLS, resource limits, observability, the quiet failure at 3 a.m. — you either deal with them or they deal with you. The same instinct that keeps a homelab boring is what any engineer needs to keep a production system from being exciting.

This is also the substrate for everything else on this site: every app I build runs here, self-hosted, behind the same tunnel.

Full story → The homelab, version 3 — the Unraid → Proxmox evolution, the services that earn their keep, and the 3D-printed rack.