SSH, SFTP, Git, and browser shell

Use only account-authorized access

The Toolkit exposes developer-oriented tools, including a browser-shell experience in gated contexts. Availability and authorization are account-specific. This documentation does not publish hostnames, SSH usernames, ports, key locations, or public connection endpoints; obtain connection details from your account’s approved support channel.

SFTP and SSH

Use SFTP for file transfer and SSH only when your service explicitly provides it. Keep private keys private, protect them with a passphrase, and never paste them into tickets, browser forms, or Git repositories. Do not assume shell access is enabled for every plan or site.

Git workflow

Keep application code in version control and exclude environment secrets, uploads containing personal data, database dumps, and credentials. Validate changes in a non-production environment when available. A Git push is not evidence that a deployment or production update occurred.

Browser shell

A browser shell is a privileged, gated capability. Treat commands as running with the authority granted to the signed-in session. Inspect commands before execution; avoid destructive recursive operations and never print environment secrets into logs or support conversations. If shell access is unavailable, ask support rather than trying private routes.