home.neusix.org: A Self-Hosted Production Stack
A serious, production-grade self-hosted private cloud — Proxmox, Kubernetes with ArgoCD, Keycloak, Garage S3, Wazuh SIEM, and more — run continuously as a discipline, not a demo.
home.neusix.org is my personal infrastructure environment — and it's not a toy lab. It's a production-grade private cloud running on enterprise hardware, built and operated with the same discipline I'd apply to a client environment, because I believe that's the only way to keep self-hosting skills genuinely sharp.
Compute & Orchestration
The foundation is Proxmox VE running across multiple nodes on enterprise-grade hardware. On top of that sits a Kubernetes cluster managed with ArgoCD for GitOps-driven deployment — every workload change flows through Git, not ad-hoc kubectl commands.
Identity, Security & Secrets
Keycloak provides centralized authentication and SSO across the stack — a cluster I've maintained continuously for three years, including through major version upgrades. OpenBao handles secrets management, and Wazuh runs as a SIEM, giving the environment genuine security monitoring rather than an afterthought.
Storage & Object Storage
Object storage is split across MinIO and Garage — a Rust-based S3-compatible store I've increasingly preferred for its simplicity and resource footprint, typically run with a replication factor of three. Harbor serves as the container registry, with images promoted through the same GitOps flow as everything else.
Networking & DNS
Technitium DNS handles internal name resolution across the environment, supporting the segmented network design that ties the Kubernetes cluster, storage nodes, and management plane together.
Backup & Resilience
Proxmox Backup Server (PBS) provides scheduled backups across the cluster, and Portainer gives a quick operational view of container workloads when I need to check on something without going through the full GitOps loop.
Automation
n8n ties together the operational glue — scheduled jobs, notifications, and integrations between the self-hosted stack and external services. Combined with ArgoCD, the goal is that very little in this environment requires a manual SSH session.
Why This Matters
Most of what I design for clients — multi-node Proxmox clusters, ZFS storage layouts, Valkey/Redis topologies, Keycloak SSO, S3-compatible object storage with real replication — I run myself, continuously, at home. It's the difference between knowing how these systems are supposed to work and knowing how they actually behave at 2am during an upgrade.
