Where Can My DPanel Instances Run?

DPanel is the control plane

The deployment selector should never imply that DPanel owns the customer cloud or is the compute host. The product manages the AI-team control plane, approvals, usage, and handoff around the selected runtime target.

The trust line is: managed by DPanel · billed by <host> · runs on your infrastructure.

Deployment target choices

Local / my PC means a self-hosted Docker install. The button should say Prepare Local Docker Install.

Connect existing remote instance means the user brings an already running host and connects it with API/token setup. The button should say Connect Existing Instance.

Cloud / provider covers AWS, GCP, Oracle, Hetzner, Fly, and Railway. Mark these routes Coming later unless they are actually built. Buttons should be specific, such as Deploy To My AWS Account.

Partner host is also Coming later unless a partner route is live. The button should say Deploy With Partner Host.

Billing and ownership copy

Each target should say who owns the infrastructure, who bills for compute, and what DPanel manages.

Good copy pattern: managed by DPanel · billed by AWS/GCP/Oracle/Hetzner/Fly/Railway/partner/local infrastructure · runs on your infrastructure.