Manoj Yadav

Homelab & Infrastructure

A living document of the hardware, network layout, power footprint, and core services powering my self-hosted homelab.

## Philosophy I run my homelab like a miniature production environment with two ground rules: 1. **Efficiency over raw compute**: Thin clients and low-power SBCs handle the 24/7 workloads. Heavy rigs run on-demand. 2. **Reproducibility**: If any machine dies today, everything on it must be restorable from Git repositories, Docker Compose definitions, and automated backups in under an hour. --- ## Hardware Fleet | Device | Base OS | Primary Role | Power | Operating Hours / Day | | :--- | :--- | :--- | :--- | :--- | | **HP T630 #1** | Debian | Docker Host & Komodo Core (Fleet controller) (24/7 utility workloads) | ~15W | 24 hrs (Always-on) | | **HP T630 #2** | Debian | Dev env (all development happens here) | ~15W | ~8–12 hrs (Active Dev) | | **HP ProDesk G3 600 #1** | Debian | All automation pipeline, from n8n to AI harness | ~15W | 24 hrs (Always-on) | | **HP ProDesk G3 600 #2** | Proxmox VE | Hypervisor for ephemeral test VMs and LXCs | ~15W | ~4–6 hrs (On-demand) | | **TrueNAS Box** (Ryzen 5600G, 8TB) | TrueNAS SCALE | Central storage, backups & media server with dockerised apps | ~65–70W | 24 hrs (Always-on) | | **Raspberry Pi 4B #1** | HAOS | Home Assistant (Dedicated smart home hub) | ~4W | 24 hrs (Always-on) | | **Raspberry Pi 4B #2** | DietPi | Utility Docker stack & lightweight network services | ~4W | 24 hrs (Always-on) | | **Raspberry Pi Zero 2 W #1** | Batocera | Retro emulation frontend | ~1W | ~1–2 hrs (On-demand) | | **Raspberry Pi Zero 2 W #2 + Fire TV Stick** | LibreELEC / Fire OS | Dedicated media playback & streaming (Fire TV Stick has its own perks: native Widevine DRM for OTT apps like Prime and Netflix, while Pi Zero runs lightweight Kodi/Jellyfin) | ~2–5W | ~3–4 hrs (Evenings) | | **Workstation** (Ryzen 5600X, RTX 3050) | Desktop OS | Heavy dev, local LLMs (Ollama), and gaming | ~150W+ | ~3–5 hrs (On-demand via WOL) | --- ## Network Architecture & VLANs Network isolation is managed through a TP-Link smart switch and router on a `10.0.X.X` addressing scheme: * **VLAN 10 — Management (`10.0.10.0/24`)**: Proxmox console, switch web GUI, router admin, and IPMI/out-of-band management. Accessible only through hardwired admin ports or private VPN tunnels. * **VLAN 20 — Servers (`10.0.20.0/24`)**: Docker hosts, TrueNAS storage, databases, and core application servers. * **VLAN 30 — IoT (`10.0.30.0/24`)**: ESPHome sensors, smart switches, and smart plugs. Strictly firewalled: zero internet access and blocked from reaching any local machine except the MQTT broker on VLAN 20. * **VLAN 40 — Trusted Clients (`10.0.40.0/24`)**: Everyday personal devices: laptops, phones, gaming PC, and media clients. * **VLAN 50 — Guest (`10.0.50.0/24`)**: Internet-only access for visitors; completely isolated from all internal subnets. --- ## Power Budget (Indian Context) Electricity in Indian cities averages around **₹10 / unit (kWh)**. Keeping running costs predictable was a core design constraint from day one. * **24/7 Always-on baseline**: ~139W continuous draw across the primary thin client (T630 #1), automation host (G3 600 #1), Raspberry Pis, and the TrueNAS storage pool. * **Monthly power consumption**: ~139W × 24 hrs × 30 days ≈ **100 kWh (units) per month**. * **Monthly electricity bill**: 100 units × ₹10/unit ≈ **~₹1,000/month**. The gaming workstation (RTX 3050), secondary Proxmox node, and media frontends are excluded from the 24/7 baseline and wake via Wake-on-LAN (WOL) only when actively in use. --- ## Core Software & Infrastructure Stack * **Reverse Proxy & Ingress**: Traefik with automated wildcard certificates via Let's Encrypt DNS-01, integrated with Cloudflare DNS API and a local private CA fallback for internal-only domains. * **Identity & SSO**: Authelia forward-auth with 2FA/WebAuthn hardware key support. * **Fleet Orchestration**: Komodo Core & custom deployment tooling (`mDeploy`). * **External Connectivity**: WireGuard for direct, high-speed peer-to-peer tunnels into the home LAN, along with Tailscale in specific edge locations where NAT traversal or mesh networking is needed. * **Automations**: n8n workflows and custom Python agents running on the G3 600 #1 automation node. * **3-2-1 Backup Strategy**: - **3 copies** of all critical state (production data, local snapshots, offsite mirror). - **2 different storage media** (NVMe/SSD host drives + TrueNAS ZFS hard disk pool via Restic and Proxmox Backup Server). - **1 offsite copy** (automated, client-side encrypted Restic repositories pushed to secure cloud object storage). * **Smart Home**: Home Assistant OS + Zigbee and ESPHome via MQTT.