Last updated: September 25, 2026
Is It a Self-Hosted PaaS?
Partly. It runs and routes your applications on hardware you control, but it is an infrastructure layer, not a developer platform: there is no build pipeline, and it is not production-validated.
| PaaS expectation | Here | How / notes |
|---|---|---|
| Deploy an app to machines you own | Yes | dh apply -f app.yaml; hosts admit under their own policy |
| Build from source / git push | No | bring an executable (dh artifact push) or a digest-pinned image |
| Framework detection, buildpacks | No | — |
| Rolling updates | Yes | within maxUnavailable; make-before-break for stateless replicas |
| Rollback | Yes | re-apply the previous manifest (a new generation with old content) |
| HTTPS routing | Limited | edge hosts with ACME; tested against Pebble only |
| Persistent volumes | Yes | replicated, snapshot commits at quorum 2; no erasure coding |
| Logs and exec | Yes | over the mesh; exec only where host policy allows it |
| Managed databases, templates | No | — |
| Autoscaling | No | dh scale app |
| Web dashboard | Yes | operator console served by the cluster |
| Multi-server | Limited | many hosts, but validated on one machine only so far |
If you want a polished self-hosted PaaS today, see alternatives. Decentralized.Host is for when the hosts themselves must be able to refuse the coordinator, and every transition must be signed and verifiable.