Skip to main content

Shared vs VPS vs Dedicated Hosting: What Each Is and Which to Choose

In this article

Shared hosting is one server divided between hundreds of customer accounts. It is cheap, it is fine for a static brochure site or a small PHP site, and it cannot properly run a Django application. A VPS (virtual private server) is your own slice of a server with its own operating system. It is the right answer for almost every business website and online shop. A dedicated server is a whole physical machine, worth paying for only when you have heavy, steady load or a contract that demands physical isolation.

There is a fourth option the old three-way comparison leaves out: a managed platform such as Heroku, Render or Fly.io. You hand over code and the platform runs the servers. It costs more per unit of computing than a VPS and gives you less control, in exchange for someone else doing the patching, backups and scaling.

For a hand-coded Django site our default is a modest VPS in a UK or EU region. The default becomes a managed platform when nobody on the client's side wants to think about servers. The rest of this guide explains what each option actually is, what a Django site needs from its host, and how to pick.

What each option actually is

Shared hosting

The host installs one operating system, one web server and one database server on a machine, then sells accounts on it through a control panel such as cPanel. Every account shares the processor, memory, disk and usually the IP address. The host chooses the software, which in practice means PHP and MySQL, and you cannot install anything at system level or keep a program running in the background. If a neighbouring account gets busy or gets hacked, you feel it.

It suits a site that is mostly static pages, and it is where most WordPress sites live. That is one reason the WordPress versus Django comparison ends up being a hosting comparison too.

VPS

A hypervisor such as KVM splits one physical server into several virtual machines, each with its own operating system, kernel, firewall and root login. Your memory and disk are reserved; the processor cores are usually shared with other virtual machines on the box but with a fair share enforced. You choose the operating system (almost always Ubuntu or Debian for Django) and install exactly the software you need. When you outgrow it, you resize to a bigger plan with a reboot.

Hetzner, DigitalOcean, Linode, Vultr and AWS all sell these; "cloud server" and "droplet" are marketing names for the same thing with snapshots and an API added. The catch is that the operating system is now yours to patch and secure.

Dedicated server

You rent an entire physical machine. Nobody else's traffic touches your processor or disks, and you can use every core. The price is paid in flexibility: provisioning takes hours or days rather than seconds, and scaling means ordering a second machine. Hardware failure is your problem unless you have paid for redundant disks and a spare. A dedicated server earns its keep for sustained heavy computation or large databases that want a lot of memory. The other case is a client contract that requires data to sit on hardware shared with nobody.

Managed platform

You push code, or a Docker container image, and the platform builds it and runs it. It puts TLS in front of it and attaches a managed PostgreSQL database with its own backups. Scaling is a slider. You never log into a server, which also means you cannot tune one. Each extra component (a worker, a cache, a bigger database) is a separate line on the bill. For a site with nobody technical looking after it, that premium buys a lot of sleep.

The four options side by side

AttributeSharedVPSDedicatedManaged platform
Who patches the operating systemThe hostYouYouThe platform
Root accessNoYesYesNo
Isolation from other customersWeakVirtual machinePhysicalContainer
Runs Django properly (Gunicorn, PostgreSQL, background jobs)RarelyYesYesYes
How you scaleMove hostResize, then add serversOrder hardwareSlider
Cost patternLowest, fixedLow, fixed per planHigh, fixedMedium, per component
Good forStatic sites, hobby PHPMost business sites and shopsHeavy steady load, strict isolationSites with no one technical in-house

What a Django site needs from its host

Django does not run the way a PHP site does, where the web server executes a script per request. A Django site is a long-running Python process, and everything else follows from that.

  1. A recent Python (3.12 or newer in 2026) and the ability to install packages for it.
  2. An application server, usually Gunicorn for WSGI or Uvicorn for ASGI, kept alive by systemd so it restarts after a crash or a reboot.
  3. A reverse proxy in front of it, Nginx or Caddy, to terminate TLS, serve static files and buffer slow clients.
  4. PostgreSQL, either on the same machine for small sites or as a managed database once uptime matters.
  5. Usually Redis, for caching and for queuing background work such as sending emails and generating PDFs.
  6. A way to run that background work and scheduled tasks: a worker process and a cron or systemd timer.
  7. Somewhere for uploaded files that survives a rebuild, which on a managed platform means object storage rather than local disk.
  8. Environment variables for secrets, and a deploy routine that reloads Gunicorn gracefully rather than dropping requests.

Shared hosting fails on the first, second and sixth points. That is why a Django site "on shared hosting" is almost always a site that has been squeezed onto one via a hack that breaks at the first update. A VPS, a dedicated server or a managed platform all satisfy the list.

Sizing is less dramatic than hosting adverts suggest. A hand-coded business website with quote forms, a news page and a few thousand visits a day runs comfortably on a one-core VPS with two gigabytes of memory, PostgreSQL included. A shop processing a few hundred orders a day is happy on two cores and four gigabytes. Gunicorn's own documentation suggests two workers per core plus one, and each worker on a typical site uses somewhere around a hundred megabytes. That is why memory rather than processor is the number to watch.

Where the server should be

Two things decide the region. The first is latency. Every request from a visitor in Leeds to a server in Virginia crosses the Atlantic twice before the first byte arrives, and time to first byte feeds straight into rankings. The second is data residency. Customer records held under UK GDPR are simplest to account for when they stay in the UK or the EU, where the adequacy arrangements are settled. Every provider named above offers a UK or EU region. If a shop ships worldwide, keep the server there and put a CDN in front of the static assets rather than moving the database abroad.

Who looks after it

This is the question that should decide between a VPS and a managed platform, and it is the one people skip. A VPS arrives as a bare operating system. Someone has to switch on automatic security updates, configure the firewall, install and renew the TLS certificate, and schedule and test backups. Someone has to watch the disk filling with logs and read the alert when the site goes down at two in the morning. All of it is routine for a developer who does it every week. It is not routine for a business owner, and a VPS nobody maintains is less safe than shared hosting after a year.

So the honest decision tree is: if a developer or a maintenance arrangement will look after the server, a VPS gives the most for the money. If not, pay the managed platform's premium. Either way, insist that the account is in your company's name, not the developer's, so a change of supplier is a change of login rather than a migration. On our projects the hosting and the domain are always registered to the client.

Which to choose

  • Static site with no forms or logins. Shared hosting or a static host is fine; nothing is running, so there is nothing to isolate.
  • Hand-coded business site with forms, a small admin area and a blog. A small VPS, or a managed platform if no one will maintain it.
  • Online shop. A VPS with a managed PostgreSQL database, or a managed platform. The database backups matter more than the server here, because the server can be rebuilt from code in an hour and the order history cannot.
  • Platform with many logged-in users. Start on one well-sized VPS with the database separate, so that a second application server and a load balancer can be added later without a rebuild.
  • Dedicated server. Only when measured load, memory needs or a contract says so. Buying one "for growth" is paying for cores that sit idle.

Questions people ask

Is VPS hosting better than shared hosting?

For anything beyond static pages, yes. You get reserved memory, your own operating system and the freedom to run the software your site needs. The trade is that the operating system becomes your responsibility to patch.

Is cloud hosting the same as a VPS?

Usually. A "cloud server" from a large provider is a VPS with extras such as snapshots and an API for creating more. True elasticity, where servers appear and vanish with demand, needs an application built for it and is rarely worth the complexity for a single business site.

Can you run Django on shared hosting?

A few shared hosts offer Python through Passenger or a similar bridge, and it works until you need a background worker, a specific Python version or a system package. Treat it as a demo environment, not a home for a business site.

Does an online shop need a dedicated server?

No. A shop taking hundreds of orders a day is well within a two-core VPS. What a shop needs is a database that is backed up and restorable, a payment provider such as Stripe that holds the card data, and monitoring. None of those come from the size of the machine.

How we handle this on our own builds

We specify the hosting at the quote stage, not after launch, because the answer changes how the site is built. A managed platform means uploads go to object storage from day one, and a VPS means the deploy script and the backup job are part of the project. The default is the smallest server that leaves headroom, in a UK or EU region, in the client's own account. If you are weighing a plan for a site you already own, start by writing down who will patch it. That one answer usually settles the rest.