dFlowvsDokploy

COMPARE · DOKPLOY

dFlow vs Dokploy

Dokploy is an open-source, self-hostable PaaS built on Docker and Traefik. Its CLI and MCP server cover the whole Dokploy API. dFlow runs on Kubernetes, from a CLI or a coding agent, with typed confirmations on destructive tools.

Rival facts checked Nov 19, 2026. Sources at the end.

your app todayone command eachdFlow on Kubernetes
01

Who should pick which

Pick dFlow if

  • You want Kubernetes underneath, without running the control plane.
  • You want a small set of agent tools with typed confirmation on deletes and restores.
  • You want releases kept for you, without setting up a registry for rollbacks.

Pick Dokploy if

  • You want to self-host the whole platform, open source.
  • You are happy with Docker Swarm and Traefik on your own servers.
  • You want every API endpoint as a CLI command or MCP tool.
02

Side by side

FeaturedFlow beta, Nov 2026Dokploy
Where apps runKubernetes. Our shared cluster, or yoursDocker and Traefik, with Docker Swarm, on your Dokploy server or remote servers 12
Deploy fromA GitHub repo (apps:build --repo) or an image (apps:deploy --image)Applications and databases from the Dokploy UI or API 1
CLIThe dflow CLI@dokploy/cli, with 449 commands generated from the API spec 3
Agent accessHosted MCP at k8s.dflow.sh/mcp, plus 4 skills@dokploy/mcp, with 508 tools across 49 categories 4
Guardrails for agent actionsDestructive tools need a typed argument, such as confirm_name or confirm_hostNot described in the MCP README we read 4
Rollbackdflow apps:rollback APP --release IDAutomatic Docker Swarm rollback on failed health checks, or a manual rollback to any image saved in your registry 5
PostgresPostgres 16, 17 or 18. On-demand backups and restorePostgres, plus MySQL and other databases 6
Cron and jobsdflow jobs:scheduleSchedule Jobs 7
Your own servers or clusterRegister your own Kubernetes cluster from the CLIYes. Remote deployment servers and build servers 2
Self-host the platformNo. dFlow stays hosted. dflow-server cluster:create installs k3s or kubeadm on a machine an operator already has. It does not publish a self-hosted control plane.Yes. Open source 1
StatusInvite-only beta. No SLA. Pricing not setGenerally available
03

What is the same

Both have a CLI and an MCP server, deploy apps and Postgres, roll back, and let you bring your own machines.

04

Move from Dokploy to dFlow

  1. Request beta access and install the CLI.
  2. Deploy the image from your registry with dflow apps:deploy APP --image IMAGE.
  3. Create a Postgres database and link it to the app.
  4. Copy your data with standard Postgres tools. Get the connection details with dflow db:credentials.
  5. Set your env vars and secrets.
  6. Set the route, check the logs, then point your DNS to dFlow.
05

Sources

  1. 1Dokploy Docs: Welcome to Dokploydocs.dokploy.com/docs/core
  2. 2Dokploy Docs: Remote Serversdocs.dokploy.com/docs/core/remote-servers
  3. 3GitHub: Dokploy/cli READMEgithub.com/Dokploy/cli
  4. 4GitHub: Dokploy/mcp READMEgithub.com/Dokploy/mcp
  5. 5Dokploy Docs: Rollbacksdocs.dokploy.com/docs/core/applications/rollbacks
  6. 6Dokploy Docs: Databasesdocs.dokploy.com/docs/core/databases
  7. 7Dokploy Docs: Schedule Jobsdocs.dokploy.com/docs/core/schedule-jobs

Logo: Dokploy repository (apps/dokploy/public/icon.svg). All trademarks belong to their owners.

06

More comparisons

Get a beta invite.

The beta is invite only. Tell us what you deploy and which agent you use. We reply by email.

Join the beta

Open to the first 100 users.

Book a design-partner call

Invite only. Read the beta terms.