Compute and Environments

Compute is attached to an Environment, not to individual Services. Every Service in that Environment runs on the selected Worker Node or managed capacity. You typically attach compute when you create the Environment or later from the Environment Compute tab.

Placement model: Environments under Core Concepts in the sidebar and Worker Nodes under Core Concepts in the sidebar.

Prerequisites

• A Worker Node that is onboarded and reachable (for self-hosted nodes: SSH, Dokku, and checks described in Add a self-hosted server under Worker Nodes and Compute in the sidebar), or managed compute available on your plan.
• SSH keys under Security and Team Management in the sidebar and network paths configured so the control plane can reach your nodes when you use self-hosted Workers.

Path A: During Add Environment

Use this when you are in Create an environment.

1. Complete the Environment step so the Environment exists.
2. On the Compute step, select an available Worker Node or managed option.
3. Finish Activation.

Expected outcome: The Environments list shows Compute as the node name or Managed (when applicable), and you can deploy Services.

Path B: From an existing Environment

1. Open the Application → Environments tab → click the Environment row (or open View Details from the row menu).
2. Open the Compute tab.
3. Follow the in-product flow to attach, change, or unlink compute as offered. The UI may warn if a node is already used by another Environment or if services must move.

Expected outcome: Compute on the Environment matches the node or managed pool you selected; health or reachability checks reflect the current state.

Worker Nodes and managed compute (canonical docs)

Provisioning, onboarding, AWS-specific steps, and exclusivity rules are maintained in the Worker Nodes and Compute section so they stay in one place:

• Worker Nodes overview under Worker Nodes and Compute in the sidebar: mental model and entry points.
• Add a self-hosted server under Worker Nodes and Compute in the sidebar: Linux host, SSH, Dokku.
• Managed compute under Worker Nodes and Compute in the sidebar: dFlow-managed capacity (as this page is expanded).
• Attach a server to an environment under Worker Nodes and Compute in the sidebar: complementary task framing from the compute side.
• Choose compute / managed infrastructure under dFlow Cloud in the sidebar: dFlow Cloud decision guide.

Expected outcome: You add or fix Worker Nodes in the right section, then return here or to the dashboard to attach them to the correct Environment.

Validate before deploying Services

• The Environment lists healthy, intended compute (not N/A unless the product explicitly allows a pending state you understand).
• Create an environment and Draft vs active environments: the Environment is active when you expect production-style deploys.

If something fails

• Compute and worker node issues under Troubleshooting in the sidebar
• Compute troubleshooting under Worker Nodes and Compute in the sidebar (as expanded)

Related

Environment best practices