Shared hosting, VPS hosting, dedicated hosting, and managed WordPress hosting are four different operational models for running WordPress. Each has different cost, performance, isolation, and operational responsibility characteristics. For institutional WordPress operators (university web teams, government communications staff, nonprofit IT teams), the model decision shapes the operational reality of running WordPress for years to come. This post is the institutional decision filter.
We covered what managed WordPress hosting includes in Managed WordPress Hosting 101. This post compares the operational models institutions actually consider.
The Four Hosting Models
Shared Hosting
The hosting provider operates one server (or server cluster) hosting hundreds or thousands of WordPress installations from many customers. Each site gets a portion of the underlying CPU, memory, and disk. The institutional reality:
Cost. Lowest of the four models. Typical pricing: $5 to $30 per month per site.
Performance. Lowest predictability. The "noisy neighbor" effect (a different customer's traffic spike consuming shared capacity) is real and often unpredictable.
Isolation. Lowest. Vulnerabilities or misconfigurations in one customer's site can sometimes affect others.
Operational responsibility. The institution operates WordPress (updates, backups, plugins). The provider operates the server.
Institutional fit. Generally not appropriate for institutional WordPress. Suitable only for the smallest of departmental sites with low traffic, low importance, and no compliance considerations.
Virtual Private Server (VPS)
A virtual machine on shared hardware, with dedicated CPU, memory, and disk allocations. Multiple VMs run on one physical server, but each VM is isolated from the others. The institutional reality:
Cost. Mid-range. Typical pricing: $20 to $100 per month per VPS.
Performance. More predictable than shared. The noisy-neighbor effect is reduced because of CPU and memory isolation.
Isolation. Better than shared. VMs are isolated at the hypervisor level.
Operational responsibility. The institution operates WordPress and the VPS. Server-level management (OS updates, security hardening, monitoring) is institutional.
Institutional fit. Reasonable for institutional sites with limited traffic and basic operational needs. Requires institutional capacity to manage the VPS layer. Common for technical institutional teams running their own WordPress.
Dedicated Server
The institution gets a full physical server. No other customers share the hardware. The institutional reality:
Cost. Higher. Typical pricing: $200 to $2,000+ per month depending on server specifications.
Performance. Highest predictability for the cost. No virtualization overhead, no shared resources.
Isolation. Highest. The institution has full hardware isolation.
Operational responsibility. The institution operates WordPress, the server, and (typically) the supporting infrastructure. Highest operational burden of the four models.
Institutional fit. Increasingly rare. Most institutional workloads that justified dedicated hardware historically have moved to cloud-based alternatives (managed WordPress on cloud, dedicated cloud capacity through Reserved Instances). Dedicated servers persist for specific institutional cases (regulatory data residency, specialized hardware requirements).
Managed WordPress Hosting
The provider operates the WordPress runtime and the underlying infrastructure as a service. The institution provides content and configuration. The institutional reality:
Cost. Mid-to-high range. Typical pricing: $50 to $500+ per month per site for institutional-grade managed WordPress.
Performance. Highest predictability. Provider operates an optimized WordPress platform with cache, CDN, and tuned PHP runtime.
Isolation. High. Per-site isolation at the application or container level, even if underlying infrastructure is shared.
Operational responsibility. The institution operates content, plugins, and themes. The provider operates everything else (WordPress core, server, security baseline, performance tier).
Institutional fit. The most common institutional choice for new WordPress deployments. Combines operational simplicity with WordPress-specific optimization. The most common institutional question is which managed provider, not whether to use managed.
The Institutional Decision Filter
The decision filter that holds for institutional WordPress:
What is the institutional operational capacity? Institutions with deep WordPress operational expertise can run VPS or dedicated effectively. Institutions without that expertise get more value from managed hosting.
What is the performance requirement? Public-facing institutional sites with high traffic or visibility need the predictable performance that VPS, dedicated, or managed hosting provides. Shared hosting does not meet institutional performance expectations.
What is the compliance posture? Sites with compliance considerations (FERPA-adjacent education content, HIPAA-adjacent healthcare content, state-level privacy law requirements) typically run on dedicated or managed hosting where the provider can document the controls. Shared hosting documentation is typically inadequate for institutional compliance.
What is the institutional cloud strategy? Institutions with broader AWS or Azure strategy often benefit from WordPress hosted on the same cloud platform (sometimes through a managed partner) for unified governance. Institutions without a broader cloud strategy benefit from pure-play managed WordPress that does not require cloud expertise.
What is the budget profile? Smaller institutional WordPress can fit pure-play managed hosting at moderate per-site cost. Larger institutional fleets often produce better economics with managed cloud-hosted WordPress through a partner.
What Mature Institutional WordPress Hosting Looks Like
Institutional WordPress that produces sustained value typically lands on managed hosting (either pure-play managed WordPress or managed WordPress on cloud through a partner). The exceptions:
Specialized institutional sites with deep customization. Sites with custom infrastructure requirements (specialized integrations, custom workflows, unusual capacity profiles) sometimes run on dedicated or VPS where the institution has full control.
Institutional development and staging environments. Lower environments often run on VPS or dedicated for cost efficiency. The production environment runs on managed.
Institutional WordPress fleets with shared infrastructure. Universities running multisite WordPress at scale, government agencies with sub-site networks, sometimes operate dedicated infrastructure shared across the fleet.
For WordPress hosting engagements supporting institutional sites, the model decision is one of the first conversations. The right model depends on the institutional context.
Frequently Asked Questions
Should institutional WordPress ever run on shared hosting?
For institutional sites with any of: meaningful traffic, compliance considerations, high availability requirements, or institutional brand visibility, the answer is no. Shared hosting is operationally inadequate for institutional WordPress in any of those cases. For low-traffic departmental sites with no compliance considerations and explicit acknowledgment of the operational limitations, shared hosting is sometimes acceptable, but the institutional pattern that holds is to standardize on better-suited models.
What is the difference between managed WordPress hosting and managed cloud hosting with WordPress?
Managed WordPress hosting (WP Engine, Pantheon, Kinsta) is a WordPress-specific service. The provider operates WordPress at scale across thousands of customers. Managed cloud hosting with WordPress (AWS-hosted WordPress operated by a partner, Azure-hosted WordPress operated by a partner) is a more general managed-cloud service that includes WordPress as a workload. Both are valid institutional choices; the right one depends on broader institutional cloud strategy.
Can institutional WordPress migrate between hosting models?
Yes. WordPress is portable, and migration between hosting models is operationally similar to migration between providers within the same model. Institutional migrations typically involve: content export, target platform setup, content import, DNS cutover, validation, post-migration support. The friction is in coordination and validation, not in the technical migration.
How does this decision interact with the institutional CMS choice?
The hosting model decision applies once the institution has chosen WordPress. For institutions still selecting a CMS, the hosting model question is downstream of the CMS decision. We covered the higher-ed CMS selection criteria in Higher Education CMS Selection.