Engineering Brief
Hosting with SSH access — A shell is only useful if the toolchain and the limits are real
Plenty of hosts advertise SSH and then hand you a jailed prompt with no Git, no Composer and a process ceiling that kills a database import halfway through.
The short answer
Buy shared hosting where SSH is enabled at signup and the toolchain is already installed — on Turbo at $4.66 a month you get a shell with Git, Composer and the standard utilities on it, without a support request or a waiting period.
Judge the shell in your first ten minutes with four commands: `git --version`, `composer --version`, `php -v`, and a `mysqldump` of a real database. If any of those fails, or the dump gets killed partway, the SSH tick on the feature grid was decorative.
The rest of this page is what to test, what the limits mean, how key-based authentication works here, and where a shared shell genuinely stops and a VPS begins.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target
24/7
Humans on the desk
Free
SSL, every plan
NVMe
Storage as standard
SSH changes the class of work you can do. With it, a deployment is `git pull`, a bulk content change is one WP-CLI command, and diagnosing an error means tailing a log while you reproduce the fault. Without it you are dragging files and guessing.
But the tick on the comparison table is not the feature. The feature is the toolchain, the process limits and the file access that come with it — and those are what this page tells you how to verify before you pay for anything.
The ten-minute shell test
Connect, then run the version checks: `php -v`, `git --version`, `composer --version`, `mysql --version`. A host that means it will answer all four. A host that does not will give you a shell with almost nothing on the path.
Next, test the limits rather than reading about them. `mysqldump -u user -p dbname > dump.sql` on your largest database, and a `tar -czf` of the whole home directory. Both are long-running, single-process jobs — exactly the shape that gets killed on hosts with an aggressive process ceiling.
Finally, check file access is genuinely yours: `ls -la ~` should show your document root, your logs and your mail directory. Accounts here are jailed to their own environment, so you see your files and your processes and nothing belonging to anybody else.
Keys, not passwords
Generate a key with `ssh-keygen -t ed25519`, upload the public half through the panel's SSH access screen, and connect with `ssh -i ~/.ssh/id_ed25519 user@yourdomain.example`. Key-based authentication is supported, and it is the only sensible way to run a deploy script.
The same credentials carry SFTP, so any editor or file client that speaks SFTP works without a second account. That is one credential to rotate rather than two, and no plaintext FTP.
If you script deployments, put the key on the machine doing the deploying and nowhere else. A key in a repository is a credential in a repository.
What the shell is actually for
Deployment: `git pull` in the document root, or an rsync from a build directory. Both are reversible in a way that a drag-and-drop upload never is.
Bulk operations: WP-CLI turns a search-and-replace across 4,000 posts into one command, and `wp plugin update --all --dry-run` tells you what an update would touch before it touches it.
Diagnosis: `tail -f ~/logs/yourdomain.example.error.log` while you reproduce the bug in a browser is worth more than any amount of guessing from a plugin's status page.
Measurement, which is the one people forget: `curl -s -o /dev/null -w '%{time_starttransfer}'` from the server against itself separates application time from network time, and timing a single WP-CLI eval tells you whether the database is the slow part.
Where the shared shell ends
A shared account gives you your own environment, not the machine. You cannot install system packages, bind a port, or run a long-lived daemon. For PHP work, Composer projects and WordPress at any reasonable scale, none of that matters.
It starts to matter when you need a queue worker running permanently, a runtime that is not PHP, or root to install something. Business hosting on Overdrive at $19.99 a month adds native Node.js, Python and Ruby on Rails plus PostgreSQL alongside MySQL; a 1 Core VPS at $13.52 or 2 Core at $20.28 gives you full root on KVM with a choice of 24 Linux and BSD images and a London or Dallas location.
Turbo at $4.66 covers the middle ground well: 25 sites, 20 GB of NVMe, 1 TB of bandwidth, 1 core and 2 GB of RAM, 50 MySQL databases, and the renewal charged at the same $4.66. Upgrades between shared tiers are account changes with no migration.
Why we bother printing the commands
A page that tells you how to test us is a page that has to be right. That is the trade we are making: we recommend our own plan, and in exchange we give you the exact checks that would expose us if the shell were decorative.
The desk is staffed at every hour, and shell questions are in scope — key setup, a stuck cron, a dump that will not import. A two-hour first-reply target, one hour when a site is down.
- Four version checks that settle it in a minute
- ed25519 keys supported, SFTP on the same credential
- Process limits you can test, not just read about
- $4.66 at order is $4.66 at renewal
Why HostingFast
Standard on every plan
Enabled at signup
The shell is on the account when it provisions. No form, no ticket, no two-day wait for a human to flip a flag.
Toolchain already installed
Git, Composer and the standard utilities are on the path, so the first thing you run is your code rather than a support request.
Keys and SFTP on one credential
ed25519 key authentication for scripted deploys, and SFTP through the same login for whatever editor you use.
Room for long-running jobs
A full mysqldump or a tar of the home directory finishes rather than being cut off partway through.
Per-site PHP from the panel
Switch the branch for one site without touching the others, then confirm it from the shell with `php -v`.
A clean step up when you need root
Overdrive at $19.99 for native Node, Python and Ruby, or a KVM VPS from $13.52 with full root and 24 images.
Prices Side by Side
Our numbers next to the big names
Typical intro and renewal pricing across the market, lined up against ours — including the renewal figure most comparison charts skip.
| Feature | HostingFastMost popular | Typical household-name host | Typical bargain host | Typical loss-leader deal |
|---|---|---|---|---|
| Starting price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Renewal price / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Cheapest plan renews at its sign-up price | ||||
| SSL as standard | ||||
| Migration done for you | ||||
| NVMe drives on the cheapest tier | ||||
| Daily backups from the first tier | ||||
| Real humans on support, 24/7 |
*Our number is the lowest-priced plan we sell on an annual term, pulled live from the same catalogue that powers our pricing page — it physically cannot fall out of date. The other three columns show the ranges shared hosts in each bracket typically advertise: introductory offers that mostly demand a one-to-four-year commitment, then jump once it expires. We no longer name rivals or print their prices, because a figure we cannot verify on the day you read it has no business on this page. Line us up against whichever host you are really weighing — and give the renewal row the hardest look.
Quick Start
From order to online
- 1
Run the four version checks
php, git, composer, mysql. Sixty seconds, and it separates a real shell from a tick on a feature grid.
- 2
Push a long job through it
A full mysqldump and a tar of the home directory. If either dies partway, the process limits are the actual product you are buying.
- 3
Set up key authentication straight away
`ssh-keygen -t ed25519`, upload the public key in the panel, and stop typing passwords into deploy scripts.
- 4
Time something before and after
Run a curl timing loop from the server against itself, change one thing, run it again. That is the whole method.
Built In
Loaded onto every plan
- The renewal invoice shows the same figure as the first one
- Full SSH access with Git and Composer already installed
- Key-based authentication, with SFTP on the same credentials
- Your existing site moved across by our engineers, free of charge
- 99.9% uptime monitored continuously rather than sampled occasionally
- WebP image conversion built in at no extra cost
- Webmail plus IMAP, POP and SMTP for any mail client
- In-place upgrades between tiers, with no migration to arrange
- Softaculous: WordPress and 240+ applications in one click
- Volumetric traffic scrubbed at the network edge before the machine sees it
- Inbound mail screened for spam and malware on every account
Frequently Asked
What people ask us most often
How do I tell a real shell from a decorative one before I pay?
Ask pre-sales to confirm four things: that SSH is enabled at provisioning rather than on request, that git and composer are on the path, that key-based authentication is supported, and what happens to a long single-process job like a full mysqldump. A host that answers all four precisely is telling you the feature is real.
Will a big mysqldump or tar get killed partway through?
It should not, and that is the specific thing worth testing in your first week. Dump your largest database and tar the whole home directory; if both complete, the process and memory limits are sized for real work rather than for a demonstration.
Can I use SSH keys instead of a password?
Yes. Generate an ed25519 key locally, upload the public half through the SSH access screen in the panel, and connect with `ssh -i`. The same credentials also carry SFTP, so your editor connects without a second account and nothing travels in plaintext.
What can I not do from a shared shell?
Install system packages, bind a port, or keep a daemon running — the account is jailed to its own environment. For PHP, Composer and WP-CLI work that is no constraint at all. When you need more, Overdrive at $19.99 adds native Node.js, Python and Ruby, and a KVM VPS from $13.52 gives you full root.
Keep reading
Web App Hosting
When an application needs a runtime rather than a document root, and what that changes about the plan you buy.
Bots and Automation Hosting
Long-lived processes and scheduled work: where a shared shell is enough and where it stops being enough.
How to Connect to a VPS with SSH
Key generation, the first connection and hardening the login, written for the step up to root access.
Web Hosting
Sprint, Turbo and Nitro with the cores, memory and storage printed, and a shell on every one of them.
Domain Names
Registration and DNS for the hostnames your deploy scripts will be pointing at.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
A prompt, not a promise.
Turbo at $4.66 a month: SSH with Git and Composer from the first login, on NVMe behind LiteSpeed.
View Web Hosting plans