Why it is built this way
Keys, not passwords
Store public keys in your account and attach them at deploy time.
Reset root safely
Set a new password from the dashboard; it is shown once and never emailed.
Rescue mode
Boot a recovery system with your disk attached, and repair what stops the machine booting.
Four steps, no ticket
Add your public keys
Once, in your account. They are offered on every deploy.
Deploy with keys attached
The server boots with password login already disabled if you want.
Boot into rescue when stuck
Mount the disk, fix the config that locked you out, and restart.
Rotate when people leave
Remove a key and redeploy or update in place.
Straight answers before you deploy
Our firewall runs in front of the machine, not on it, so the rule is removed from the dashboard and you are back in. Nothing has to be typed on the server.
Boot it into rescue mode from the dashboard. It starts a recovery system with your disk attached, so you can repair the configuration and restart.
Yes. Deploy with SSH keys and turn password authentication off in the same step.
Ready when you are.
Configure a server now. Your account is created right before payment, with the configuration saved.