Dokploy: Self-Hosted PaaS with Applications, Compose, Remote Servers, and Swarm

🌏 中文版

Dokploy is a self-hosted Docker and Traefik platform for Git deployments, domains, TLS, logs, monitoring, databases, backups, and previews. First decide whether a workload is a single Application, multi-service Docker Compose, or a Swarm Stack.

Application and Compose are different abstractions

An Application maps to one service or container with provider, build, replica, resource, volume, and domain settings. Compose preserves multi-container topology. UI variables are written to .env but enter containers only through explicit env_file or environment configuration.

Dokploy can inject Traefik labels into Compose, but domain changes require redeployment. Preview the final model and verify that database ports are not host-published, services do not join unintended shared networks, and secrets are not exposed in readable configuration.

A remote server is not a cluster

Deployment options are distinct. The single Dokploy Server is simplest. SSH-managed Remote Servers each run independent Docker and Traefik and do not form a cluster. Swarm Nodes share scheduling and load balancing. Use remotes for regional or customer isolation and Swarm only for cross-machine replicas.

A dedicated build server can build Applications, push a registry, and let deployment servers pull; Compose builds currently do not use it. The registry becomes a supply-chain and availability dependency. Pin images, scope push credentials, retain artifacts, and test registry outages.

Volume backup is not whole-system recovery

Compose storage supports bind mounts and named volumes, while Dokploy's volume backup supports only named volumes. A Swarm scheduler does not move local data with a container. Use database-native consistency tools, off-site storage, and restoration drills.

Previews execute pull-request code on your servers. The official docs warn against enabling them on public repositories. Isolate credentials, resources, and networks; deny Docker sockets and production access; limit counts and clean up after merges.

Dokploy fits Docker teams favoring Compose, independent VPS fleets, or gradual Swarm adoption. Coolify's resource control plane, CapRover's simplified Swarm, and Kubernetes orchestration have different complexity. Test UI-host failure, SSH loss, Traefik reload, registry outage, malicious preview builds, and volume restoration.

References

• Dokploy documentation
• Dokploy applications
• Dokploy Docker Compose
• Dokploy deployment options
• Dokploy remote servers
• Dokploy preview deployments