Almost every self-hosted deploy tool — Coolify, CapRover, Dokploy, Portainer — works the same way: you install it on a server, it runs as a persistent service, and you manage everything through a web dashboard served from that server. DeployOS is built differently on purpose, and the reasoning is worth spelling out rather than just asserting.
What "runs on your server" actually costs
A control-panel service running on your server is a container that needs updating when a CVE lands, a process that needs monitoring, and — critically — a web-exposed admin interface with its own authentication surface, usually on a port you have to remember to firewall correctly. None of that is hypothetical: self-hosted panel software has had real authentication and RCE vulnerabilities disclosed over the years, precisely because "web dashboard with admin privileges over your infrastructure" is an attractive target.
The alternative: nothing runs there but your apps
DeployOS is a native desktop app (macOS and Windows). It connects to your server over SSH, on demand, to do exactly the operation you asked for — deploy, check logs, run a backup — and then it's done. There's no DeployOS process listening on your server between actions. No admin dashboard to patch. No extra port beyond the ones your actual deployed apps need (typically just 80/443).
What this trades away
This is a real trade-off, not a strictly-better argument. A web dashboard means you can manage your infrastructure from any browser, on any machine, without installing anything — genuinely convenient if you manage servers from multiple computers or want a teammate to have web access without giving them an app install. DeployOS's model means the app itself has to be installed wherever you want to manage from, and credentials live in that machine's OS keychain rather than a shared web session.
Why we think it's the right trade for the target user
DeployOS is built for developers running their own handful of VPS instances, not a platform team managing infrastructure-as-a-service for others. For that audience, "one more attack surface, permanently exposed, for the sake of browser convenience" is usually not the trade they'd choose if it were explained plainly — so we chose the other side of it by default.
If you're evaluating DeployOS against a panel-based tool, this is genuinely the core architectural difference — everything else (templates, databases, backups) is table stakes both sides have. See the fuller breakdown on the DeployOS vs Coolify comparison page.