Separate capacity from ownership
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.
Compare two fictional 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. Do not claim that one-server-per-client is always safer or cheaper; specify which operational boundary the extra separation is intended to provide.
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.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Cloudways distributing sites across servers — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- Cloudways server transfers: owner and paid-account requirements — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21