Skip to main content
HostingSeller
Shop plans

Trade Terms

When a VPS Beats Buying More Client Accounts

Somewhere on your client list, renting more accounts stops being cheaper than running a box you administer yourself.

Straight answer first

A VPS is a virtual machine carved out of a physical server, with reserved processor, memory and disk, and full root access. For a reseller it marks the point where the job changes: you stop buying accounts and start operating infrastructure, patching and all.

Treat it as a make-or-buy decision rather than an upgrade. A node buys control, isolation and the ability to run software no shared platform will allow. It bills you back in administration hours, and those hours come out of the same margin the accounts were funding.

Written by the Hosting Seller staff · Checked 4 August 2026

0

Terms we duck

100+

Entries, cross-linked

Real

Kit, not diagrams

Free

To read, no signup

A hypervisor, KVM on our racks, splits one powerful machine into several separate servers. Each gets its own operating system, its own reserved slice of memory and processor, and complete administrative control from the command line upwards.

Our VPS plans are self-managed by default. The virtualisation platform, the hardware and the network are watched around the clock at our end, while the operating system, the firewall rules and everything installed on top of them belong to you.

The moment the sums flip

A reseller plan bills a flat base and a small charge for each active client account, so the cost follows the revenue. A node bills the same monthly figure whatever you do with it. The crossover is not really about account counts; it is about whether a client needs something the shared platform cannot give anybody.

If your usage graphs sit flat and low and nobody is asking for root, the reseller plan was already the right answer and a node is a hobby with a standing order attached. If one client needs a queue worker, a specific runtime or a written line about tenancy, the box earns its keep on that client alone.

What you take on the day it boots

Patching, firewall rules, backups, mail deliverability, monitoring, and the certificate renewals that used to happen without you. None of it is hard, all of it is regular, and a node bought to avoid learning is a node quietly running an unpatched kernel a year later.

Add a control panel if you want the routine work automated, and remember the panel licence is a real line in your cost per client rather than a rounding error. cPanel can be added at the counter when your clients expect the interface they already know.

What the client should never notice

Nothing about the move should reach them. Same domain, same mailboxes, same panel login if you have kept the panel consistent. If a client can tell that you changed infrastructure, something leaked: a nameserver, a certificate hostname, or a mail server banner nobody thought to check.

Plan the cutover around DNS rather than around the copy. Shorten record lifetimes a day ahead, move the data while the old account still answers, then flip delegation. Mail is the part that strands people, so move mailboxes with the site rather than a fortnight afterwards.

The migration nobody else will run for you

Moving client accounts onto a node of your own is your project. Budget an evening per handful of accounts, keep the old accounts alive until the new ones are answering properly, and tell clients nothing until there is nothing left to tell them.

Sizing is the easy part to change later. Stepping up a tier keeps your data, your operating system and your configuration exactly as they are and swaps only the processor, memory and storage behind them, so buy for the client list you have rather than the one you are hoping for.

Cloud servers wired together to run VPS infrastructure

Make-or-buy, written down

Half the entries in this file exist to stop a reseller buying infrastructure they do not need. The other half exist to stop the same reseller buying it a year too late.

Backups run daily on every plan, and putting a file or a database back takes one click from the panel rather than a ticket and a wait.

  • Make-or-buy framed as cost per client
  • The administration you inherit, listed out
  • Cutover and DNS traps flagged in advance
  • Panel licensing counted as a real cost

Why Hosting Seller

On every plan, as standard

The crossover, not the hype

Where a node genuinely beats more accounts, judged on client requirements rather than on how serious it feels to own one.

Administration priced in

The recurring hours a self-managed box adds, counted against the same margin your client accounts were funding.

Root, and what it unlocks

The specific client requests only root can answer, so you know which enquiry actually justifies the purchase.

A cutover clients never notice

Record lifetimes, the order mail must move in, and the checks to finish before you tell anybody anything.

Sizing you can change later

Stepping up keeps the data, the operating system and the configuration and changes only what sits behind them.

Where we stop and you start

Hardware, network and virtualisation are watched at our end; the operating system upwards belongs to you.

First Steps

From choosing to live

  1. 1

    Write the requirement down first

    Name the client and the thing shared hosting cannot do for them. If you cannot name both, you are buying a feeling rather than a server.

  2. 2

    Cost the administration honestly

    Patching, monitoring, backups and any panel licence, per month, in hours as well as money, before the box is ordered.

  3. 3

    Rehearse the cutover on your own site

    Move something you own before you move something you invoice for, and time each step so the client-facing window is a number rather than a guess.

In the Box

Packed with every plan

  • Root access, with nothing fenced off
  • KVM virtualisation, so the memory on the invoice is genuinely yours
  • 24 Linux and BSD builds on the shelf
  • A counter in London or Dallas, whichever suits the client base
  • 1 Tbps+ DDoS filtering sitting in front
  • 20 Gbps uplink on every hypervisor
  • cPanel available at the counter if your clients expect it
  • Snapshot backups, yours to switch on
  • Reboot, rebuild and console access from the panel
  • Setup is free, and real people answer round the clock

Across the Counter

Things people ask us all the time

Should I move client accounts onto a VPS to improve margin?

That is rarely the reason that works. A reseller charge follows your revenue, whereas a node bills the same whether you have four clients or forty, so any saving only appears at a density you may not have reached. Move for capability instead: root, a runtime, a tenancy requirement. Then check afterwards whether a saving turned up as well.

Who patches the server once it is mine?

You do. Our plans are self-managed by default: the hypervisor, the hardware and the network are ours and watched around the clock, and everything from the operating system upwards is yours. A control panel automates most of the routine work, but the responsibility does not transfer along with the automation.

How do I keep a node migration invisible to clients?

Shorten record lifetimes a day ahead, copy files and databases while the old account still answers, move mailboxes with the site rather than after it, then switch delegation and watch both ends. Say nothing to the client until the new box has served them for a day without producing a ticket.

Is KVM worth insisting on for client workloads?

Yes, because it is what makes the numbers on your invoice mean something. KVM virtualises the hardware, so the memory is genuinely reserved and you boot your own kernel. Container platforms share the host's kernel and often quote burstable figures that cannot be guaranteed to a client who asks you to guarantee them.

Read next

  • Best VPS for Developers

    The tiers developers ask for by name, with root, the runtimes and console access spelled out.

  • WordPress Hosting

    Managed WordPress you can resell without inheriting the update rota yourself.

  • Laravel Hosting

    PHP versions, Composer and queue workers arranged the way a Laravel build expects to find them.

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.

One email brings the checklist, then now and again a note about running a site properly. Leave the list whenever you feel like it. Our privacy policy spells out the rest.

Rent the box, keep the margin.

KVM virtualisation, full root, DDoS filtering in front and nothing to pay at setup. Add cPanel at the counter if your clients expect it.

See WordPress Hosting plans