Welcome to dFlow

The Welcome to dFlow page (first item under Introduction in the sidebar) carries the main pitch: what dFlow is, what makes it different, the feature table, and who it is for. This page adds comparison, trade-offs, and boundary cases so you can decide with confidence.

Compared to DIY scripts and snowflake servers

Instead of bespoke deploy scripts per repository, dFlow ties Git, containers, and templates to Services and Deployments you can see in the UI. Operators still decide where compute runs by attaching Worker Nodes to Environments.

Compared to “pure” PaaS

Managed platforms optimize for zero infrastructure touch. dFlow optimizes for visible Environments, Worker Nodes, and Deployments you can trace and inspect. That model applies whether dFlow hosts the control plane (dFlow Cloud) or you self-host it.

One product model for cloud and self-hosted

The same concepts apply either way: Application, Environment, Service, Deployment, and Worker Node. Under Core Concepts in the sidebar, read How dFlow is structured, then Platform architecture for the runtime picture.

Operational visibility

Environments isolate stages (for example production vs staging). Services expose the units you scale, configure, and troubleshoot. Deployments give you a concrete history of what ran when. The Deployments page under Core Concepts spells out the concept.

Data and apps together

Run application workloads and data services (where your plan and architecture allow) so smaller teams do not split context across unrelated tools. Database-focused guides live under Databases in the sidebar.

Organisation boundary

Organisations group members, billing (on cloud), and shared settings. When tenancy matters for your rollout, read Organisations and tenants under Core Concepts in the sidebar.

When dFlow might not be the first choice

• You only need static hosting with no environments or teams; simpler hosts may fit.
• You want a fully managed runtime with no compute decisions; evaluate whether you still want control over Worker Nodes and Environments.

Next steps

• Welcome to dFlow for overview, differentiators, and first actions.
• Choose your path to start onboarding.
• What you can do with dFlow for a capability tour.