SSH and SFTP

Keys belong to people, not sites

Add your SSH public key once, under Account → SSH keys, and it works for every site you have access to — there’s no per-site key to manage. If you’re removed from a site’s team, your access disappears everywhere at once, instantly.

Connecting

sftp -P 2222 <site-handle>@ssh.example.com
ssh -p 2222 <site-handle>@ssh.example.com

The site handle is shown on the site’s SSH page, along with the exact hostname to use (your provider’s SFTP/SSH hostname — the same for every site, one address for the whole platform). Port 2222 is used instead of the standard port 22, which is reserved for your provider’s own server administration.

A sample ~/.ssh/config entry, so you can just run ssh mysite:

Host mysite
    HostName ssh.example.com
    Port 2222
    User mysite-handle
    IdentityFile ~/.ssh/id_ed25519

What you get

SFTP works on every plan.
Shell access (ssh, interactive or exec) is available on plans that include it — check your plan’s features if you don’t see it.
Your session lands directly in the site’s home directory, sandboxed from every other site on the server: you cannot see, and cannot affect, anyone else’s files or processes.
Database tunnels: ssh -L 3306:localhost:3306 mysite (or your SSH client’s tunnel option) opens a secure tunnel to the site’s own database, so tools like TablePlus or DBeaver can connect without the database ever being exposed on the public internet. See Databases.

File manager and web terminal

Prefer a browser? The site’s Files page gives you a full file manager with an editor, and the Terminal page gives you a shell in the browser — the same sandboxed session SSH gives you, no client needed.

Every session is logged

Who connected, with which key, to which site, from where, and for how long is recorded — visible to your provider’s operators, and useful if you ever need to know who touched what.