Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

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

​
Prerequisites

  • A provider account with the required permissions
  • Dashboard access to the Nodes page

​
Workflow

1
Add a provider connection in the BYOCloud panel.
2
Validate the connection using the saved provider configuration.
3
Choose the provider connection, region, StackShift tier, and node name.
4
Wait 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.
  • Provisioning creates a BYOCloud node record, starts an async provisioning operation, bootstraps the machine, installs the agent, and waits for heartbeat before the node becomes schedulable.

​
Expected result

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

BYOCloud overview

Connect customer-owned cloud accounts to StackShift, provision cloud-backed nodes, and operate them through the same node workflows used elsewhere in the product.

BYOCloud cloud resources

Manage provider-backed node resources such as volumes, snapshots, placement metadata, stable public IPs, refresh, retry, reboot, and delete actions from the node detail surface.

Maintenance mode

Use maintenance as a safety control before upgrades or disruptive host changes.