| Where apps run | Kubernetes. Our shared cluster, or yours | Docker on servers you connect over SSH 1 |
|---|
| Deploy from | A GitHub repo (apps:build --repo) or an image (apps:deploy --image) | A Git repo, a Dockerfile, a Docker Compose file or a prebuilt image 1 |
|---|
| CLI | The dflow CLI | The coolify CLI for the Coolify API 2 |
|---|
| Agent access | Hosted MCP at k8s.dflow.sh/mcp, plus 4 skills | An MCP server at /mcp over Streamable HTTP, with a Bearer token. Off by default on self-hosted 3 |
|---|
| Guardrails for agent actions | Destructive tools need a typed argument, such as confirm_name or confirm_host | Token scopes. delete is separate from write, and MCP hides tools the token can't use 3 |
|---|
| Rollback | dflow apps:rollback APP --release ID | Rollback is a deploy operation; the token needs deploy 3 |
|---|
| Postgres | Postgres 16, 17 or 18. On-demand backups and restore | Supported databases, with persistent storage and backup configuration 1 |
|---|
| Cron and jobs | dflow jobs:schedule | Scheduled tasks with cron expressions 4 |
|---|
| Your own servers or cluster | Register your own Kubernetes cluster from the CLI | Yes. Any server you connect over SSH 1 |
|---|
| Self-host the platform | No. 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, or Coolify Cloud as a managed control plane 1 |
|---|
| Status | Invite-only beta. No SLA. Pricing not set | Generally available |
|---|