CLI overview

No first-party customer CLI; dashboard, SSH/Dokku on Worker Nodes, and Docker Compose for self-hosted control planes.

Written By Zoro

Last updated 3 days ago

dFlow does not ship a separate first-party command-line client (for example a `dflow` binary) for customers to manage Applications, Services, or billing.

Day-to-day control happens in app.dflow.sh (cloud) or your self-hosted dashboard URL.

What operators use instead

Need	Typical approach
Control plane (orgs, apps, deploys)	Web UI; server-side logic uses Server Actions and tRPC (see API overview).
Worker Node operations	SSH to the node; Dokku and host tools where installed (Add a self-hosted server under Worker Nodes and Compute in the sidebar, Dokku integration under Worker Nodes and Compute in the sidebar).
Self-hosted control plane	Docker and Docker Compose per Install with Docker / Docker Compose under Self-Hosting dFlow in the sidebar and Environment configuration under Self-Hosting dFlow in the sidebar.
Logs and debugging	Dashboard Logs and troubleshooting guides (Logs under Deployments and Operations in the sidebar).

Monorepo developer CLIs

Contributors use pnpm scripts (for example pnpm dlx ultracite, app dev servers, and package filters). That tooling is for repository development, not for production customer operations, and it is not part of the hosted product surface.

Learn more

Admin and advanced operations for Compose, backups, and operator workflows.
API overview if you expected an HTTP API instead of a CLI.