Knowledge base

Getting file and shell access to a site

SFTP and SSH details, where the keys live, and why the credentials are per site.

Every site has its own file access. Sites → your site → Access.

SFTP

The host, port, username and a password you generate on that screen. Any SFTP client works — FileZilla, Cyberduck, your editor's built-in one. The account is confined to that one site's files, so an SFTP credential for one site cannot read another.

SSH

Add your public key on the same screen and connect with your usual client. Password SSH is deliberately not offered: a key cannot be guessed, and a shared server with password SSH is a shared server that will eventually be brute-forced.

If you do not have a key yet, ssh-keygen -t ed25519 on your own machine creates one. The file ending .pub is the one you paste in; the other one never leaves your computer.

What you get in the shell

Your site's files, wp-cli on WordPress sites, composer, and the PHP version the site is set to. You are inside the site's own isolated environment — you cannot see another customer's files, and neither can they see yours.

Why credentials are per site rather than per account

Because access is the thing most often shared with a contractor, and one credential per site means you can give somebody exactly the site they are working on. Revoking it later affects nothing else.

⭐ For a person rather than a machine, add them to your team instead (Organisation → Team) — they then sign in as themselves, their access is logged under their own name, and removing them removes everything at once.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →