Practical guide

How to host multiple WordPress sites on one server, and when to split them

Last reviewed October 6, 2026

Quick answerGive each site its own application, files and database on the server, keep small sites together and move a busy one to a server of its own.

Separate capacity from ownership

To host multiple WordPress sites on one server, run each as its own application with its own files and database; Cloudways Flexible runs as many applications as the server can carry, and Cloudways advises groups of at most ten small sites a server.

Several modest WordPress applications may share server resources, but capacity efficiency is only one design question. Who owns the commercial relationship, who can authorize changes and how a client leaves can matter more than the number of sites. Cloudways documents transferring a server between accounts; that is a different operation from moving one application out of a server shared by several unrelated clients. Plan the unit of ownership explicitly.

A Cloudways server can be tested for 3 days with no credit card.

We may earn a commission if you buy through links on this page, at no extra cost to you.

Start a 3-day Cloudways trial →

Compare two example portfolios

Imagine four stable brochure sites owned by one company and four unrelated clients with separate contracts. The technical workload might look similar, but the second arrangement has more independent exit and billing requirements. A shared server can still be appropriate if those responsibilities are understood. One server per client is not always safer or cheaper; it pays off when you can name the operational boundary the extra separation gives you.

Consider the failure and change boundary

An application has its own files and database, yet a busy task can still compete for shared server resources. Maintenance, scaling and server-level access can also affect more than one site. List the applications that could be touched by a proposed operation before approving it. A directory boundary or a different domain name does not automatically create independent capacity, independent billing or a separately recoverable server configuration.

Write the exit test before provisioning

Ask how one client would take control of their website without disturbing the others. If the answer requires migrating an application, include that work and its verification in the handoff plan. If a whole server will transfer, verify the current account and eligibility requirements. Choose the arrangement whose operating and exit procedures your team can actually support, then use workload evidence to size it rather than reversing that order.

Continue when useful

Next: Cloudways reseller hosting: running and billing client sites as an agency

Resell Cloudways by running client sites on your own servers and invoicing clients with the Client Billing & Reporting add-on; Stripe's fee is charged separately.

Open Cloudways reseller hosting: running and billing client sites as an agency →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labeled so you can separate product claims from independent evidence.

  1. Cloudways distributing sites across servers — Merchant documentation · support.cloudways.com · Merchant-controlled · read October 5, 2026
  2. Cloudways server transfers: owner and paid-account requirements — Merchant documentation · support.cloudways.com · Merchant-controlled · read September 21, 2026
  3. Cloudways pricing — Vendor pricing page · cloudways.com · read October 6, 2026
  4. Cloudways home page and FAQ — Vendor product page · cloudways.com · read October 6, 2026