Web Hosting Buyer's Guide: Shared, VPS, Managed, and Cloud Explained

Web hosting is the service that stores your website's files on a remote server and delivers them to visitors on demand, and the type you choose determines your site's speed, uptime, cost, and control ceiling.

What Web Hosting Actually Does

Web hosting connects three moving pieces: a domain name, DNS resolution through a nameserver, and a web server that returns files over an HTTP response. When a visitor types your URL, their browser asks a nameserver for the IP address on record, opens a connection to the web server at that address, and the server returns the HTML, CSS, JavaScript, and images that assemble your page. Per AWS's overview of web hosting, a hosting provider takes on ongoing server maintenance and security upgrades so you don't have to. In practice that also extends to jobs a browser never sees directly: bandwidth allocation and data center power and cooling.

The category everyone calls "web hosting" is actually four distinct products with different resource models and management responsibilities. Shared hosting, VPS hosting, managed WordPress hosting, and cloud hosting sit on the same continuum, but they answer very different questions about who owns the operating system, how many other tenants share your CPU cores, and how quickly the platform can absorb a traffic spike. Choosing the wrong tier is the single most common cause of the two problems every site owner eventually complains about: slow pages and surprise renewal bills.

Shared Hosting: The Entry Point

Shared hosting is the entry-level web hosting tier, where dozens or hundreds of accounts share the same physical server, disk, memory pool, and network interface, typically administered through cPanel or Plesk on top of Apache or LiteSpeed. For a plain WordPress site or a brochure page, it works fine. The friction shows up under two conditions: your traffic climbs past what a cramped resource share can serve, or a neighbor on an oversold server hogs CPU and drags everyone's response times down, the classic noisy neighbor effect. For a fuller side-by-side, see shared vs VPS vs managed hosting compared in depth.

• Resource model: pooled CPU, RAM, and disk I/O across many tenants. Every shared plan publishes a concurrency ceiling, and the entry tier sits at the bottom of its vendor's range: Hostinger, for instance, documents 20 PHP workers on Web Single against 60 on Web Business, per Hostinger's published plan limits. Tight memory ceilings and CPU throttling during usage spikes come with the territory. Kinsta's PHP workers knowledge base entry explains how a worker cap converts into queued requests.
• Who manages what: the web hosting provider handles everything below your public_html directory, including OS, web server, PHP version, security patches, and MySQL server. You install WordPress and manage your site.
• Failure modes: the noisy neighbor effect, disk I/O contention, and CPU throttling during traffic bursts. Bluehost, Hostinger, SiteGround, A2 Hosting, and DreamHost all publish policies that quarantine or throttle high-load accounts.
• Best fit: personal blogs, portfolios, brochure sites, and early-stage projects under roughly 20,000 to 50,000 monthly visitors on lightly dynamic content.

VPS Hosting: Dedicated Resources on Shared Hardware

VPS hosting, short for virtual private server hosting, is the web hosting configuration where a physical server is partitioned into isolated virtual machines using a hypervisor such as KVM or OpenVZ. Per the AWS VPS definition, each user receives a virtual machine with dedicated resources, ready to deploy and configure independently of other tenants on the same physical hardware. Standard VPS plans also grant root or SSH root access to the operating system, giving you full stack control. That resource isolation is why a virtual private server handles a Reddit spike or a Product Hunt feature where shared hosting would fold.

• Resource model: dedicated resources per virtual machine with hardware-enforced resource isolation. Common budget web hosting providers in this tier include DigitalOcean, Vultr, Linode (now part of Akamai), and Hetzner.
• Who manages what: on an unmanaged VPS, you install and update the OS (Ubuntu, CentOS, Debian), the web server (Nginx or Apache), PHP, MySQL, and Docker or any other runtime. A managed VPS shifts patching and monitoring to the provider for an added monthly fee.
• Best fit: developers who want SSH access and full control, agencies running Docker-based deployment pipelines, and growing WooCommerce stores that have outgrown shared plans but do not want to pay managed WordPress prices.

Managed WordPress Hosting: Performance Without the Server Work

Managed WordPress hosting is a web hosting category built around a single application. Instead of handing you a raw server, the provider preconfigures Nginx, PHP-FPM, MySQL, Redis, and server-level caching specifically for WordPress, ships a staging environment, runs automated backup jobs, and takes responsibility for core and PHP security patches. Kinsta, WP Engine, Cloudways, Flywheel, Rocket.net, and Nexcess are the mainstream picks. Do not confuse this with "managed cloud," which is a broader arrangement where a partner operates general AWS or Azure infrastructure for you.

What the provider handles

OS, web server, PHP, MySQL, Redis or Memcached, server-level caching (usually a full-page cache tuned for WordPress), staging environments, automated backup with one-click restore, malware scanner, and CDN integration.

What you handle

Site content, plugins, themes, third-party integrations, and application-layer security. Some providers extend into malware remediation and WordPress core updates, but plugin conflicts remain your problem.

Where it differs from managed cloud

Managed cloud vendors operate your AWS, Google Cloud, or Azure workloads and handle monitoring, incident response, security, patching, and cost optimization for arbitrary applications. Managed WordPress hosting focuses on one CMS and ships opinionated stack choices tuned for it.

Adjacent tooling

SpinupWP and GridPane are control-plane products that automate WordPress deployments on top of your own DigitalOcean, Vultr, or Hetzner virtual private server, sitting between "roll your own" and full managed WordPress hosting. WordPress Multisite and Git deployment workflows are common features across the category.

Cloud Hosting: Elastic Resources, Pay as You Go

Cloud hosting is the web hosting model where your workload runs on a pool of virtualized resources spanning many physical machines, often across multiple availability zones. Per the AWS cloud hosting definition, you pay a cloud provider to host your application across a network of physical and virtual servers spanning diverse geographic locations. Automatic scaling is the differentiator that follows from that architecture: capacity grows or shrinks as traffic changes, on Google Cloud, Microsoft Azure, and AWS alike, each billing on a consumption basis where you pay only for what you use.

• Resource model: elastic capacity across a pool of servers with pay-as-you-go billing. AWS EC2, Google Cloud Compute Engine, and Azure Virtual Machines are the reference platforms, with AWS CloudFront, Google Cloud CDN, and Cloudflare fronting the compute for delivery.
• How it differs from VPS hosting: a VPS is one virtual machine on one physical server; cloud hosting draws its resource pool from many physical servers, which is why an auto-scaling group can absorb a traffic burst that would exhaust a single VPS.
• Delivery patterns: containerization with Kubernetes, load balancer routing to multiple availability zones, and hybrid arrangements that mix public cloud, private cloud, and hybrid cloud footprints. Complexity climbs with capability.

All Four Types at a Glance

Four web hosting types, four different answers to the question "who runs the server stack, and how much elasticity do you need?" The comparison below summarizes the operational trade-offs between shared hosting, VPS hosting, managed WordPress hosting, and cloud hosting.

The Decision Criteria That Matter

Choosing web hosting comes down to seven levers, and most people over-index on one or two while ignoring the rest. Budget is a starting point, not the whole answer; a $3/mo introductory plan that renews at $13/mo and cannot handle your holiday traffic burst is not cheap in year two. Work through the criteria below in order.

• Budget with renewal-rate realism. Compare the introductory price and the renewal price side by side, and pick a plan whose renewal you can absorb 12 months from now. Shared plan introductory rates commonly sit 60 to 80 percent below the renewal.
• Technical confidence. An unmanaged VPS with root access is powerful and cheap, but if you cannot patch a Linux kernel or configure Nginx, the savings evaporate into support outages. A managed hosting plan (managed VPS or managed WordPress hosting) is the honest answer for non-Linux-fluent operators.
• Traffic volume and growth curve. Shared plans stay viable up to roughly 20,000 to 50,000 monthly visitors for lightly dynamic content. Beyond that, PHP worker limits and database contention start capping throughput.
• Application requirements. WooCommerce needs PHP worker headroom, the 256 MB WordPress memory limit its own server requirements call for, and Redis or Memcached for object caching. WordPress Multisite adds routing and file-system considerations not every host supports cleanly.
• Control needs. SSH deployment, custom PHP extensions, Docker, cron jobs, Node.js sidecars, and Git deployment pipelines are the exclusive domain of VPS or well-provisioned managed WordPress plans. Shared hosting rarely offers any of them.
• Security posture. Look for two-factor authentication on the control panel, WAF protection, DDoS mitigation, free Let's Encrypt SSL certificate provisioning, and daily backups with off-server storage. WooCommerce brings PCI-DSS scope, which raises the bar further. Uptime SLA language in the terms of service should be specific, not aspirational.
• Team size and workflow. A solo blogger and an agency running 50 client sites live in different worlds. Staging environments, role-based access, and SSH deployment pipelines separate agency-grade platforms from consumer plans. When Time to First Byte (TTFB) or Core Web Vitals (LCP, CLS, INP) degrade, the platform is usually the cause. For the mechanics, see TTFB, PHP workers, and server-level caching explained.

How We Evaluate Web Hosting

Our web hosting evaluation criteria are public and consistent across every review in this cluster. This guide is criteria-based comparative research against primary sources, not a benchmarking program. We compare each web hosting provider on the axes that actually move a site's outcomes: PHP worker and entry-process limits published in vendor documentation, uptime SLAs stated in the terms of service, renewal pricing transparency, WordPress and WooCommerce compatibility notes from vendor knowledge bases, staging environment availability, and which support channels each plan includes. We anchor definitional claims to primary sources: AWS, Google Cloud, and Microsoft Azure for the platform categories, and each vendor's own pricing page for cost figures. We ran no TTFB benchmarks and no support-response trials for this guide, and we quote no figures for either. We do not fabricate testing timelines or invent lab conditions we did not run. When a claim depends on a live benchmark we have not run, we say so.

Costs: What You'll Really Pay

Web hosting pricing splits into two numbers that rarely appear next to each other in the marketing copy: the introductory rate that pulled you in, and the renewal rate that arrives 12 or 36 months later. The cheapest sticker price is not automatically the best value once Time to First Byte and PHP worker headroom are priced in, since a slow entry-tier plan often costs more in lost conversions than the monthly savings are worth. The table below sets the entry price against the typical renewal for each tier, with vendor-specific citations in the paragraphs that follow. For the managed WordPress category specifically, see managed WordPress hosting pricing in full detail.

Shared hosting. Hostinger's WordPress plan starts at $2.99/mo introductory and renews at $10.99/mo, per Hostinger's WordPress hosting page. Bluehost's shared WordPress Starter plan starts at $3.99/mo introductory on a 36-month term, per Bluehost's WordPress page, and renews at $9.99/mo on the same term, per Bluehost's renewal price FAQ. Entry-tier extras (free SSL certificate provisioning via Let's Encrypt, a one-click WordPress install, a starter mailbox) are the norm; common add-on fees include domain registration after year one, backup storage above the free quota, and malware cleanup.

VPS hosting. VPS pricing is flat, no intro-vs-renewal gap. DigitalOcean droplets start at $4/mo per the DigitalOcean droplet pricing docs; Vultr High Performance instances start at $6/mo, with Regular Performance plans from $2.50/mo, per Vultr's pricing page; Linode (Akamai) shared-CPU plans start at $5/mo per Akamai's compute instance plan types; Hetzner Cloud prices in euros and sits in the same entry band, per Hetzner's pricing documentation. Add-on costs: managed add-ons, backups, floating IPs, and load balancers.

Managed WordPress hosting. Cloudways starts at $11/mo per the Cloudways pricing page. Rocket.net promotional plans start at $25/mo per Rocket.net's pricing page. Flywheel starts at $25/mo per Flywheel's pricing page. WP Engine starts at $30/mo per WP Engine's plans page. Kinsta starts at $35/mo per Kinsta's pricing page. Add-on costs include bandwidth overages, additional-site fees, CDN overage, and premium DNS.

Cloud hosting. Consumption-based pricing, roughly $4-50+/mo depending on instance size, bandwidth, and storage, across Azure, Google Cloud, and AWS alike: you pay only for what you use. The intro-vs-renewal problem disappears, but egress bandwidth, snapshot storage, load-balancer hours, and managed-service add-ons compound at scale.

The renewal-rate shock trap is worst on shared hosting: introductory pricing often sits 60 to 80 percent below the renewal rate, and Bluehost's jump from a $3.99/mo intro to a renewal of $9.99/mo on a 36-month term, $11.99/mo on 12 months, or $15.99/mo billed monthly, per Bluehost's renewal price FAQ, is representative. Ask before committing: what does the renewal cost, and can you absorb that cost 12 months from now? On cloud hosting, the equivalent question is: what does your bill look like once your site actually gets the traffic you are building for?

Our Recommendations by Scenario

The right web hosting pick depends on what you actually run, not which brand has the loudest marketing. The eight scenarios below map common situations to specific recommendations and the deeper techshooked guide that covers each in detail.

1. Running a WooCommerce store. Cloudways or Nexcess give you WooCommerce-tuned stacks with Redis object caching, server-level caching for anonymous traffic, and PHP worker headroom appropriate for concurrent checkouts. Start on Cloudways at $11/mo per the Cloudways pricing page via Cloudways. Budget for what the fee excludes: no bundled email or domain registration, a CDN that bills as a paid add-on, and server costs that rise with usage rather than sitting at a flat monthly cap. Full breakdown: best WooCommerce hosting for growing stores.
2. Agency managing 10 or more client sites. Cloudways agency accounts or Kinsta's multisite billing consolidate invoicing and give you role-based access and per-site staging environments. Kinsta plans start at $35/mo per Kinsta's pricing page via Kinsta. It is the most expensive entry point in this guide, its plans meter visits and bandwidth, and it blocks a curated list of plugins it considers unstable at scale. Deep dive: best WordPress hosting for agencies and freelancers.
3. Developer who needs SSH access, root access, Docker, and Git deployment. An unmanaged VPS on DigitalOcean, Vultr, or Hetzner gives you dedicated resources with hardware-enforced resource isolation and full stack control. Start on DigitalOcean droplets from $4/mo per DigitalOcean pricing docs. Understand what you are buying: the droplet is unmanaged, so OS patching, the web server, and every security update are yours, there is no WordPress support desk, and the $4 tier ships 512 MiB of RAM, too little to run WooCommerce with any headroom. Full comparison: best VPS hosting for developers with root access.
4. Budget-first blog or small business. Hostinger's Premium plan covers a WordPress launch checklist at the lowest credible entry price, with server-level caching included. Introductory pricing starts at $2.99/mo and renews at $10.99/mo per Hostinger's WordPress hosting page, available via Hostinger. The trade-offs are real: renewal is roughly 3.7 times the intro rate, the entry tier ships no staging environment, and its PHP worker allocation is the lowest in Hostinger's shared lineup. Full read: Hostinger review: what the budget tier actually delivers.
5. Frustrated with Bluehost overcrowding. The most common complaint about Bluehost's shared plans is CPU throttling and slow response times during traffic spikes. See Bluehost alternatives worth paying for for the shortlist that avoids the noisy neighbor pattern.
6. Frustrated with WP Engine cost or plan limits. WP Engine's visit caps and overage charges are the two most-cited pain points from users considering a move. See WP Engine alternatives worth switching to for the current shortlist of managed hosts that solve the pricing pinch.
7. Undecided between Kinsta, WP Engine, and Cloudways. These three are the recurring finalists in any managed hosting plan shortlist. The head-to-head is at Cloudways vs Kinsta vs WP Engine head-to-head, and the broader roundup at best managed WordPress hosting options compared.
8. First-timer trying to understand all four types. Before shortlisting vendors, get the four-type comparison at shared vs VPS vs managed hosting compared in depth. Cloud hosting only enters the picture once you have concrete traffic elasticity requirements.

Common Mistakes When Choosing Web Hosting

Most web hosting regrets trace back to six recurring mistakes. All six are avoidable if you slow down long enough to compare renewal rates, plan capacity, and migration paths before signing a 36-month term.

1. Choosing on introductory price alone. The Bluehost jump from a $3.99/mo intro to $9.99/mo renewal per Bluehost's renewal price FAQ is the canonical introductory price lock-in trap. Compare renewal rates before committing, and treat any plan whose renewal you cannot absorb as a mistake in year two.
2. Staying on shared hosting after outgrowing it. When response times climb past the 0.8-second TTFB that web.dev sets as the "good" threshold, PHP worker limits queue requests during traffic peaks, and support tickets pile up faster than answers arrive, the move to VPS or managed WordPress hosting is overdue. Waiting for a full outage is expensive; a WordPress site migration handled at your own pace is not.
3. Buying an unmanaged VPS with no Linux administration skills. An unmanaged VPS is cheap because you own the OS, the web server, the database, and every security patch. Without that experience, the savings evaporate into support outages and a security liability. Take the managed VPS tier, or step up to managed WordPress hosting instead.
4. Skipping a migration plan before switching hosts. Server migration costs during a WordPress site migration are dominated by missing MX records, DNS TTL still cached at the old IP, database charset mismatches, and media library URL rewrites. All of these cause avoidable downtime SLA breaches. The full runbook is at migrating a WordPress site without downtime.
5. Ignoring PHP worker limits when evaluating plans for WooCommerce. Every shared plan caps concurrent PHP processes, and entry tiers cap them hardest. Once checkout concurrency exceeds the cap, requests queue, time out, and carts are abandoned. Confirm the published PHP worker count, PHP version support, and memory floor before committing.
6. Locking into a proprietary control panel or backup format. Custom control panels, proprietary backup format archives, and platform-specific caching plugins all raise vendor lock-in and control panel portability costs. Prefer providers that publish standard backup archives (SQL dump plus files) and support cPanel, LiteSpeed, Nginx, or standard SSH access, so a future move is a weekend, not a project.

Frequently Asked Questions