Every developer eventually hits the same wall: you write a beautiful, stateless application, and then you burn an entire weekend fighting with ingress configurations, TLS certificates, and YAML files just to get it online.
On one extreme, you have the bare-metal VPS - sovereign and cheap, but requiring you to act as a full-time systems administrator. On the other extreme, you have the managed PaaS and Kubernetes ecosystems, which offer frictionless deployments but trap you in proprietary platforms or bury you under enterprise-grade cognitive overhead.
You can have both sovereignty and ergonomics. While open-source tools like Dokku, Coolify, and CapRover are fantastic solutions for self-hosting, they largely default to monolithic designs. In a monolithic setup, if your orchestration layer crashes during a heavy build or deploy, your routing table and active containers are suddenly in an inconsistent state because they all share the same execution context. Even Kamal - arguably the closest philosophical cousin in this space - relies heavily on remote SSH execution rather than maintaining a persistent, state-aware connection to the cluster.
By abandoning strict multi-tenant isolation and aggressively decoupling state from execution, we can architect a deployment engine that feels like a managed cloud but runs comfortably on a $5 DigitalOcean droplet - sovereign infrastructure on your own terms.
