API, CLI, and Admin Reference
CLI overview
No first-party dFlow customer CLI today: use the dashboard, SSH on Worker Nodes, and MCP for agents.
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.
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 (Worker Nodes and Compute). |
| AI agents | dFlow for Agents and dFlow MCP. |
| Logs and debugging | Dashboard Logs and troubleshooting guides. |
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.