Dev.to
7/6/2026

The original title is: "The part of a PaaS you use most should have the least power — so I built Mooring"
Original: The part of a PaaS you use most should have the least power — so I built Mooring
Short summary
Author built Mooring, a security-first self-hosted PaaS for Docker that separates read and write planes: dashboards run unprivileged via read-only socket proxy, while deployments are gated separately. It's a single Go binary with SQLite that auto-generates hardened Dockerfiles and Docker Compose, eliminating manual reverse-proxy config and plaintext secrets. Positioned as the security-conscious alternative to Coolify, Dokku, CapRover, and Kamal.
- •Read plane (dashboards) runs unprivileged; write plane (deploys) is gated—core security architecture philosophy
- •Single Go binary, SQLite state, auto-generates hardened Dockerfiles and Docker Compose—zero node_modules or runtime build artifacts
- •Direct competitive positioning against Coolify, Dokku, CapRover, Kamal, emphasizing security posture as key differentiator
Generated with AI, which can make mistakes.
Is this a good recommendation for you?


