AI-augmented homelab operations, from multi-agent orchestration to automated content pipelines. This wiki documents how Claude Code and agentic patterns accelerate infrastructure work.
4-Layer Agentic Architecture # A framework for organizing AI-assisted automation into composable layers:
Building a 4-Layer Agentic Architecture for Claude Code: Justfile, Commands, Skills, and Agents, where each layer has a single responsibility Skill Development # The Skills layer outgrew a folder of one-off scripts. It is now a curated collection of 60+ skills with a shared prefix: journaling, homelab health checks, code mentoring, adversarial review, and build-plan generation. Skills live in a central configuration repo and deploy to every machine via symlink, so a skill written on the laptop shows up in the homelab session an hour later.
This homelab uses segmented networks, policy enforcement at the edge, and redundant services for the few components that would otherwise make a bad afternoon much worse.
Architecture at a glance # The design separates management, infrastructure, isolated workloads, connected devices, and out-of-band administration. The firewall enforces the boundaries. Internal services use role-based names, and public access is mediated through an authenticated edge rather than direct exposure of individual workloads.
Automation is the backbone of my homelab. This wiki covers the tools, patterns, and workflows that keep 50+ services running with minimal manual intervention.
Automation Stack # n8n Workflow Automation # n8n is my primary workflow automation platform—think Zapier/Make but self-hosted with full code access.
Visibility into 50+ services requires centralized logging, proactive alerting, and dashboards. This wiki covers my monitoring stack and the patterns that make it work.
Monitoring Stack # Graylog Centralized Logging # Graylog is my log aggregation platform—collecting, processing, and visualizing logs from across the homelab.
Enterprise security principles applied to a homelab. This wiki covers the layered security architecture — from next-gen firewall policies to XDR threat detection to certificate lifecycle automation.
Firewall Architecture # The Palo Alto Networks PA-440 provides the network security foundation with App-ID, zone-based policies, and centralized logging. Full details in the Networking wiki — including security zones, VLAN trust levels, and DNS proxy configuration.
My homelab runs on a 4-node Proxmox VE cluster hosting 50+ LXC containers and VMs. This wiki documents the architecture, conventions, and lessons learned.
Proxmox Cluster Architecture # Cluster Specifications # Node Storage Type CPU RAM Primary Workloads Node 2 ssd-data LVM-thin 4 cores 16 GB PBS, Development Node 3 zdata ZFS 4 cores 32 GB Databases, DNS-Primary Node 5 ssd-data LVM-thin 4 cores 16 GB Graylog VM, DNS-Secondary Node 6 zdata ZFS 4 cores 32 GB Docker-Main, HA services Total Resources: