Manage access and secrets

Control SSH access

Use your own passphrase-protected key. Keep the private key on your own device and install only the matching public key for the correct guest user. Confirm a second session can log in before removing a credential or changing SSH settings.

ssh-keygen -t ed25519
ssh -i ~/.ssh/id_ed25519 <user>@<vm-host>

The second command assumes the public key is installed for that user. If the generator warns that a key already exists, choose a new filename or use the existing key. Replace <user> and <vm-host> with your VM details.

Scope application credentials

Run the worker as a dedicated user. Prefer narrow provider credentials, rotate them when access changes and keep them out of source control, project archives, unit files and logs. If the application needs a secret file, place it outside the repo and make it readable only by the required service user or root. Prefer your runtime’s credential mechanism over secrets in arguments or shell history.

Hostodo handles the infrastructure, account and billing. You control guest accounts, patches, backups, provider credentials and application access.