Working at Scale
SSH: How One Person Runs Forty Client Accounts
Your client list has grown to the point where doing anything twice by hand is a whole morning.
Straight answer first
SSH is the encrypted protocol that lets you drive a server from a text prompt, and for a reseller it is the difference between clicking through forty client accounts one at a time and running a command that handles the lot.
A migration search-and-replace, a bulk plugin update, a log inspection across several sites: all of these are a morning in a panel and a few minutes at a prompt.
It is also where the question of what to give clients gets interesting, because shell access is genuinely useful and genuinely a thing you may not want in every customer's hands.
Written by the Hosting Seller staff · Checked 4 August 2026
100+
Terms defined for resellers
2 min
Time to read one entry
Plain
English, from WHM to invoice
24/7
Cover for you and for them
The threshold is real and most resellers hit it somewhere between fifteen and forty accounts. Below it, the panel is fine and the command line is an affectation. Above it, the panel is the reason your evenings disappear and every repeated task is worth learning to script.
The protocol carries more than shells, which is what makes it worth the learning. SFTP runs on top of it, Git pushes travel through it, and port forwarding reaches services that are otherwise fenced off. One credential system covers the lot.
The job that takes an afternoon in the panel
Fixing every stale URL in a freshly migrated client database is a single WP-CLI search-replace at the prompt. The same job clicked through phpMyAdmin eats an hour, invites a typo into a live table, and has to be repeated per site.
Multiply that by a client list and the arithmetic makes itself. Any task you will do more than three times is a task worth doing at a prompt the first time.
What actually breaks at forty accounts
Not the platform — your process. Panel-driven work scales linearly with the client list, so the day arrives when routine maintenance takes longer than the maintenance is worth to you. That is the moment margin quietly disappears without a single price changing.
Fixing it is unglamorous: a handful of scripts, a note of which accounts are which, and the discipline to do repeated work at the prompt rather than by memory and mouse.
Whether to give clients a shell of their own
A developer client will expect it and use it well. A non-technical client has no use for it and gains only a new way to break something you will then be asked to fix. It is reasonable to make shell access a feature of your higher package rather than a default on every account.
When you do grant it, the fence holds: a client's shell sees their own files, their own databases and their own processes, and nothing belonging to anybody else on your plan. That is worth saying explicitly, because it is the first question a security-conscious client will ask.
Where it is available, and what to read next
Shell access, along with Git and Composer, sits on the plans built for developers, with keys managed from the account's own panel rather than through a ticket.
Worth reading next: SFTP, Git, Cron Job and VPS.
SSH, Git and Composer sit on the plans built for developers, and you decide which of your packages carry them.
Jargon costs you an hour a week
This is the reseller desk's own vocabulary list. It exists because explaining the same eight words to every new client is unpaid work, and a link is quicker than a paragraph.
Step up a tier whenever the client list demands it — every account you have already built comes along untouched.
- Plain English, from WHM down to the invoice
- Every entry ends on how it behaves at scale
- Where a setting can leak your supplier
- Safe to forward straight to a customer
Why Hosting Seller
On every plan, as standard
Judged at forty accounts
Each term is tested against a long client list as well as a short one, because that is where reseller decisions actually bite.
Costed per account
Every entry says what the term does to your resource pool and your ticket queue, not merely what the word means.
Written from the WHM side
Definitions from the reseller's panel rather than the end customer's: packages, limits, suspensions and handover.
What the client actually sees
Each definition names the screen, the email or the error a customer meets, so you can answer before they open a ticket.
Entries that point onwards
Related terms cross-link, so one lookup turns into a working grasp of the whole account stack rather than a single answer.
SSH, in one read
SSH defined, judged at forty accounts and priced into your packages — the tool that keeps the list profitable.
First Steps
From choosing to live
- 1
Script anything you have done three times
The third repetition is the signal. Everything after it is margin you are handing back to the client list for free.
- 2
Decide which package carries a shell
Developer clients will want it and use it. Make it a reason to be on your higher tier rather than a default nobody thought about.
- 3
Read the neighbours
SFTP, Git and Cron Job finish this one's picture, each a two-minute read from here.
In the Box
Packed with every plan
- Client accounts moved in by our staff, at no charge
- Webmail plus IMAP, POP and SMTP on every mailbox in every account
- A domain free for year one when the order is annual
- Softaculous in every account you open, for one-click installs
- Real people on the desk at any hour, for you and for your clients
- Every client account copied daily, with restores you run yourself
- Seven days' money back on reseller, thirty on hosting plans
- DDoS filtering handled out at the network edge, before it reaches you
- NVMe SSD under the whole platform, LiteSpeed cache in front
- SSH, Git and Composer on the plans built for developers
Across the Counter
Things people ask us all the time
Should I give clients shell access or keep it to myself?
Keep it off the entry package and offer it where it earns its place. A developer client uses it properly and would otherwise ask you to run every command for them. A non-technical client gains a new way to create work for you. Making it a feature of a higher tier turns the decision into a pricing question rather than a judgement call each time.
Can a client's shell session see my other accounts?
No. Each cPanel account you create is fenced into its own environment, so a client's shell sees their own files, their own databases and their own processes and nothing else on the plan. That isolation is what makes it safe to offer at all, and it is the sentence to have ready when a security-minded customer asks.
What actually gets faster once I have forty accounts?
Repeated work. Bulk updates, search-and-replace after migrations, log inspection, dumping databases on a schedule. None of it is impossible in a panel; all of it scales with your client count in a way that a command does not. The saving is your time, which on a reseller list is the input that decides your margin.
Do I need shell access to run WP-CLI on a client's site?
Yes, that is the door it comes through, which is why it sits on the plans built for developers alongside Git and Composer. If you are managing WordPress sites for clients at any volume, WP-CLI is the tool that turns per-site maintenance into one command per task, and shell access is the prerequisite for having it at all.
Read next
OpenCart Hosting
OpenCart in one click, on PHP set up for storefronts, with free SSL and staging.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and daily backups.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Run the client list, not the mouse.
WHM for you, a cPanel for every customer, and the developer kit on the plans that need it.
See OpenCart Hosting plans