Selling managed VPS to agencies: offer, pricing and tooling

Managed VPS for agencies means you give each agency its own virtual server and take care of everything below their websites: the operating system, the control panel, security updates, backups, monitoring and help when something breaks. Agencies want it because a dedicated server avoids noisy neighbours and gives them room to grow, but they do not want to be on call for Linux. Price it from your real costs, mostly your own time, and use tooling that lets you run many servers from one place.

This article is for hosting companies and freelance sysadmins who want to add a managed VPS plan for web agencies. If you are the agency yourself, see hosting for web design agencies instead. If you want to sell shared space to agencies on your own server, the reseller hosting guide covers that model.

Why agencies buy managed VPS

An agency with a few dozen client sites has usually outgrown shared hosting. The common reasons:

• Isolation from other customers. A dedicated VPS means another host's customer cannot slow their clients down.
• Control over the stack. PHP versions, cron jobs, Node.js or Python apps, staging copies.
• One bill and one place. All client sites on one server they can explain to their clients.
• No server work. The people at an agency are designers, developers and account managers. Nobody wants to apply kernel updates at night.

That last point is what you sell. The VPS itself is a commodity they could buy in minutes from DigitalOcean or Hetzner. What they cannot buy in minutes is someone who keeps it patched, backed up and answering.

What the offer should include

Define the plan by what you do, not by RAM and CPU. A clear offer looks like this:

Included	What it means in practice
Server provisioning	You choose and size the VPS, install the OS and the panel
OS and security updates	Automatic security updates, reboots after kernel updates in an agreed window
Control panel updates	Applied by you, with a rollback if an update fails
Off-site backups	Daily, encrypted, stored with a different provider, with a stated retention
Restore on request	A number of restores per month included, then billed
Monitoring and alerts	Server and website uptime, disk, memory, certificates, blocklists
Security	Firewall, WAF, malware scanning, two-factor sign-in, panel IP allowlist
Migrations	Moving existing client sites in, with a limit on how many are included
Support	Channel, hours and response time in writing

What is not included matters as much. Say it in the contract: plugin and theme updates (unless you sell that too), website development, content, client email support, and fixing code the agency wrote.

Who is responsible for what

Most disputes in managed hosting come from an unclear line between the host and the customer. Write it down before the first server.

Area	You (the host)	The agency
VPS, network, provider account	Responsible	Informed
Operating system and kernel	Responsible	Informed of maintenance windows
Control panel and its updates	Responsible	Informed
Backups and restore tests	Responsible	Asks for restores
Server security (firewall, WAF, 2FA policy)	Responsible	Follows the policy
WordPress core, plugins, themes	Optional add-on	Responsible by default
Client accounts, packages, client logins	Sets the limits	Responsible
Website code and content	No	Responsible
Client communication	No	Responsible

Operating system lifecycle

Part of what you sell is planning the next OS upgrade before it is urgent. Ubuntu LTS releases get 5 years of standard security maintenance; 22.04 ends in May 2027 and 24.04 in May 2029 (Ubuntu release cycle). Debian's security team supports a stable release for three years (Debian security FAQ), and Debian LTS extends that to at least five; Debian 12's LTS ends on 30 June 2028 (Debian LTS). Put the end date of each agency's OS in your records and plan the move a year ahead.

Pricing managed VPS for agencies

Price cost-plus: what the server costs you, plus licences and storage, plus your time, plus margin. Here is an example for one agency server. The unit prices are published prices at the time of writing (October 2026), without VAT; the hours and rate are assumptions.

Line	Example	Monthly cost
VPS	DigitalOcean Basic, 8 GiB, 4 vCPU, 160 GiB (pricing)	$48.00
Control panel	ZoPanel Pro, $49 a year per server (pricing)	$4.08
Off-site backups	500 GB on Backblaze B2 at $6.95 per TB (pricing)	$3.48
Your time	2 hours a month at $50 (assumption): updates, checks, small requests	$100.00
Cost		$155.56

At a 30% margin on price, that server sells for about $222 a month. A cheaper VPS lowers the first line; for example, Hetzner lists a CPX32 with 4 vCPU and 8 GB in its EU locations at €35.99 a month (Hetzner). The VPS is not the line to optimise, though. Two hours a month is a guess: track your real time per server for three months and correct it, because one demanding agency can take five times that.

Pricing tips that protect your time:

• Tier by support, not by RAM. Offer a basic plan with business-hours support and a priority plan with faster response, both on whatever server size fits.
• Count migrations separately. Moving 40 client sites in is a project, not a monthly task. Quote it once.
• Include a fixed number of restores, then charge per restore. It keeps backups valuable without making them unlimited work.
• Pass server upgrades through at cost plus margin, written into the contract.

How agencies use the server

Giving an agency root access defeats the point of managed hosting: you cannot be responsible for a server someone else changes. A better split with a control panel:

• You keep the administrator login and root.
• The agency gets a reseller account on its server, with a package that sets the total disk, websites and resources it can hand out. It creates its own packages and one hosting account per client, so each client site is isolated from the others.
• Client staff or freelancers get member logins to single websites, with manage or view-only access.

In ZoPanel, a reseller cannot create a package larger than its own plan, and suspending the reseller suspends its customers (resellers). Reseller accounts need a Pro licence. The agency can also connect its own WHMCS, Blesta, HostBill or Paymenter with an API token limited to its own packages.

Tooling: running many agency servers

One agency server is easy. Ten is where tooling decides whether you sleep. What you need:

Need	What to look for
One view of every server	Status, CPU, RAM, disk, site count per server
Safe sign-in	One-click sign-in that keeps a per-person audit trail, with 2FA
Alerts that reach you	Email, chat or webhook, deduplicated
Self-healing	Services restarted automatically, with limits
Updates with rollback	Panel updates that roll back on failure; OS security updates on
Backups you can prove	Off-site, encrypted, restore-tested
Moving sites	Move a site to a bigger server without rebuilding it
Rebuild a server	Restore the whole configuration onto a new VPS

With ZoPanel

ZoPanel's fleet connects servers into one view. Each agency's server is a node, enrolled with a token its own administrator generates, and your panel is the controller:

• Status of every node: online, CPU, RAM, disk, websites, accounts, uptime and agent status; a node that fails three checks in a row is reported down.
• One-click sign-in to a node through a one-time link. On the node you appear as a dedicated administrator named after your own login, so two technicians never share an account and the node's activity log names who acted. Your 2FA on the controller protects every node.
• Monitoring-only tokens for dashboards that should not change anything.
• Move websites to another server with their databases, users and passwords, for example when an agency outgrows its VPS. Databases keep their names, so wp-config.php needs no changes.

On each server, a watchdog restarts stopped services (at most three times an hour, then it alerts you), alerts go out by email, Telegram or webhook, and zopanel ctl doctor explains what is broken (operations). Panel updates are signed and roll back automatically if they fail, and the installer turns on unattended security updates for the OS. Backups go to S3-compatible storage, encrypted, and a daily configuration backup lets you rebuild a server on a new VPS.

Where ZoPanel is weaker for this model: the fleet documentation describes status, sign-in, account creation and moves, not bulk changes across nodes, so settings such as automatic panel updates (installed at 04:00 server time once turned on, updating) are set on each server. White-labelling the panel name needs a Business licence that is not on the public price list, and it applies to the whole server. Email from billing or an outside status page are separate tools. If you will run many agency servers, ZoPanel's partner programme gives volume pricing from 10 licences and an API to issue a licence per server.

Alternatives worth knowing

You are competing with services an agency can buy directly. Hosted dashboards such as SpinupWP and RunCloud manage a VPS the agency rents itself, and GridPane PeakFreq and Cloudways sell managed servers outright, Cloudways with an agency partner programme. Our GridPane alternative and RunCloud alternative articles price several of them. Your edge over them is a named person who answers, in the agency's language and time zone, and who handles migrations and odd requests. If you cannot offer that, an agency is better served by one of those services.

Conclusion

Selling managed VPS for agencies is selling your time and judgement, wrapped around a commodity server. Write down what is included and who is responsible for what, price it from your real hours, and use tooling that gives you one view, safe sign-in and reliable backups across every server. Keep the agency in a reseller account on its server so you stay responsible for what you manage.

To build the first agency server, install ZoPanel on a VPS and start on the Free plan (3 hosting accounts, 10 websites, 10 databases, no time limit); reseller accounts and off-site backups need Pro.

Frequently asked questions

What is managed VPS hosting?

A virtual server where the provider looks after the operating system, control panel, security updates, backups and monitoring, while the customer runs their own websites on it. It sits between shared hosting, where you control little, and an unmanaged VPS, where everything is on you.

How much should I charge for managed VPS?

Start from your costs: the VPS, licences, backup storage and, above all, your hours per server each month. Add your margin. In our example, a server costing $155.56 a month including two hours of work sells for about $222 at a 30% margin.

Should agencies get root access on a managed VPS?

Usually not. If the agency can change anything as root, you cannot be responsible for the result. Give them a reseller account in the control panel instead, and keep root for yourself. Agencies that need root are better served by an unmanaged VPS.

How many client sites can an agency put on one VPS?

It depends on the sites. In our measurements, a 4 GB VPS ran 100 WordPress sites without page cache and 250 with it. Agencies with shops or heavy page builders should plan for far fewer; see how many hosting accounts fit on one server.

What happens when an agency outgrows its server?

Resize the VPS if the provider allows it, or move the sites to a larger server. With ZoPanel's fleet you can move websites with their databases and passwords to another server and then switch DNS.