Sleep/wake orchestration for self-hosted side projects: a wire-protocol proxy approach instead of a full PaaS.
retained text
<!-- SC_OFF --><div class="md"><p>I built an open-source tool (Hobbyist) around one architectural bet and I'd like this community to poke holes in it.</p> <p>The bet: for small self-hosted workloads, you don't need Kubernetes-style orchestration; you need scale-to-zero on a single box. Hobbyist runs each project's Postgres 18, Docker apps, workerd-based functions, and queues in containers, and shuts them down entirely when idle. A proxy layer (Postgres wire protocol for the DB, HTTP for apps) intercepts incoming traffic and cold-starts the right container: ~170ms for Postgres, ~125ms for apps, on my hardware. Caddy handles TLS and routing; Tailscale covers private access; a daemon plus a 16-command CLI is the whole control plane. No Terraform, no K8s.</p> <p>Where I suspect it gets ugly, and where I'd value experienced eyes: connection storms on wake, health-checking containers that are deliberately dead, cert lifecycle across container replacement (currently an actual bug), and whether wire-protocol interception bites me on auth and TLS edge cases at scale.</p> <p>It's v0-alpha, not production ready, and the known-broken list is in the README (Linux queue producers, snapshot CLI, the cert issue above). Not selling anything — there's no hosted tier and no paid version coming.</p> <p>Repo: <a href="https://github.com/uziiuzair/hobbyist">https://github.com/uziiuzair/hobbyist</a></p> </div><!-- SC_ON -->   submitted by   <a href="https://www.reddit.com/user/uziiuzair"> /u/uziiuzair </a> <br /> <span><a href="https://www.reddit.com/r/devops/comments/1vyep15/sleepwake_orchestration_for_selfhosted_side/">[link]</a></span>   <span><a href="https://www.reddit.com/r/devops/comments/1vyep15/sleepwake_orchestration_for_selfhosted_side/">[comments]</a></span>
document fetched 2026-08-26 05:58 · canonical https://reddit.com/r/devops/comments/1vyep15/sleepwake_orchestration_for_selfhosted_side