Hosting for web design agencies: host client sites profitably

Agency web hosting is profitable when you sell a maintenance or care plan, not bare server space. Hosting a typical client WordPress site on your own VPS costs very little, in our example about $1.44 a month in servers, licences and backup storage, but the time you spend on updates, checks and small requests costs far more. Price per client site from your hours, put each client in its own hosting account, and give clients their own login under your brand so they never need your passwords.

This article is about the business side of hosting your clients' sites: pricing, margins, account structure and client access. If you are choosing between tools, our GridPane alternative compares the software cost of GridPane, SpinupWP and ZoPanel for 30 client sites. If you would rather have someone else run the server, see managed VPS for agencies.

Why agencies host client sites at all

Many agencies start hosting because handing a finished site to the client's cheap shared host went badly: slow pages, no backups, a hacked plugin, and a support call that lands on the agency anyway. Hosting the sites yourself gives you:

• Control over quality. Same stack, same caching and backups for every client.
• Recurring revenue. A monthly fee per client smooths out project income.
• Faster support. You can fix a problem in minutes instead of opening a ticket with someone else's host.

The cost is responsibility. Once you host the site, downtime, email trouble and restores are your problem. Price for that.

What to sell: hosting, care plan or both

Clients rarely compare your hosting to a server price list; they compare it to what they get. Package it so the scope is clear.

Plan	Typical scope	Who it suits
Hosting only	Server, SSL, daily off-site backups, uptime monitoring, security updates of the server	Clients with their own developer, static sites
Care plan	Hosting plus plugin, theme and core updates, monthly check, small content changes up to a time limit	Most small business clients
Priority care	Care plan plus faster response, staging for every change, monthly report	Shops and sites that make money every day

Write the limits down: how many minutes of changes a month, what counts as a new project, what response time you promise, and what happens with work above the limit.

A margin example per client site

Here is a worked example for 40 client WordPress sites on two 4 GB VPS servers, 20 sites each. Two servers mean one problem does not take every client down. Both servers are far below what we measured a 4 GB VPS can carry (how many hosting accounts fit on one server), which leaves room for heavy sites. Unit prices are published prices at the time of writing (October 2026), without VAT; the time, rates and plan prices are assumptions to replace with yours.

Cost line	Calculation	Per month	Per client site
Servers	2 × DigitalOcean Basic 4 GiB, $24 each (pricing)	$48.00	$1.20
Control panel	2 × ZoPanel Pro at $49 a year (pricing)	$8.17	$0.20
Off-site backups	200 GB on Backblaze B2 at $6.95 per TB (pricing)	$1.39	$0.03
Infrastructure		$57.56	$1.44

Now the part that decides the margin, your time:

Plan (example)	Price per site	Time per site per month (assumption)	Time cost at $40/hour	Infrastructure	Margin per site
Hosting only	$15	10 minutes	$6.67	$1.44	$6.89 (46%)
Care plan	$35	30 minutes	$20.00	$1.44	$13.56 (39%)
Priority care	$75	60 minutes	$40.00	$1.44	$33.56 (45%)

Three things stand out:

• Infrastructure is a rounding error. Doubling the server budget would add about $1.20 per site. Choosing a cheaper VPS barely moves the margin.
• Time is everything. If the care plan really takes an hour per site, its margin drops to about −$6.44, a loss. Track your time per client for three months before you fix prices.
• Tooling that saves minutes pays most. Anything that turns a manual update, check or restore into a click improves the margin of every site.

Card fees and taxes are not in the table. At small monthly amounts the fixed card fee matters, so offer yearly billing; what it costs to run a small hosting company shows the effect. If your clients are in Vietnam, collecting by QR bank transfer is covered in selling hosting to Vietnamese customers.

Set up one hosting account per client

The most useful structural decision is to give every client its own hosting account, even if you manage them all.

• Isolation. In ZoPanel each hosting account is its own Linux user with its own PHP-FPM pool and its own CPU, RAM and process limits. A hacked plugin on one client's site cannot read another client's files, and a traffic spike slows only that client.
• Clear usage per client. Disk, traffic and resource use are shown per account, which is useful when a client's site grows into a bigger plan.
• Clean exits. When a client leaves, their account backup contains their sites, databases and mail. It can be restored on any ZoPanel server, or you hand over the files and database dump.

Use packages to match your plans: a small package for brochure sites, a larger one for shops (packages and limits). Staging copies and clones count toward an account's website and database limits, so allow for them.

Client logins under your agency's brand

Clients often want to see something: their traffic, whether the site is up, or their mailboxes. Freelancers need to deploy or update. None of them should get your password.

Website members

ZoPanel's website members give a person their own login to one or more websites of an account, with one of two access levels:

Who	Access	What they can do
Client who wants to look	View only	See status, uptime, analytics and logs; nothing can be changed
Freelancer or client's developer	Manage	SSL, domains, PHP settings, cache purge, WordPress updates and staging, deploys
Neither		File Manager, databases, email, DNS, backups and members of the account stay with the owner

An account can have up to 50 member logins. Members sign in on the normal panel page, can turn on two-factor authentication, and every action they take is recorded under their own name. Removing a member ends their access at once.

If a client should manage their own mailboxes or files, give them the hosting account login itself, and keep your agency's access through the administrator account.

Your brand on the panel

• Your domain. Set the panel to an address such as panel.youragency.com with a trusted certificate (Settings → General → Panel domain & SSL).
• Your welcome email. Edit the text new accounts receive, with the panel address, nameservers and your support link filled in (resellers).
• Your support link. Customers see Contact support pointing to your helpdesk.
• Your panel name. Replacing the ZoPanel name everywhere is white-label, which needs a Business licence not on the public price list; it applies to the whole server.

For the full branding checklist, including nameservers and mail hostnames, see white label hosting panel.

Day-to-day tools that protect the margin

The minutes in the margin table come from routine work. With ZoPanel (WordPress features):

• Safe updates. Updating plugins, themes or core takes a snapshot first, checks that the home page and login still answer, and rolls back automatically if the site broke. It can run every night.
• Staging and publish to live. Clients approve changes on a staging copy; publishing replaces the live site and rolls back if it fails.
• One-click wp-admin login without storing client passwords.
• Page cache that skips logged-in users and carts and purges when content changes.
• Uptime checks every minute and alerts by email, Telegram or webhook; clients can get their own alerts too.
• Backups on the server and encrypted off-site on S3 storage (Pro), with restores of a whole account, a file or a database.

Where ZoPanel is not the obvious choice: if your agency builds on Windows and .NET Framework, or if nobody on your team wants to look after Linux servers at all, a fully managed service suits you better. Hosted dashboards such as SpinupWP also keep working when one of your servers is down, because the dashboard lives elsewhere.

Conclusion

Agency web hosting is profitable when you price per client site from your time, sell a scope clients understand, and keep infrastructure cheap and boring. Put each client in its own hosting account, give clients and freelancers their own logins under your domain, and let safe updates and backups do the routine work. Track your hours for a few months; they decide the margin.

To try this with real client sites, ZoPanel's Free plan runs 3 hosting accounts, 10 websites and 10 databases on one server with no time limit; move to Pro when you pass that or need off-site backups.

Frequently asked questions

Should web design agencies host their clients' websites?

It is often worth it: recurring revenue, control over quality and faster fixes. The trade-off is responsibility for uptime, backups and email. If you take it on, sell it as a care plan with a clear scope, not as cheap hosting.

How much should an agency charge for hosting a client site?

Price from your time, not the server. In our example the infrastructure costs about $1.44 per site a month, while 30 minutes of monthly work at $40 an hour costs $20, so a $35 care plan leaves about $13.56. Track your real time before you set prices.

Should each client get a separate hosting account?

Yes. Separate accounts isolate clients from each other's security problems and traffic spikes, show usage per client, and make it easy to hand a site over when a client leaves.

Can clients log in to see their own website?

Yes. With ZoPanel's website members, a client gets their own login with view-only access to status, uptime, analytics and logs, while a freelancer can get manage access. Neither needs the account owner's password.

Can I put my agency's brand on the hosting panel?

You can serve the panel on your own domain, write your own welcome email and set your support link on any plan. Replacing the ZoPanel name itself is white-label and needs a Business licence.