Attach compute to an environment

Bind Worker Nodes or managed compute to an Environment during the wizard or from the Compute tab.

Written By Zoro

Last updated 9 days ago

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.

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. For Azure nodes: a connected account and completed provisioning as described in Add an Azure server under Worker Nodes and Compute in the sidebar.

  • 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

  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.

  2. Open the Compute tab.

  3. Follow the in-product flow to attach, change, or unlink compute as offered.

Worker Nodes and managed compute (canonical docs)

Provisioning, onboarding, Azure and AWS steps, and exclusivity rules are maintained in the Worker Nodes and Compute section:

If something fails

  • Compute and worker node issues under Troubleshooting in the sidebar

  • Compute troubleshooting under Worker Nodes and Compute in the sidebar