live
Homelab Infrastructure
A practical self-hosted stack split across an MKG server, HomeLab server, Raspberry Pi edge device, and isolated Digital server — with deployment, creative media, storage, and home services kept in the right boundaries.
Challenge
Needed reliable home services, private media, document management, password storage, deployment hosting, AI tooling, creative media generation, and client workflow support without pretending every workload belonged in one neat cluster. The real constraint was boundaries: family services, personal/operator tools, edge devices, creative pipelines, backup lanes, and David's photography infrastructure all needed different trust zones.
System choice
Split the system by role: HomeLab server for Home Assistant, HomeBridge, Frigate, TrueNAS SMB, and DNS backup; MKG server for Coolify, Jellyfin, Immich, Vaultwarden, Paperless, draw.io, AI/runtime, ComfyUI, Pascal, Blender, and operator services; Raspberry Pi for lightweight edge duties; Digital server isolated for David's photography workflows. Nginx Proxy Manager and internal routing expose only selected services.
Outcome
The public model now matches the actual operating model: home automation and family storage stay pinned to local hardware, MKG services and deployments live on the MKG server, creative media has its own MKG-local pipeline, and client-owned infrastructure remains isolated.