Documentation

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.

Try StackShiftRead the overview

Search Docs

Nodes

BYOCloud overview

Live

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

Goal

Understand the current BYOCloud workflow, supported providers, and the node-scoped operating model StackShift exposes today.

Current status

Live

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

Workflow

  1. 1Create a provider connection from the Nodes page.
  2. 2Validate the saved credentials before provisioning a cloud node.
  3. 3Provision a node using StackShift tiers and tested provider regions.
  4. 4Operate the resulting cloud node through the same health, maintenance, placement, and workload flows used for other StackShift nodes once bootstrap and registration are complete.

What BYOCloud includes

  • Encrypted provider connections and credential validation
  • Provisioning StackShift nodes in customer-owned Hetzner, DigitalOcean, AWS, and Azure accounts
  • Bootstrap, agent registration, health tracking, retry, reboot, delete, cleanup, and reconciliation
  • Node-scoped cloud resource operations such as volumes, snapshots, placement metadata, and stable public IP actions where supported
  • Provider metadata surfaced through StackShift node concepts instead of provider-native consoles

How the model works

  • Users choose a provider connection, tested region, StackShift tier, and node name instead of assembling raw infrastructure primitives.
  • The node stays the operational boundary for the cloud resources StackShift creates and tracks.
  • Provisioning and resource actions are asynchronous and become visible through node status, bootstrap status, and operation state.
  • Once healthy, a BYOCloud node behaves like a normal schedulable StackShift node for workloads.

Expected result

You understand BYOCloud as a current StackShift node workflow for customer-owned infrastructure, including provisioning and ongoing node operations.

Common failures

  • Provider credentials are invalid
  • Permissions are too narrow for lifecycle operations
  • Selected region or tier is not supported
  • Provider capacity or quota blocks creation