Every machine gets a unique public IPv4 address. SSH directly into it:
You land in a shell as the boxd user (the SSH username is ignored for authentication — only your public key matters).
How it works
When you SSH to a machine’s public IP, the boxd proxy:
- Reads your SSH public key
- Verifies you own the machine at that IP
- Opens a session to the machine on your behalf
All standard SSH features work through the proxy:
- SCP — copy files to/from the machine
- Port forwarding — tunnel ports through SSH
- VS Code Remote SSH — develop remotely
- rsync — sync files over SSH
When to use direct SSH
| Method | Best for |
|---|
HTTPS (name.boxd.sh) | Serving web traffic |
Control plane (ssh boxd.sh exec ...) | Automation, running commands remotely |
Direct SSH (ssh root@ip) | Interactive development, file transfer, port forwarding |
Finding your machine’s IP
name status ip image
myapp running 5.135.42.17 default
With JSON output:
Direct SSH only works for the machine owner. Your SSH key must match the key registered to the account that created the machine.