Connection methods
One saved computer can have several routes. The identity belongs to the machine and development account, not a URL or IP address.
Direct SSH and VPN
devbox connection add home --ssh my-box
devbox connection add home --ssh my-box-vpn --route vpn
devbox connection list --jsonVerify both aliases independently through OpenSSH. The CLI checks machine ID, username, UID, home and the actual negotiated Ed25519 host key. A mismatch fails instead of falling through to another machine.
Use an existing VPN/Tailscale SSH alias if that is how you reach the host. Devbox does not install or administer your VPN.
Hosted relay
Signed enrollment saves a direct route and a hosted relay route. The host initiates the relay connection outbound. Your laptop still authenticates to SSH; the relay transports encrypted bytes rather than receiving SSH private keys or vendor bearer tokens.
The control plane authorizes an expiring grant for the exact computer. A saturated relay returns a typed rejection rather than accepting unbounded sessions. Dashboard enrollment requires an operator-signed release channel.
Self-hosted relay
Use a separately deployed relay when you want to own that transport too. Connector and client credentials are separate, and every route must resolve to the same verified machine/account.
devbox connection add home --relay https://relay.example.com \
--remote-computer computer_home --route private-relay \
--credential-file /private/client-token --allow-private-fileThis is an operator configuration example; the URL and token file must come from your relay operator. First relay-only trust also needs an independently verified machine ID and SSH host key. Adding an arbitrary URL is not a trust bootstrap.
Route selection
Direct routes are preferred, then configured relay routes in order. --route selects one explicitly. A changed host key or account stops the operation. Commands and terminal input are not automatically replayed after ambiguous failure.
devbox connection remove home --route vpnRemoving one route leaves the others intact. Multiple routes improve reachability; they do not make the host's disk, power or OS redundant.