VPS vs Shared Hosting vs Dedicated vs Cloud: How to Choose (2026)

VPS vs shared hosting comes down to isolation and control. Shared hosting gives you an account on a server whose CPU, memory and software you share with other customers; a VPS (virtual private server) gives you a virtual machine of your own, with its own operating system, a fixed allocation of RAM and disk, and full root access.

Shared hosting is the simpler choice for a small site; a VPS is the step up when you keep hitting your host’s resource limits, need software the host will not run, or want performance you can predict. A dedicated server gives you a whole physical machine, and a hyperscaler cloud VM (AWS, Google Cloud, Azure) is a virtual machine billed as separate metered parts.

VPS vs shared hosting vs dedicated vs cloud: the comparison table

The table compares the five options on the questions that decide most moves. Shared hosting is often sold simply as “web hosting.” “Managed hosting” is a service level that can sit on top of any of the other four, so its column describes what the provider takes off your plate. If the term VPS is new to you, read what a VPS is and how it works first.

One caveat on the VPS column: KVM-based plans, ours included, run their own kernel. Container-based VPS products, such as those built on LXC, aim for an environment close to a standard Linux installation “but without the need for a separate kernel”: they share the host’s kernel.

Quick decision checklist

• Stay on shared hosting if your site runs on PHP and MySQL, never hits its resource limits, and you want the host to handle updates, email and backups.
• Choose a VPS if you need root access, a long-running process (a Node.js app, a bot, a queue worker), software your host does not offer, or limits you set yourself.
• Choose a VPS with dedicated vCPUs before a dedicated server if your problem is CPU contention rather than the size of the machine.
• Choose a dedicated server if one workload keeps many cores or the disks busy around the clock, or a contract requires single-tenant hardware.
• Choose a hyperscaler if you will actually use its managed databases, autoscaling, identity controls or region count.
• Choose managed hosting if nobody on your team wants to patch a server, and you would rather pay for that work than do it.

How shared hosting works, and where its limits come from

On shared hosting, many customer accounts run inside one operating system on one server. You manage files and databases through a control panel such as cPanel, but you cannot install system software or change the server’s configuration.

To stop one busy site from slowing down everyone else, the host caps each account. On servers that run CloudLinux OS, these caps are called LVE limits. The CloudLinux documentation lists them: CPU speed, physical memory, entry processes (concurrent connections), number of processes, disk throughput (IO), disk operations per second (IOPS) and inodes (the number of files and folders you may store).

The same documentation says what happens at each cap: a site limited by CPU or IO “will start responding slower,” and a site limited by memory or process count gets 500 or 503 errors. When concurrent requests go above the entry-process limit, the web server serves a 508 “Resource Limit Reached” page. Those three symptoms are the clearest sign that your site is hitting the plan’s limits; the matrix below sorts out whether a bigger server or leaner code is the fix.

Shared hosting is still the right answer for a lot of sites. If your account never touches its limits, a VPS will not make it noticeably better, and you would take on server maintenance for nothing.

Is a VPS faster than shared hosting?

Often, but not automatically. A VPS is faster when shared hosting was the thing holding you back: your site hit its CPU, memory or entry-process limits, or other accounts kept the server busy. It is not faster when the slowness comes from the site itself, such as uncached pages, a heavy plugin or a slow database query. The same code on a bigger machine stays slow, and a k6 load test from a VPS against a staging copy helps tell the two cases apart before you move.

A VPS has neighbors too, but a hypervisor fences them off. DigitalOcean’s plan documentation is a clear public example: RAM, disk and network bandwidth are always dedicated, while a shared-CPU Droplet’s hyper-thread “may be shared between multiple other Droplets” and dedicated-CPU plans “have guaranteed access to the full hyper-thread at all times.” HourlyVPS draws the same line.

You can measure CPU contention instead of guessing. On a Linux VPS, run top and read the st value in the CPU line. The top manual defines it as “time stolen from this vm by the hypervisor.” If steal time stays high while your app is slow, the physical CPU is busy with other guests: a plan with dedicated vCPUs fixes that, and a code change does not. The VPS benchmark guide shows how to log steal time over a whole test.

Signs you have outgrown shared hosting

Use this matrix before you buy anything. Each row pairs a symptom with its usual cause, where to check it, and whether a VPS fixes it. On cPanel servers with CloudLinux, the “CPU and Concurrent Connection Usage” page (CloudLinux’s Resource Usage plugin) shows when and how often your account hit each limit.

If two or more rows describe your site and the last column says yes, the move is worth planning. If your only symptom is the last row, spend an afternoon on caching before you spend money on a server. If your problem looks like row 6, plan the mail move before you make it: a VPS gives you your own IP address and its reputation, and outbound port 25 starts closed on new HourlyVPS servers and opens only on request, as our acceptable use policy explains.

What you take over when you leave shared hosting

Shared hosting bundles a lot of work into the price, and an unmanaged VPS hands that work to you. At HourlyVPS, for example, you get root access and run the operating system and everything on it; we run the hardware, the hypervisor and the network.

None of this is hard, but it never ends: updates and backup checks are recurring chores, not one-time steps. Start with connecting to the server over SSH, then work through the security checklist for a new Linux VPS before you expose any port. For the web layer, Caddy as a reverse proxy with automatic HTTPS and Docker on Ubuntu keep the moving parts few. If the Linux command line itself is new, eight hands-on Linux labs on a throwaway VPS teach the basics behind these chores, about two hours per lab.

Managed VPS vs shared hosting: who does the upkeep?

“Managed” describes who does the work in the table above, not a kind of server. On a managed VPS the provider patches the OS and supports the software stack; managed WordPress hosting goes further and runs the whole application platform. That labor is part of the price, while an unmanaged VPS is priced for the server alone because you supply the labor yourself. Our who-does-what table for managed and unmanaged VPS splits the tasks line by line. A self-hosted platform such as Coolify on a VPS sits in between: it automates Git deploys, HTTPS certificates and database backups from a dashboard, while you still patch the server.

VPS vs dedicated server

A dedicated server is a physical machine that only you use; a VPS is one of several virtual machines a hypervisor carves out of a physical machine. With a dedicated server you get every core, all the RAM and the full disk bandwidth, with no hypervisor and no neighbors.

You also take on hardware. A bigger dedicated server means a new order and a migration, and a failed component means a repair window. A VPS is a smaller, more flexible unit: you can add a second server for a week, or delete one the hour a job ends.

When a dedicated server is the right call

• One workload keeps many cores busy around the clock: large databases, build farms, video encoding.
• You need the full throughput of local disks, or more RAM than VPS plans offer.
• A contract, audit or software license requires single-tenant hardware.
• You want to run your own hypervisor and split the machine yourself.

The middle ground: dedicated vCPUs

If steal time is your problem, a VPS with dedicated (pinned) vCPUs removes the CPU sharing without the hardware commitment. At HourlyVPS you still pay by the hour, never more than the plan’s monthly price for a server in a billing period, and you can delete the server when the job ends. Chrono plans are built for this:

VPS vs cloud server: is a VPS a cloud server?

Usually, yes. NIST defines cloud computing by five essential characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity and measured service. A VPS ordered from a web portal, reached over the internet, run on a pooled host and billed by the hour matches most of that list, which is why so many VPS products are sold as “cloud servers.”

Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.

NIST Special Publication 800-145, The NIST Definition of Cloud Computing (September 2011)

The useful difference is between bundled VPS plans and hyperscaler clouds (AWS, Google Cloud, Microsoft Azure, Oracle Cloud). A bundled plan sells one price for CPU, RAM, disk, an IPv4 address and a traffic allowance. A hyperscaler prices each part separately and bills it by the second or minute, which suits autoscaling but makes the monthly total harder to predict.

Does a cloud server run on many machines at once?

Many hosting articles say a cloud server spreads across many physical machines while a VPS sits on one. In practice, one virtual machine runs on one physical host at a time on either platform; the difference is what happens around that host. Google’s Compute Engine documentation describes live-migrating VMs to another host for planned maintenance, and says that if the hardware fails completely, the instance “terminates and restarts automatically.” That is a restart, not zero downtime, so keep backups off the server whichever option you choose.

Bundled vs component pricing, in numbers

The entry sizes below come from our Hourly VPS Fine-Print Index, where every cell links to the provider’s own page. Prices are list prices in USD as checked on October 2, 2026.

The arithmetic shows where component pricing bites. A Google e2-micro plus one external IPv4 comes to $0.008376428 + $0.005 = about $0.0134 per hour before any disk, or roughly $9.76 for a 730-hour month (our arithmetic from the Index figures). The bundled plans above already include the disk and the address. In fairness, Google’s Free Tier covers one e2-micro instance a month in three US regions, plus 30 GB-months of standard persistent disk, which changes the math for a single tiny VM.

HourlyVPS plans are bundled the same way. Every server comes with one dedicated IPv4 address and IPv6, included in the plan price.

Where hyperscalers are a better fit

Choose AWS, Google Cloud or Azure when you need what sits around the VM: managed databases and queues, autoscaling, fine-grained identity and access controls, or reach. The Index lists 43 Compute Engine regions and 80+ Azure regions. For one website, a bot or a game server, a bundled VPS is simpler to budget. HourlyVPS runs in Istanbul today, with New York coming soon, so check the locations page and our guide to choosing a VPS location by latency before you decide.

Is a VPS more expensive than shared hosting?

At the entry level, list prices overlap more than most comparisons suggest. Hostinger’s web hosting page lists its Premium shared plan at $2.99/month on a 48-month prepaid term, renewing at $10.99/month (as of October 3, 2026). The bundled VPS plans in the Index table above list at $4.00 to $5.00/month (as of October 2, 2026).

They are not equivalent products. The shared price includes the host’s administration work, a control panel and often email; an unmanaged VPS price covers the server alone, and 512 MB or 1 GB of RAM is tight for a database-backed site (the sizing table below starts at 2 GB). How the bill is built differs too:

• Shared hosting: long prepaid terms. The headline monthly price often assumes the longest term: Hostinger’s $2.99/month is billed as $143.52 for the 48 months up front. Compare renewal prices, not introductory ones.
• VPS: monthly, often usage-based too. Many VPS providers also bill by the hour, minute or second. In our Index of 20 hourly-billed providers, 12 bill a stopped server in full until you delete it; the stopped-server billing guide lists who does what. Vultr vs DigitalOcean vs Hetzner billing shows how far the rules differ between three large providers.
• Hyperscaler cloud: post-paid components. Compute, disk and public IPv4 are metered separately and invoiced after the fact; Google bills compute per second after the first minute, Azure per full minute.

How to move from shared hosting to a VPS

Build the new server next to the old one, copy everything, test it privately, and only then switch DNS; keep the shared plan until the move is proven. The steps assume a PHP and MySQL site such as WordPress, SSH access to both machines, and an Ubuntu 24.04 LTS VPS with a web server, PHP and the same database family as the old host (MySQL or MariaDB, same or newer version) so the dump imports cleanly. Our guide to install WordPress on a VPS builds that stack with Caddy, PHP-FPM and MariaDB.

1. Deploy and secure the VPS. Log in with an SSH key, enable the firewall, install updates and disable root login, as in the VPS security checklist.
2. Lower the DNS TTL and check your mail records. At your DNS provider, set the TTL of the domain’s A and AAAA records to a few minutes, at least one old-TTL period before the switch, so resolvers drop the old address sooner. If the MX record points at the bare domain, mail follows the A record, so move mail or give it its own host name first.
3. Export the database on the old host (command below).
4. Copy the files and the dump to the VPS with rsync (command below).
5. Import the database into an empty database on the VPS, and update the app’s config if the database name, user or host changed (for WordPress, wp-config.php).
6. Test privately with curl --resolve and a hosts-file entry, before any visitor sees the new server.
7. Cut over. Pause edits on the old site, run rsync and the database export once more, import again, then point the A and AAAA records at the VPS.
8. Finish up. Watch HTTPS right after the switch: Let’s Encrypt’s HTTP-01 challenge fetches a file from your domain on port 80, so it succeeds only once the domain resolves to the VPS (the DNS-01 challenge is the alternative if you need a certificate earlier). Then watch the logs, move DNS hosting if it lived on the shared plan, and only then cancel it.

Export the database

Run this on the old host over SSH, from your home directory; it prompts for the database password. Per the MySQL manual, --single-transaction dumps a consistent state of InnoDB tables “without blocking any applications.” The manual also lists the PROCESS privilege as required unless you pass --no-tablespaces; a shared-hosting database user may lack that privilege, so the command includes the flag. On MariaDB hosts the tool is also named mariadb-dump and takes the same options.

mysqldump --single-transaction --no-tablespaces -u DB_USER -p DB_NAME > site.sql

Copy the files with rsync

Run these on the VPS as your sudo user, with your domain in place of example.com; the first two lines create the web root and make you its owner. The trailing slash on public_html/ copies the folder’s contents, not the folder. At cutover, run the rsync lines again: its delta-transfer algorithm sends only what changed. rsync must be installed on both ends; if your host offers only FTP, download a full backup from the control panel instead.

sudo mkdir -p /var/www/example.com
sudo chown "$USER": /var/www/example.com
rsync -avz [email protected]:public_html/ /var/www/example.com/
rsync -avz [email protected]:site.sql ~/

Import the database and test privately

Create an empty database and user on the VPS first, then load the dump:

mysql -u DB_USER -p DB_NAME < ~/site.sql

Point the web server’s site configuration at /var/www/example.com, then request the site from your own machine with the VPS address forced. The curl manual calls --resolve “a sort of /etc/hosts alternative provided on the command line.” Replace 203.0.113.10 with the VPS IP address:

curl -sI --resolve example.com:80:203.0.113.10 http://example.com/

A 200 or a redirect shows that the VPS answers, but a default welcome page also returns 200. For the real check, add a temporary hosts-file entry on your computer and click through old pages, log in and submit a form; if the site forces HTTPS, expect certificate errors until the VPS has its own certificate.

For WordPress, the official migration guide confirms that if the database and URL stay the same, you can move by copying the files and database alone. If the URL changes, use a serialization-aware tool such as WP-CLI’s search-replace, not a raw find-and-replace.

Which VPS size should you start with after shared hosting?

There is no official RAM figure for “a WordPress site,” so treat this as reasoning, not a benchmark. On a VPS the operating system, the database server and every PHP worker share the plan’s RAM, and the database usually wants the biggest slice. Start here, then check memory use after a week of real traffic.

What the move costs depends on how long each server runs: a rehearsal server you delete after a few hours, then a production server that stays online. The table shows what a Quartz Q2 costs for each duration on hourly billing; a server left on for the whole month stops at the monthly cap:

The rehearsal server bills only the hours it exists. A test copy you keep for a few days costs 24 hours of hourly billing per day, which is all a daily VPS is here. The production site stays online every day, so its bill stops at the monthly cap each billing period: that is what a monthly VPS means here, with no contract and nothing to renew. To compare totals across providers, try the VPS cost calculator, and for a wider view of prices read how much a VPS costs.