r/Proxmox • u/Dr_Iron_Devil • 12h ago
Community Showcase! My MCU-inspired homelab: ~140 Docker containers, 4 physical nodes, Proxmox, ZFS, and a virtual OpenWrt router
First post here! I've been lurking for a long time. Recently, I came across u/goblinmine's homelab diagram and knew I finally had to make one for my own setup. I forked their generator, adapted it to my infrastructure, and finally got it done! Everything is named after the MCU (Tesseract holds the space/containers, Bifrost is the bridge/router, Ultron is the gatekeeper, Agamotto handles time/backups, etc.). What started as a simple media server gradually snowballed into approximately 140 Docker containers across 10 Proxmox LXCs and four physical nodes, with a separate machine handling AI workloads.
Hardware
Tesseract (main server): AMD Ryzen 5 5600X, 32GB DDR4-3600, ASUS TUF B550M-Plus, Radeon RX 6600 XT, LSI 9300-8i SAS HBA, and a Realtek 2.5G NIC, all housed in a DAWG Y909 full tower (supports up to 17 HDDs). Runs Proxmox VE 9.1.
Tesseract's storage:
rpool: 2x 512GB NVMe in a ZFS mirror for Proxmox OS, LXC root disks, and/rpool/appdata.tank: 2x 4TB Seagate IronWolf in a ZFS mirror for important personal data (Immich photos, ownCloud, Paperless PDFs, music).scratch: 500GB WD Blue SATA SSD (single-disk ZFS) used as a sacrificial download staging area to prevent torrents from thrashing the main pools.eternity: MergerFS + SnapRAID media pool combining 2x 4TB IronWolfs (iceman,phoenix), a 2TB Barracuda (spiderverse), and a 2TB Samsung 970 EVO Plus NVMe (jarvis), protected by a 4TB Barracuda parity drive (hangman).Asgard (AI & Docker host): Mac Mini M4 with 32GB unified memory. Runs native Ollama for local LLMs alongside Open WebUI, Qdrant, AdGuard Home, Beszel Hub, Grafana + Loki, and a custom analytics stack.
Agamotto (backup server): Raspberry Pi 5 (8GB) in an Argon One M.2 case with a 1TB Samsung 980 PRO NVMe, running Proxmox Backup Server.
Watcher (external monitoring): Raspberry Pi 4 (4GB) running Uptime Kuma and a standalone NPM instance.
Network gear: BSNL FTTH (200/200 Mbps) with the ONT in bridge mode, feeding a TP-Link AX1500.
The PCIe and storage compromises
Fitting multiple NVMe drives, a GPU, and an HBA onto a micro-ATX B550 motherboard required some PCIe compromises. The RX 6600 XT operates at reduced PCIe bandwidth due to the motherboard's lane-sharing constraints. However, since it's primarily used for Jellyfin transcoding (Vision) and Immich ML (Edith), this hasn't been a significant bottleneck in my experience. The other interesting aspect is my MergerFS pool (eternity), which combines single-disk ZFS pools (iceman, phoenix) and ext4 drives (spiderverse, jarvis). It's a slightly unconventional arrangement. I have ZFS ARC hard-capped at 8GB to keep Proxmox from consuming too much of the available 32GB RAM.
Networking: Router-on-a-Stick
Instead of replacing my existing Wi-Fi router, I went with a virtual router-on-a-stick setup. Bifrost is a tiny OpenWrt VM (1 vCPU, 256MB RAM) on Proxmox that handles VLAN trunking, firewalling, and WireGuard. One of my primary design considerations was avoiding a situation where tinkering with Proxmox takes down the entire household internet. So, Asgard, Watcher, and Agamotto remain on the physical LAN, upstream of Bifrost. This means that if Tesseract or Bifrost goes down, essential services like Wi-Fi, DNS, external monitoring, and backups remain available. For internal segmentation, I've created five VLANs:
VLAN 10 – Management / Gatekeepers
VLAN 20 – Media
VLAN 30 – DevOps
VLAN 40 – Downloads
VLAN 50 – Sandbox
The physical LAN uses a static summary route to reach the internal VLANs, avoiding the need to configure individual routes on every client.
Services & Security
Instead of creating one LXC per application, I generally group applications into stacks, with one LXC per stack. Currently, that's 10 LXCs in total. Every host/container runs Beszel, Dozzle, and Portainer agents for monitoring, log visibility, and management. All externally accessible traffic passes through Ultron, which runs NPMplus with:
CrowdSec (bouncer + AppSec WAF)
Authentik SSO
IP allowlisting for services that should only be accessible through trusted networks or VPN Only a carefully selected subset of services is exposed to the public internet, such as Jellyfin, Immich, my portfolio Everything else is restricted to trusted networks and WireGuard VPN access. Downloads live in their own isolated VLAN on Quicksilver, running behind Gluetun + AirVPN with a kill switch.
Backups & Automation
Everything is automated using Semaphore UI (Ansible) on Friday, along with host-level cron scripts. Notifications are distributed through Gotify/iGotify via Apprise. My backup and maintenance workflow looks like this:
Nightly Proxmox backups of LXCs and
/rpool/appdatato Agamotto (PBS).Automated SnapRAID diff/sync, with safeguards to abort if deletions exceed a configured threshold.
Scheduled SnapRAID scrubbing.
Additional monthly backups of important personal data from
tankto PBS. The idea is to keep backups, monitoring, and essential infrastructure as independent as possible from the main Proxmox host.
What's next?
There are plenty of things I'd still like to improve. The homelab is very much a continuous learning project. I'm particularly interested in improving automation, local AI integration, storage management, and infrastructure observability. Open to any questions, roasts, suggestions, or alternative approaches! (Note: The diagram was built using Goblinmine/homelab-diagram. I also used AI to help organize my notes and polish this write-up so I wouldn't miss anything.)
P.S. Reposting this today as the original was removed earlier as it was posted outside showcase day. Happy to answer any questions about the setup!
