Escalation Path
VPS hosting for developers — The client who has outgrown your reseller plan
The day you move a client onto their own server, you stop being their host and start being their sysadmin — and only one of those two jobs is in your current price.
Straight answer first
Move a client to a VPS only when their workload genuinely cannot live inside a shared package, and reprice before you do — an unmanaged KVM server from $13.52/mo transfers the machine to you, not just the cost, and the management is the part your current retainer does not cover.
Below: the four signals that a client has actually outgrown shared resources rather than merely having a slow week, what unmanaged means in practice for an agency, how to structure the billing so you are not doing sysadmin work for a brochure-site fee, and what to hand over if the relationship ends.
Written by the Hosting Seller staff · Checked 24 August 2026
Free
Migration on the way in
24/7
Cover behind your escalations
Daily
Backups on hosting accounts
$0
Setup on every VPS
Most clients who ask for a server do not need one. A busy shared account with proper caching behaves better than a badly maintained small VPS, and the honest advice is usually to step up a shelf rather than change category. The exceptions are real, though, and recognising them early is worth more than any technical detail on this page.
The VPS shelves: 1 Core Unmanaged VPS at $13.52/mo with 1 GB of RAM and 25 GB of SSD; 2 Core at $20.28/mo with 2 GB and 50 GB; 4 Core at $33.81/mo with 4 GB and 75 GB; 6 Core at $67.63/mo with 8 GB and 100 GB; 8 Core at $108.22/mo with 16 GB and 200 GB. All KVM, all with full root, DDoS filtering in front and a choice of London or Dallas.
Four signals that it is genuinely time
The client needs software you cannot install in a shared package. A specific PHP extension, a queue worker, a long-running process, a service listening on its own port. This is the cleanest signal and the least arguable — no amount of tuning gets around it.
Their resource use is sustained rather than spiky. A shared allocation absorbs bursts comfortably; it is a constant floor that causes trouble. If a client's site is at the ceiling all day rather than for an hour at lunchtime, they are no longer a shared-hosting customer.
Their compliance position requires it. Some clients need to say, in writing, that no other tenant shares their environment. Whether or not you think that is technically meaningful, it is a real commercial requirement and a VPS satisfies it.
They need root for their own developer. If the client's in-house or contracted developer needs SSH with root, you are not going to fake it. Note that this signal also means the machine will be changed by somebody who is not you, which changes the support conversation entirely and should change the price.
What unmanaged means when you are the agency
It means the operating system is yours. Root access with nothing fenced off, KVM virtualisation underneath, 24 Linux and BSD builds available, reboot, rebuild and console from the panel — and every patch, every firewall rule, every certificate renewal and every backup decision now belongs to somebody on your side of the table.
The specific things that stop being automatic are worth listing, because they are the ones agencies forget: security updates, cPanel if the client wants a panel (it is available to add at the counter), free SSL that previously issued itself, daily backups that previously ran without asking, and Imunify360 that was previously watching. Snapshot backups are yours to switch on, and the emphasis is on yours.
There is also a refund difference that matters to your cash flow rather than your client's: VPS and dedicated servers are provisioned to order the moment payment clears, so they sit outside the money-back window that covers shared, business, WordPress and WooCommerce hosting. Do not sell a client a trial on a VPS that you cannot honour.
Billing it so you are not working for nothing
Separate the two lines explicitly on the invoice: the server, and the management of the server. The server is a pass-through with your margin on it — $13.52, $20.28, $33.81 and up, billed monthly with free setup. The management is a new product and it should be visibly more expensive than the shared-hosting retainer the client is used to, because it is a fundamentally different amount of work.
Define what management includes: patching cadence, backup schedule and retention, monitoring, and a response target. Define what it excludes: the client's own application code, anything their developer changes, and any third-party service on the box. Without that second list you will spend a Sunday debugging somebody else's deployment for free.
The 20 Gbps uplink and 1 Tbps+ DDoS filtering in front of every hypervisor are worth mentioning to the client once, at the point of sale, and then never again. They are the reason you can say yes to a nervous merchant without qualifying it, not a feature to be listed monthly.
The handover you will eventually make
A managed VPS relationship ends the same way every other one does, and it is harder to unwind than a cPanel account because there is no standard export. Decide at the start what the client receives: root credentials, a documented list of what is installed and why, the backup location, and any DNS you control.
Write the build down as you go. A short document naming the distribution, the stack, the cron entries, the firewall rules and the certificate mechanism takes an hour to maintain across a year and turns a painful handover into an email. It also protects you when the client's own developer changes something and asks you what it used to be.
Choose the location deliberately at the start, because moving later is a migration rather than a setting: London or Dallas, picked on where the client's visitors actually are. For a UK audience, London puts round-trip times in the 5–15 ms band; for a US audience, the East Coast sits at 70–90 ms from London and the West Coast at 130–150 ms, which is a real difference for uncached, logged-in work.
Two categories, one supplier
The client who needs a server and the twenty clients who do not can sit with the same supplier, which keeps your billing, your escalation route and your support relationships in one place rather than three.
Moving up is a change to your account rather than a hunt for a new host, and free migration covers bringing an existing site in, so the escalation is a scheduled job rather than a project.
- Full root on KVM, nothing fenced off
- London or Dallas, chosen at order time
- 1 Tbps+ DDoS filtering in front
- Free setup, billed monthly
Why Hosting Seller
On every plan, as standard
A real escalation route
Shared, reseller, VPS and dedicated all under one supplier, so a growing client never forces you to open a second relationship.
Root with nothing fenced off
KVM virtualisation and full root mean the client's developer gets what they asked for and you get a machine you can document.
Free setup on every VPS
Nothing to pay before provisioning, which makes staging a build and testing the migration cheap to plan.
Location chosen at order time
London or Dallas, picked on where the client's visitors are rather than discovered afterwards as a latency complaint.
DDoS filtering in front
1 Tbps+ filtering and a 20 Gbps uplink on every hypervisor, so saying yes to a nervous client needs no qualification.
cPanel available at the counter
Add a panel if the client wants one, or keep the box bare if their developer would rather have it that way.
First Steps
From choosing to live
- 1
Test the four signals before you agree
Software they cannot install, sustained rather than spiky load, a compliance requirement, or a developer who needs root — anything else is a shelf upgrade.
- 2
Reprice before you provision
Two lines on the invoice: the server, and the management of the server. The second must visibly exceed the shared retainer or you are working for nothing.
- 3
Write the build document on day one
Distribution, stack, cron, firewall and certificate mechanism — an hour a year to maintain, and the whole of your eventual handover.
- 4
Choose the location for the audience
London sits at 5–15 ms for UK visitors and 70–90 ms for the US East Coast; pick once, because changing it later is a migration.
In the Box
Packed with every plan
- A written test for when a client genuinely needs a server
- Separate invoice lines for the server and its management
- A management scope naming what is excluded, not just included
- Patching cadence agreed and diarised
- Snapshot backups switched on and their restore tested
- A firewall rule set documented rather than remembered
- Certificate renewal mechanism chosen and verified
- Location picked on the client's actual audience
- A build document kept current as things change
- Handover contents agreed at the start of the relationship
Across the Counter
Things people ask us all the time
How do I tell a client they do not need the server they asked for?
With their own numbers. Show what their account actually consumes against its allocation, and what caching would do to the part that is dynamic. Most requests for a server come from a bad fortnight rather than a sustained ceiling, and stepping up a shared shelf — Pro at $4.66/mo, Elite at $7.08/mo — costs a fraction of a managed VPS. Offer the upgrade first; you will look like an adviser rather than an upseller and you keep an easy account easy.
What should I charge for managing a client's VPS?
Visibly more than the shared retainer, and priced on response rather than resources. The server itself is a pass-through — $13.52/mo for 1 core, $20.28 for 2, $33.81 for 4 — and the margin on that line is small. The management line has to carry patching, monitoring, backups and the fact that you are now the person who gets called when something on that machine stops. Agencies that price the two together almost always underprice the second.
Who patches the operating system on an unmanaged VPS?
You do, or the client's developer does, and it must be decided in writing before the machine goes live. Unmanaged means exactly what it says: root access with nothing fenced off, and nothing done for you. This is the single item that most often gets assumed by both sides and performed by neither, which is how a client's server ends up two years behind on security updates while everyone believed it was covered.
Is there a trial period on a VPS?
No. VPS and dedicated servers are provisioned to order the moment payment clears, so they sit outside the money-back window that covers shared, business, WordPress and WooCommerce hosting — where it is 30 days — and reseller hosting, where it is 7. Never promise a client a trial you cannot honour; if they want to try before committing, stage the build on a shared account first.
What happens to the client's mail when their site moves to a VPS?
Decide deliberately, because this is where a migration strands email. An unmanaged box has no mail stack until somebody builds one, so the usual answer is to leave the mail where it is: point the A record at the new server and leave the MX records untouched. Standalone Email Hosting at $2.99/mo is the tidy home for mail that used to live on a hosting account whose website has moved on.
Read next
Drupal Hosting Plans
The Composer-era client build, and what its deployment step means for a machine you are responsible for.
VPS Hosting
KVM servers with full root and DDoS filtering, for the client who has genuinely outgrown a shared allotment.
SSL Certificates
Free certificates on every client site, with wildcard and EV for the two cases a free one cannot cover.
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.
Escalate without changing supplier.
KVM servers from $13.52/mo with free setup, full root and DDoS filtering — alongside the reseller plan carrying the rest of your book.
See VPS Hosting plans