dFlow Cloud overview
Why use dFlow Cloud, where to sign in, browser requirements, and how it relates to your Worker Nodes.
Written By Zoro
Last updated 26 days ago
dFlow Cloud hosts the dFlow control plane for you. You still attach or purchase Worker Nodes for the environments where Services run; your servers remain yours; dFlow orchestrates deploys and configuration.
Why use the cloud version
Less setup: no Docker Compose stack to run for the dashboard itself.
Updates: control-plane updates are handled by the service (exact cadence is defined by dFlow operations).
Access from anywhere; use a normal browser session to app.dflow.sh.
Secure connection to your nodes: SSH and credentials stay under your control; dFlow drives provisioning through the product flows.
Where to sign in
Open https://app.dflow.sh.
The cloud dashboard runs on that domain. Custom domains for the control plane login are not the default experience; expect to use app.dflow.sh unless your organisation has a documented exception.
Browser and connectivity
Relationship to self-hosting
If you need the control plane inside your network, use Self-hosting overview under Self-Hosting dFlow in the sidebar instead. The Application β Environment β Service model is the same.