Uncloud

Lightweight container orchestration across a network of Docker hosts — “the missing middle between Docker and Kubernetes”. Compose-format services, WireGuard mesh with NAT traversal, built-in DNS service discovery, zero-downtime rolling deploys, no control plane (peer-to-peer cluster state). Zero-downtime rolling deploys are built in — the exact semantics the zero-downtime-compose war story had to hand-roll (redispatching proxy + health-gated replacement; see Reverse proxies > Deploy semantics). Ingress = built-in Caddy per machine, auto-generated Caddyfile from published ports, automatic Let’s Encrypt; 0.21 added clustered cert storage via the caddy.storage.uncloud module so multi-machine ingress behind one LB shares ACME tokens/certs (stock Caddy image lacks the module — pre-built ghcr.io/unlabs-dev/caddy-uncloud or xcaddy build; details and repo links in Reverse proxies > Uncloud and standard Caddy). Imperative-over-declarative by philosophy — the anti-GitOps-reconciler stance, kin to Musk engineering process step 5 (automate last).

Details and stats: uncloud (OSS) · related: Open source PaaS (Uncloud = the orchestration layer under a PaaS, not one) · Homelabs, pi-cluster (OSS) (the K3s alternative at the same scale point)