Nodes
BYOCloud overview
LiveUse customer-owned cloud accounts as StackShift node hosts without turning the product into a generic cloud console.
Goal
Understand what BYOCloud includes today, which providers are supported, and how the product boundary stays node-led.
Current status
Live
This area is documented as current, user-reliable behavior.
Workflow
- 1Create a provider connection from the Nodes page.
- 2Validate the saved credentials before provisioning a cloud node.
- 3Provision a node using StackShift tiers and tested provider regions.
- 4Treat the resulting cloud node like any other schedulable StackShift node once bootstrap and registration are complete.
What BYOCloud covers
- Encrypted provider connections and credential validation
- Provisioning StackShift nodes in customer-owned Hetzner, DigitalOcean, and AWS accounts
- Provider-aware cleanup, reconciliation, reboot, and health tracking
- Compact provider metadata shown through StackShift concepts
What it intentionally avoids
- Arbitrary raw machine catalog browsing
- Full network builders or generic cloud-account administration
- Terraform-style infrastructure orchestration
- A broad provider console for unrelated customer resources
Expected result
You understand BYOCloud as a StackShift node workflow instead of a raw provider-management feature.
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