dFlow Cloud practices

These practices assume you use dFlow Cloud at app.dflow.sh with the Application → Environment → Service model. For running the control plane yourself, start with Self-hosting overview under Self-Hosting dFlow in the sidebar; many runtime habits below still apply to Worker Nodes.

Organisation and access

• Treat one Organisation per real-world company or billing entity; avoid sharing owner credentials.
• Use Invites and team members under Security and Team Management in the sidebar so collaborators have least privilege.
• Align Application names with products or systems so Environments (production, staging) stay obvious.

Compute and environments

• Attach Worker Nodes per Environment, not “per app at random,” so blast radius and scaling stay clear. See Environments under Core Concepts in the sidebar and Attach compute to an environment under Environments in the sidebar.
• Prefer managed compute only where it meets compliance and region needs; otherwise run your own nodes and keep them patched. See Choose compute / managed infrastructure.
• Keep SSH keys under Security and Team Management in the sidebar rotated and remove retired nodes from dFlow so deploys never target dead hosts.

Git and build hygiene

• Connect Git with minimal repository access; reinstall or narrow scopes when repositories move.
• Pin branches or use protected flows for production Services; avoid pointing production at personal experiment branches.
• Read Connect your Git provider and Integrations overview under Integrations in the sidebar when onboarding new teams.

Configuration and secrets

• Store secrets in dFlow environment variables or your approved secret store; do not commit them to Git.
• Document Service-level vars next to the Service; keep Environment defaults for shared values; see Environment variables under Deployments and Operations in the sidebar for task-level detail.

Legacy Projects

• Put new work in Applications, not new legacy Projects, unless you are blocked by a migration dependency.
• Use Migrate from legacy Projects to Applications under Migration and Release Notes in the sidebar when your team is ready so Git and compute line up with the current model. Legacy Projects vs Applications under Core Concepts in the sidebar explains the mapping.

Day-to-day operations

• Watch Deployments and Logs after changes: Logs under Deployments and Operations in the sidebar.
• Follow Quick start for dFlow Cloud under Getting Started in the sidebar when onboarding someone new; it matches how the UI wants the steps ordered.

Related

• dFlow Cloud overview
• Create your cloud workspace
• Cloud limits and expectations
• Payment setup
• Troubleshooting overview