Use one VPS per WordPress site when the sites have different owners, security needs, software stacks, release schedules, or recovery targets. Put several independent WordPress installations on one VPS when they can share infrastructure and you value lower cost and centralized operations. Choose WordPress Multisite only when the sites are deliberately managed as one network. There is no universal sites-per-VPS limit. Capacity depends on traffic patterns, PHP and database workload, caching, scheduled jobs, media processing, and the headroom you reserve for failures and growth.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The three ways to host multiple WordPress sites
“Multiple sites on one server” can describe two very different designs. WordPress documents three patterns: one Multisite installation with one database, multiple standard installations that share a database, and multiple installations with separate databases. The last option gives each site the clearest boundary while still sharing the VPS. WordPress’s documentation on these patterns is available in Installing Multiple WordPress Instances.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchOne VPS for each site
Each site receives its own operating-system environment, web server and PHP configuration, database service or database instance, files, deployment process, monitoring and backup set. The environments can still run on the same cloud account or provider, but a fault or resource spike is less likely to affect the other sites.
Several separate installations on one VPS
Every site has its own WordPress files, database and administrator accounts, while the VPS, operating-system updates, web server, PHP runtimes and monitoring are shared. This is usually the middle ground for agencies and owners of several conventional sites. WordPress’s hardening guidance recommends separate databases and database users for multiple blogs on one server; apply that advice even when the sites share hardware. See Hardening WordPress.
#1 Best Overall
WordPress Multisite
A Multisite network is a collection of sites that “all share the same WordPress installation core files,” as WordPress explains in Create a Network. Network administrators control the shared core, network-enabled plugins and themes. Individual sites retain separate media directories and content tables, but the network is intentionally governed as one system.
How the choices differ in practice
| Decision area | One VPS per site | Separate installations on one VPS | Multisite network |
|---|---|---|---|
| Monthly infrastructure cost | Highest, because every site has its own VPS allocation | Usually lowest for sites with a common stack; exact savings depend on provider and sizing | Often efficient for closely related sites, with one shared platform |
| CPU, RAM and storage headroom | Reserved per site; unused capacity on one VPS cannot automatically serve another | Shared pool improves utilization but creates contention during spikes | Shared pool and shared application layer; one busy site can affect the network |
| Failure blast radius | Normally limited to one site | A VPS, kernel, web-server or database failure can take every site offline | A network failure or incompatible network-wide change can affect every site |
| Security containment | Strongest practical separation between sites | Separate Unix users, databases and database users improve containment; the host remains shared | Shared core and network administration require trust between site owners |
| Plugin and PHP compatibility | Each site can use its own PHP version and extensions | Sites generally share the installed runtimes, although separate pools can add flexibility | Plugins, themes and core changes must work across the network’s sites |
| Deployment autonomy | Independent release windows and rollback plans | Independent WordPress releases are possible, but infrastructure changes are shared | Network-level updates can impose a common schedule |
| Backup and restore scope | Small, site-specific backup and restore jobs | Per-site backups are possible; VPS-level recovery remains a shared concern | Back up the network’s files and database structures, while testing individual-site recovery |
| Monitoring and patching burden | Most systems to patch and observe | One host to patch, with several applications to monitor | Fewest application environments, but network-wide changes need greater coordination |
| Growth and ownership changes | Easy to move, sell or hand off one site | Sites can be migrated individually, though they share host capacity | Sites are tightly coupled to the network and harder to separate later |
When one VPS per WordPress site is the safer decision
Unrelated client or organizational sites
If different customers or departments control the sites, separate VPSs make ownership and access boundaries explicit. A client’s administrator should not need to trust another client’s plugin, shell account or deployment process. Independent environments also simplify billing, incident communication and eventual migration.
Different software stacks
Use separate environments when one site needs a different PHP version, extension, web-server configuration, object-cache service or operating-system package. A plugin that is harmless on one site can be incompatible with another. A dedicated VPS lets each owner schedule upgrades after compatibility testing instead of waiting for every site to agree.
High-value transactions or strict recovery objectives
An online store, membership service or revenue-critical publication may justify a smaller failure domain. If its recovery-time or recovery-point objective is materially tighter than the other sites, give it independent compute, storage, backups and monitoring. Isolation does not eliminate risk, but it prevents an unrelated site’s crash, runaway import or compromised plugin from consuming the same resources.
Different release and uptime schedules
Separate VPSs allow maintenance on a low-traffic site without placing a busy site into the same maintenance window. They also let you roll back one site’s operating-system, PHP or plugin change without reverting other sites.
When several separate installations on one VPS make sense
Common stack and predictable workloads
Consolidation works well when sites use compatible PHP versions and extensions, similar web-server settings, and comparable traffic patterns. A shared VPS can keep CPU and memory busy instead of leaving each site with its own idle allocation.
Lower cost with deliberate boundaries
You can reduce infrastructure cost without putting every site into one Multisite network. Create a separate system user, document root, database and database user for each installation. Limit file permissions so one site’s process cannot write to another site’s files. This is not equivalent to separate VPSs—the kernel and host remain shared—but it is a materially better boundary than a single database and shared administrator credentials.
Centralized operations
One host means one operating-system patch cycle, one base monitoring configuration and one place to maintain the web server. Keep application operations site-specific: inventory each site’s plugins, PHP requirements, cron jobs, owners, backup schedule and rollback procedure. Centralized infrastructure should not become a reason to use one shared administrator account.
When WordPress Multisite is the right model
Sites with shared governance
Multisite is designed for a network whose sites intentionally share core files, network-managed plugins and themes. It suits a school with departmental sites, a publication with regional editions, or a company managing branded sub-sites under one technical team. A network administrator can maintain common functionality once and make it available across the network.
What remains separate inside a network
Each site has its own content tables and media directory, so posts and uploads are not automatically merged. Nevertheless, the shared core and network-level administration create a common change and security domain. A vulnerable or incompatible network-enabled plugin can affect every site that uses it.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesReasons not to choose Multisite
WordPress warns in Before You Create A Network that a network may not fit sites requiring strong interconnection, shared data or shared users in the way you expect. In practice, avoid Multisite when owners need independent administrators, sites require incompatible plugins or PHP versions, release policies differ, or you may need to separate a site later. Network setup also has additional domain, hosting and configuration requirements compared with a normal installation.
How many WordPress sites can one VPS handle?
No responsible universal number exists. The reviewed WordPress and AWS guidance does not publish a sites-per-VPS limit, a minimum VPS size or a traffic break-even point. Any fixed claim such as “ten sites per gigabyte of RAM” ignores the variables that dominate performance.
Measure the workload that actually matters
- Request mix: Cached page views are cheap compared with uncached PHP requests, logged-in sessions, searches and checkout actions.
- Concurrency: A short traffic burst can exhaust PHP workers even when daily page views look modest.
- Database work: WooCommerce queries, reporting, imports, revisions and poorly indexed plugin tables consume CPU, memory and storage I/O.
- Background jobs: Backups, image regeneration, scheduled publishing, email queues and feed imports compete with visitor traffic.
- Media and storage: Large uploads and image transformations require both disk space and temporary working room; storage latency matters as much as capacity.
- Headroom: Reserve capacity for spikes, updates and recovery tasks rather than sizing to the average.
A practical sizing process
- List every site’s peak-hour requests, logged-in usage, scheduled jobs, database size and monthly media growth.
- Group sites by compatible PHP, extension and web-server requirements.
- Load-test representative pages and authenticated workflows while observing CPU, memory, disk I/O, database latency and PHP-worker saturation.
- Add the workloads together and repeat the test with a failure scenario, such as one site running an import while another receives a traffic spike.
- Choose a VPS with measurable reserve capacity, then set alerts before CPU, memory, storage or PHP-worker exhaustion becomes an outage.
Re-test after major plugin changes, a traffic increase or the addition of another site. Capacity is an operational measurement, not a permanent property of a VPS plan.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Backups, security and recovery on a shared VPS
Keep backups restorable per site
WordPress’s hardening guidance recommends regularly timed snapshots of files and databases. Schedule backups often enough to meet each site’s recovery-point objective, retain copies outside the VPS, and test restoring one site without overwriting its neighbors. A single VPS snapshot is useful for disaster recovery, but it should not be your only way to recover an accidentally deleted post or a corrupted plugin update.
Separate credentials and databases
Give each installation a distinct database and least-privilege database user. Do not reuse WordPress salts, administrator passwords or deployment keys across unrelated sites. On a shared host, separate Unix users and document roots reduce accidental cross-site writes; they do not protect against a fully compromised operating system, so patch the host and monitor it as one security boundary.
Plan for the shared failure domain
Document which sites are on each VPS, who owns them, where backups are stored, and how to disable one site without stopping the others. Keep emergency access independent of a single WordPress administrator account. If the host, kernel, storage volume or database service fails, every co-located site may be affected; your recovery plan must address that scenario explicitly.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Operating and monitoring each architecture
For one VPS per site
- Automate baseline hardening, patching and configuration so the larger server count remains manageable.
- Give every site its own uptime, error-rate, disk-space and backup-success alerts.
- Document a tested restore and rollback procedure for each owner.
For separate installations on one VPS
- Monitor resources both per site and at the host level; aggregate CPU or memory graphs can hide one noisy neighbor.
- Set limits on PHP workers, upload processing and scheduled jobs so one site cannot starve the others.
- Patch the operating system and shared services during a coordinated window, while releasing WordPress and plugins site by site.
For Multisite
- Test every network-wide plugin, theme and core update against representative sites before deployment.
- Define who can install or activate network plugins and who can administer individual sites.
- Back up network files and databases, then prove that an individual site can be recovered without damaging the rest of the network.
A decision checklist
Choose one VPS per site if most answers below are yes:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Do the sites have unrelated owners or contractual access boundaries?
- Would one site’s compromise or outage be unacceptable for the others?
- Do they need different PHP versions, extensions, plugins or deployment windows?
- Do their uptime, backup or recovery objectives differ substantially?
- Is independent migration or sale of a site likely?
Choose separate installations on one VPS if the sites share a compatible stack, can tolerate a common host failure, and lower infrastructure cost matters. Preserve separate databases, users, files, backups and deployment records.
Choose Multisite only if one team intentionally governs the network, shared core files and network-managed extensions are acceptable, and the sites do not need independent software or release policies.
What AWS’s guidance adds to the decision
Amazon Web Services describes “a single server installation for low traffic websites” as the simplest option in its Best Practices for WordPress on AWS. It presents more advanced architectures as incremental improvements in availability and scalability, not as mandatory starting points. That supports a proportional approach: begin with the simplest architecture that meets your isolation and recovery requirements, instrument it, and split sites or add redundancy when measured risk and workload justify the additional operational cost.
Moving from one model to another
Splitting a site out of a shared VPS
- Inventory the site’s files, database, PHP version, extensions, cron jobs, DNS records, mail dependencies and external integrations.
- Provision the destination VPS with matching or tested versions and restore a copy of the files and database.
- Test front-end pages, administrator login, forms, scheduled jobs, media uploads, payments and integrations on a temporary hostname.
- Lower DNS time-to-live ahead of the cutover, freeze writes for the final export, and perform a final database and file synchronization.
- Switch DNS, monitor errors and resource usage, and keep the old copy available until the agreed rollback window ends.
Consolidating sites safely
Confirm that the destination has enough tested headroom for peak workloads plus recovery tasks. Recreate each site with separate users and databases, migrate one site at a time, verify backups and monitoring, and only then retire the old environment. Do not use consolidation to conceal unresolved plugin incompatibilities or an undersized database server.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Bottom line
There is no best architecture for every WordPress portfolio. Dedicated VPSs buy isolation, compatibility freedom and smaller failure domains. Separate installations on one VPS provide a cost-efficient compromise when stacks and risk tolerance align. Multisite is a governance choice for intentionally related sites, not merely a cheaper way to host unrelated customers. Decide from ownership, compatibility, recovery and measured resource usage first; use cost as a constraint, not as the only design criterion.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
