Alternatives

Coolify is a mature, feature-rich self-hosted PaaS with builds, templates and a large UI, and it is the better choice for hosting apps today. Its coordinator commands servers over SSH. Decentralized.Host inverts that: hosts admit or refuse signed proposals under their own policy and sign what they observe. It has no build pipeline or templates and is not yet production-validated.

License

AGPLv3 / Apache 2.0 dual

Model

Self-hosted single/multi-server coordinator

Multi-server

Supported via SSH tunnel agent to remote servers

Git deploy

GitHub App / Webhooks / Git push via proxy

TLS

Traefik / Caddy automatic Let’s Encrypt

Dokploy offers a polished dashboard and Swarm clustering with Git-based builds. Decentralized.Host has no builds; its multi-host model is a Raft control plane that proposes work and sovereign hosts that admit it, connected by a userspace WireGuard mesh — validated so far on one machine only.

License

Apache 2.0

Model

Self-hosted single server (multi-server in Docker Swarm mode)

Multi-server

Supported via Docker Swarm clustering

Git deploy

GitHub / GitLab / Bitbucket webhooks

TLS

Traefik automated SSL certificates

CapRover is an established Swarm-based PaaS with one-click apps and a CLI. Decentralized.Host trades that convenience for signed intent, host-side admission, hash-chained ledgers and a published protocol, and is much younger.

License

Apache 2.0

Model

Self-hosted single/multi-node cluster (Docker Swarm)

Multi-server

Yes, leader and worker nodes in Docker Swarm

Git deploy

Captain definition files & git webhooks

TLS

Nginx reverse proxy with Certbot Let’s Encrypt

Dokku is a proven single-server, git-push PaaS. Decentralized.Host is multi-host by design, has no git-push builds, and focuses on verifiable state (desired, admitted and observed kept separate) rather than developer workflow.

License

MIT License

Model

Single server self-hosted mini-Heroku

Multi-server

Experimental via Nomad/Kubernetes scheduler plugins (primarily single-server)

Git deploy

Native `git push dokku main` over SSH

TLS

Let’s Encrypt plugin for Nginx

Heroku is a fully managed platform: you trust the provider with everything. Decentralized.Host is software you run on machines you control, where each machine keeps a veto over what runs on it. It offers none of Heroku's managed services.

License

Proprietary Cloud Service

Model

Managed Multi-tenant Cloud (AWS)

Multi-server

Managed automatically by Heroku platform

Git deploy

Pioneer of `git push heroku main`

TLS

Automated certificate management (ACM)

Vercel is a managed frontend and serverless platform with a global edge network. Decentralized.Host is a different category: self-hosted infrastructure for long-running processes and containers on your own hosts, with no CDN or build step.

License

Proprietary Cloud Platform

Model

Managed Global Serverless & Edge Network

Multi-server

Global anycast edge routing managed by Vercel

Git deploy

Automatic Git branch preview deployments via GitHub/GitLab

TLS

Instant edge wildcard SSL

AWS offers every building block as a managed service under one provider's control. Decentralized.Host is for running workloads on hardware you (or cooperating operators) own, where no coordinator — including your own control plane — can force a host to run something its policy refuses.

License

Proprietary Cloud Service

Model

Managed multi-tenant cloud; you assemble EC2/ECS/ALB/Route53 yourself, or use Elastic Beanstalk's opinionated wrapper around them

Multi-server

Yes, via ECS clusters, Auto Scaling Groups, or multi-AZ Elastic Beanstalk environments -- powerful, but real infrastructure-as-code work to configure

Git deploy

Not native -- typically wired up via CodePipeline/CodeDeploy or a third-party CI, not a plain `git push`

TLS

ACM (Certificate Manager) issues certs, but wiring them to an ALB/CloudFront is manual setup, not automatic per-deploy

UpCloud sells servers. Decentralized.Host is software you could run on such servers; it does not provision or manage the machines themselves.

License

Proprietary Cloud Service

Model

Managed European IaaS cloud -- you provision Cloud Servers/Kubernetes/databases yourself; there is no app-level "push and deploy" product

Multi-server

Yes, via Managed Kubernetes clusters or manually-networked Cloud Servers -- infrastructure you assemble, not a built-in app scheduler

Git deploy

Not offered -- upctl and the API manage infrastructure (servers, storage, networking), not application source or git pushes

TLS

Not automatic for arbitrary apps -- TLS is your responsibility to configure on whatever you run on their servers/load balancer