Explore WaseerHost

Appearance

BlogWeb Hosting 11 min read

Shared hosting vs VPS: differences and when to move up

Shared hosting gives you an account on a server the host runs. A VPS gives you a virtual server you run yourself. Compare control, resources, upkeep and cost.

Shared hosting vs VPS: differences and when to move up

Summarize with:

Share:

The shared hosting vs VPS choice comes down to who runs the server. On shared hosting, your site lives in one account on a server the host manages for many customers. On a VPS (virtual private server), you rent a virtual machine with its own operating system and a fixed amount of CPU, memory and storage, and unless you pay for management, you run it yourself.

Key takeaways

  • Shared hosting gives you an account on a server that the host installs, patches and secures. A VPS gives you a whole virtual server and root access to it.
  • Both types share physical hardware. Shared accounts split one operating system, and each VPS has its own.
  • A shared account that reaches its limits slows down or returns errors such as 508 or 503. A VPS that runs out of memory or CPU has the same problem, but you choose the plan size and can see every process.
  • On an unmanaged VPS you handle updates, the firewall, SSH access, backups and monitoring. Budget time for that work or pay for a managed plan.
  • Move up when you can name the limit you are hitting or the software you cannot install. A slow site is often a caching or plugin problem that a VPS will not fix.

What shared hosting is

Shared hosting places many customer accounts on one server. Every account uses the same operating system, web server and database server, and the host keeps all of it installed and updated. You log in to a control panel such as cPanel to add domains, create email accounts, manage databases and upload files.

You do not get root access, and that is the reason shared hosting needs so little upkeep. The host decides which software versions are available, and you pick from that list. On many plans you can still choose a PHP version per site or run a Node.js or Python app from the control panel, but you cannot install system packages or change server-wide settings.

What a VPS is

A VPS is a virtual machine. Red Hat's documentation describes a hypervisor as software that pools a physical machine's processing, memory and storage and reallocates them among virtual machines. Each virtual machine contains its own operating system and is isolated from the others on the same host.

For you, that means a server that behaves like a small dedicated machine. You pick the operating system, log in over SSH as an administrator, and install whatever the project needs. Nothing arrives preconfigured unless the plan includes it, so a control panel, a mail server and backups are either extras you buy or things you set up.

Shared hosting vs VPS at a glance

AreaShared hostingVPS
What you rentOne account on a shared serverA virtual server with its own operating system
Access levelControl panel user, no rootRoot or administrator over SSH
Software choiceVersions the host offersAnything the operating system can run
ResourcesPer-account limits set by the hostCPU, memory and storage set by your plan
Server maintenanceDone by the hostDone by you, or by the host on a managed plan
Skills neededUsing a control panelLinux command line and basic server security
Cost modelOne flat fee that covers the server workFee scales with resources, with extras billed separately
Typical useBusiness sites, blogs, small storesBusy sites, custom stacks, long-running apps

Control: a panel account or the whole server

Control is the clearest difference. A shared account lets you manage your own sites inside limits the host sets. A VPS lets you change the server itself.

Things you can usually do on shared hosting through the control panel:

  • Add domains and subdomains, and issue SSL certificates
  • Create mailboxes and databases
  • Choose a PHP version for each site
  • Schedule cron jobs and manage files

Things that need a VPS:

  • Installing system packages or a different database or web server
  • Running background workers, queues or WebSocket servers that stay up all day
  • Running Docker containers
  • Editing server-wide configuration, kernel settings or firewall rules
  • Opening custom ports for your own services

If nothing on the second list applies to your project, a VPS adds work without adding anything you would use.

Resources and performance isolation

Every server has a finite amount of CPU, memory and disk throughput. The two hosting types divide it in different ways, and that decides what happens during a traffic spike.

What happens when a shared account hits its limit

Good shared hosts put a cap on each account so one busy site cannot take down the server. A common tool for this is CloudLinux OS, which places each account in a container it calls an LVE. The CloudLinux documentation says the goal is "to make sure that no single web site can bring down your web server", and it limits CPU, memory, disk IO, the number of processes and the number of entry processes (concurrent connections) for each account.

The same documentation describes what a visitor sees at each limit:

  • At the CPU or IO limit, the site responds more slowly.
  • At the entry process limit, the server returns error 508.
  • At the memory or process limit, scripts fail with 500 or 503 errors.

So a shared plan has a ceiling. If your site returns 508 errors every time a campaign goes out, you have reached it.

What isolation a VPS gives you and what it does not

A VPS isolates you at the operating system level. Your memory and CPU allocation belongs to your virtual machine, and another customer's PHP script cannot use your entry processes because that customer runs a separate operating system.

Isolation has limits. The virtual machines still share the physical CPUs. On Linux, the top command shows a value labelled st, which the manual page defines as "time stolen from this vm by the hypervisor". A high st value means other virtual machines on the host are competing for the CPU your plan lists.

A VPS also has a ceiling of its own. When a Linux server runs out of memory, the kernel's OOM killer ends a process to keep the system running, and that process may be your database. You fix it by tuning the software or buying a larger plan.

Maintenance: what you must manage yourself on a VPS

On an unmanaged VPS, the provider keeps the hardware, network and hypervisor running. Everything inside the virtual machine is yours. Plan for these jobs before you move.

  1. Keep the operating system updated. Ubuntu's documentation says the unattended-upgrades package is installed by default and applies security updates automatically. Other updates, and the reboots some of them need, are still your job.
  2. Turn on a firewall. On Ubuntu the default tool is ufw, and the firewall documentation notes that it is disabled at first.
  3. Secure SSH. Create a key pair and copy the public key to the server so you log in with a key, as the OpenSSH guide shows.
  4. Install and tune the stack. The web server, PHP or Node.js, the database and SSL renewal are your choices and your configuration.
  5. Set up backups and test a restore. Check whether your plan includes snapshots, and keep a second copy somewhere other than the server.
  6. Watch the server. You need to know when the disk fills up, when memory runs out and when a service stops.
  7. Handle email with care. Running your own mail server means managing SPF, DKIM and the reputation of your IP address. A separate email service avoids that work.

These are the first commands from the Ubuntu Server documentation. On the server, refresh the package index and upgrade the installed packages.

bash
sudo apt update
sudo apt upgrade

Still on the server, allow SSH, enable the firewall and check its status.

bash
sudo ufw allow 22
sudo ufw enable
sudo ufw status

On your own computer, create a key pair and copy the public key to the server.

bash
ssh-keygen -t ed25519
ssh-copy-id username@target_machine

Allow SSH before you enable the firewall, or you can lock yourself out of the server.

A managed VPS hands most of this list to the provider for a higher fee. What "managed" covers differs between companies, so read the list of included tasks before you rely on it.

How the cost model differs

Shared hosting spreads the cost of one server and one operations team across many accounts, which keeps the fee low. The fee is flat, and it normally includes the control panel, SSL certificates and server administration.

A VPS is priced by the resources you reserve, so the fee rises as you add CPU cores, memory or storage. The plan price is also only part of what you spend. Add these items when you compare:

  • A control panel licence, if you want one
  • Backup or snapshot storage
  • A managed service plan, or the hours you spend on administration
  • Monitoring and, for some projects, a separate email service

An unmanaged VPS can look close in price to a large shared plan and still cost more once you count those lines.

When to move from shared hosting to a VPS

Move when you can point to a specific limit or requirement. These are sound reasons:

  • Your account reaches its CPU, memory or entry process limits during normal traffic, and you have already added caching and removed heavy plugins.
  • You need software the host does not offer, such as Docker, a specific database or a custom runtime version.
  • You run long-lived processes, for example queue workers, an automation tool or a real-time app.
  • A client or policy requires your data to sit on a server that no other customer has an account on.

Check the cheaper fixes first. A page cache, fewer plugins, optimized images and a current PHP version solve many slow sites. If the site is still slow after that work, ask your host which limit the account reaches. That answer tells you whether a larger shared plan is enough or a VPS makes sense.

When shared hosting is still the right choice

Stay on shared hosting if your site runs on common software such as WordPress or a PHP framework, your traffic fits inside the plan and nobody on your team wants to administer Linux. You get a maintained server, a control panel and support for less money and almost no upkeep.

WaseerHost shared hosting uses cPanel, the LiteSpeed web server and NVMe storage, and it includes free SSL certificates. When a project needs root access or its own resources, the VPS hosting page lists the current plans. If you are changing hosts as part of the move, WaseerHost offers free website migration.

Frequently asked questions

A VPS is better when you need root access, custom software or more resources than a shared plan allows. For a standard business site or blog, shared hosting does the same job with less work, because the host maintains the server. Pick the one that matches what the site needs and the skills you have.

Waqas Ahmed Waseer

Written by

Waqas Ahmed Waseer

Founder & CEO

Founder and CEO of Wasevo LLC, the company that runs WaseerHost. He works on cPanel/WHM servers, WHMCS billing and the Next.js storefront.

Related Articles

Get new guides by email

One short email when we publish something useful. No spam; unsubscribe at any time.

Free SSL · Free migration · 24/7 support

Fast cPanel web hosting

See hosting plans
30-day money-back guarantee

Renews at the same price for the term you choose