Hosting math changes completely somewhere around client site number ten. The single-site plans every review quotes stop mattering, and the only number that matters becomes true per-site cost — what one client site actually costs you each month at 10, 25, and 50 sites. Most roundups never show that number. This guide is built around it.
I run sites on every host reviewed here, and I’ve done the tier-by-tier math so you don’t have to. Below you’ll find the per-site cost table, four hosts ranked for agency work, a white-label reality check, and the part no competitor roundup touches — which of these platforms let you automate client maintenance with AI agents instead of grinding through Monday update runs by hand.
In this guide
Quick verdict
- Best overall for most agencies: WP Engine — dev/stage/prod environments on every single site and the cleanest client handoff workflow I’ve used.
- Best margins: Cloudways — the per-server model drives per-site cost into single digits faster than anything else on this list.
- Best for automation-heavy shops: Kinsta — the cleanest API of the four, which matters more every month as agent-driven maintenance becomes normal.
- Best for heavy client sites: Liquid Web — VPS and dedicated muscle when a client’s WooCommerce store or LMS outgrows shared-anything.
If you’re managing fewer than ten sites, honestly, start with our best managed WordPress hosting guide instead — the agency math below doesn’t kick in yet at that scale.
The per-site math at 10, 25, and 50 sites
These four hosts price in three different ways, and that’s why comparing sticker prices tells you nothing. Kinsta and WP Engine sell per-site plans that get cheaper per site as you climb tiers. Cloudways sells you a server — the sites on it are your business. Liquid Web sells you a whole box, VPS or dedicated, and how many sites you stack on it is between you and your resource graphs.
Here’s what that works out to for a portfolio of typical client sites — brochure sites, small lead-gen builds, light WooCommerce. All figures are approximate and at the time of writing; heavy stores change the math.
| ~10 sites | ~25 sites | ~50 sites | Pricing model | |
|---|---|---|---|---|
| Cloudways | ~$5–7/site | ~$4–6/site | ~$4–5/site | Per server (DO, Vultr, AWS, GCP) |
| WP Engine | ~$8–10/site | ~$7–9/site | ~$6–8/site | Per-site plans, ~$20–25/mo entry |
| Kinsta | ~$10–15/site | ~$9–12/site | ~$8–10/site | Per-site plans, ~$30–35/mo entry |
| Liquid Web | ~$6–8/site | ~$3–5/site | ~$2–4/site | Per VPS or dedicated box |
Two things jump out. First, Liquid Web is the cheapest per site at 50 — but only because you’re absorbing the sysadmin work yourself. Second, Kinsta never wins on price. You buy Kinsta for the platform and the API, not the margin. Both facts matter later in this guide.
The four hosts, ranked for agency work
1. WP Engine — the client-workflow pick
WP Engine earns the top slot for one reason: every site gets a real dev/stage/prod pipeline, not a bolted-on “staging” checkbox. When you’re pushing updates across 25 client sites, that workflow is the difference between a calm Monday and an apology email. EverCache handles caching well enough that I rarely think about it, Smart Search AI covers the sites that need decent on-site search, and transferable installs make client handoffs painless — build on your account, flip billing to the client when they graduate. Entry pricing sits around ~$20–25/mo for a single site, with multi-site plans pulling per-site cost down into the $6–8 range at scale.
2. Cloudways — the margin pick
Cloudways is managed cloud hosting on servers you choose — DigitalOcean, Vultr, AWS, or Google Cloud — and you pay for the server, not the site. A mid-size server at ~$50–80/mo will comfortably carry a dozen light client sites, which is how the per-site number lands around $5 so quickly. The Copilot AI assistant flags server issues before your clients do, and the stack is flexible enough to host the odd Laravel or plain-PHP project a client drags in. The trade-off is that you’re doing capacity planning: when a server fills up, moving sites around is your job. I’ve broken down where that trade-off bites in Cloudways vs WP Engine.
3. Kinsta — the automation pick
Kinsta runs on Google Cloud C2 machines behind Cloudflare’s enterprise layer, and day to day it’s the host I think about least — sites just stay fast. But the agency case for Kinsta is the API. Site provisioning, backups, cache clears, plugin visibility — it’s all scriptable, cleanly documented, and agent-friendly. If your shop is heading toward automated maintenance (and it should be), Kinsta is the platform that fights you least. You pay for it: entry runs ~$30–35/mo and the per-site cost stays the highest here even on agency tiers.
4. Liquid Web — the heavy-workload pick
Liquid Web is where I put client sites that stopped being polite — WooCommerce stores doing real volume, membership sites, LMS builds with logged-in traffic that laughs at page caching. A dedicated VPS gives you headroom the per-site platforms can’t, and if you consolidate 40–50 light sites onto one big box the per-site cost drops to a couple of dollars. The catch: you own more of the stack. Under ~20 light sites, it’s overkill.
White-label, billing, and who owns the account
White label WordPress hosting gets marketed hard, but agencies really need three specific things: the client never sees the host’s brand, billing passes through you, and you keep account ownership. Cloudways is quietly the strongest here — clients never touch the panel, so the infrastructure is invisible and the markup is yours. WP Engine’s transferable installs solve the opposite problem: graceful exits, when a client wants to own their own hosting. Kinsta sits in between with solid per-site client access controls.
My standing advice after two decades of this: hold the hosting account yourself and bill clients a flat monthly rate. The margin funds your maintenance time, and account ownership means you’re never locked out of your own work. The exception is enterprise clients with procurement rules — let them own it, and bill for management instead.
Honest downsides
- Kinsta and WP Engine don’t host email. Neither one, at all. Every client onboarding needs a Google Workspace or Microsoft 365 step, and you’ll explain this to confused clients forever.
- Visit-based billing can spike. Kinsta and WP Engine both meter visits. One client post going semi-viral can push you into overages you didn’t quote for.
- Cloudways staging is manual-ish. It exists, but it’s not the one-click dev/stage/prod pipeline WP Engine ships. On 30+ sites you’ll feel it.
- WP Engine never gets truly cheap. The workflow is worth it for most shops, but if you’re competing on price against $15/mo “hosting included” freelancers, the math is tight.
- Liquid Web assumes competence. Their support is genuinely good, but a VPS still expects you to notice a full disk before it becomes a client call.
Automating client maintenance with AI agents
Here’s the part that separates a 2026 hosting decision from a 2020 one. Maintenance is the biggest recurring cost in agency hosting — updates, backups checks, uptime triage — and it’s now automatable with AI agents driving host APIs. A weekly run looks like this: an agent pulls your site list, clones each to staging, applies plugin and core updates, diffs the front end, promotes clean results, and flags the two sites that actually need a human. That turns a half-day of clicking into a review of one short report.
Kinsta is the standout — I’ve documented exactly how in automating Kinsta with Claude and its API. Cloudways exposes solid server-level automation plus Copilot, and WP Engine’s environment model gives agents safe places to work. If this angle is new to you, start with our AI web hosting pillar guide — agency ops is where this stuff pays for itself first.
Frequently asked questions
What is the best WordPress hosting for agencies?
For most agencies, WP Engine — the dev/stage/prod workflow and client handoff tools fit agency operations better than anything else. If margin is the priority, Cloudways’ per-server pricing wins; if automation is, Kinsta’s API does.
How much should an agency charge clients for hosting?
Typical agency retail is $50–150/mo per site against a true cost of roughly $4–15. That’s not gouging — the spread covers updates, backups, monitoring, and being the person who answers when something breaks at 9pm.
What is white label WordPress hosting?
Hosting you resell under your own brand — the client sees your name and your invoice, never the underlying host. Cloudways is the most naturally white-label of the hosts here because clients never interact with the platform at all.
Should each client have their own hosting account?
Usually no. One agency-owned account means one bill, one dashboard, and pooled pricing tiers. Give clients their own account only when they demand infrastructure ownership — then bill for management separately.
Is cheap shared hosting ever OK for client sites?
Not if you’re charging for hosting. The support burden of the bargain tier lands on you, not the host, and one noisy neighbor eats the $10/mo you saved. Our recommended hosting page lists what we actually run client work on.
Want the guided version? Our free courses walk you through picking and setting up agency hosting start to finish — including “Launch Your First Website with Claude.”