Documentation

Connect a BYOCloud node

Save provider credentials, choose a tested region and StackShift tier, and wait for the provisioned cloud node to become healthy and schedulable.

Nodes

Connect a BYOCloud node

Live

Save provider credentials, choose a tested region and StackShift tier, and wait for the provisioned cloud node to become healthy and schedulable.

Goal

Walk from saved provider credentials to a healthy BYOCloud node in the Nodes page.

Current status

Live

This area is documented as current, user-reliable behavior.

Workflow

  1. 1Add a provider connection in the BYOCloud panel.
  2. 2Validate the connection using the saved provider configuration.
  3. 3Choose the provider connection, region, StackShift tier, and node name.
  4. 4Wait for bootstrap, agent registration, and a fresh heartbeat before placing workloads on the node.

Provider setup expectations

  • Hetzner uses a project-scoped API token.
  • DigitalOcean uses a scoped personal access token.
  • AWS uses access key ID, secret access key, optional session token, and a default region.

Provisioning model

  • StackShift tiers stay starter, growth, and pro instead of exposing raw provider SKUs.
  • Regions are limited to StackShift-tested provider locations.
  • The node is not schedulable until the agent is registered and a healthy or degraded heartbeat exists.

Expected result

A BYOCloud node is provisioned and ready to host projects, stacks, or database flows once healthy.