Maintenance
Managed Hosting, a VPS or the Cloud: Where Should Your Website Live?
Shared hosting, managed hosting, a VPS and the cloud each suit different sites. Here is what you get and give up with each, the questions that settle the choice, and the hosting mismatches we come across most often.

Most websites end up where they live by accident. Someone picked a hosting plan years ago on price or on a recommendation, the site grew, and now it is either struggling on a plan that was meant for a brochure site or sitting on infrastructure far more complicated and expensive than it needs. The hosting decision affects speed, security, how quickly problems get fixed and what your developers are able to build, so it is worth making deliberately.
Through our hosting, server and DNS management service we look after sites on all of the options below, and none of them is right for everyone. Here is how we match a site to the right kind of home.
The Options in Plain Terms
- Shared hosting: your site sits on a server alongside many others, with fixed limits and very little control. Fine for a small, low-traffic site; the first thing to outgrow.
- Managed hosting: a provider runs the server and the platform for you, often specialised for one system such as WordPress, with caching, backups, staging and updates included.
- A VPS (virtual private server): a slice of a server that is entirely yours, with full root access. You, or whoever you hire, are responsible for everything on it.
- The cloud: AWS, Azure or Google Cloud, where the server is one building block among managed databases, load balancers, storage, queues and autoscaling.
The lines blur at the edges, since many VPS providers offer managed databases and many cloud platforms offer simple virtual machines, but the trade-off underneath is constant: the more control you take, the more responsibility comes with it.
Managed Hosting: When Someone Else's Rules Suit You
For a WordPress marketing site or a modest WooCommerce store, good managed hosting is often the best value overall. Server updates, a tuned PHP stack, page caching, daily backups and one-click staging sites come as standard, and support staff understand the platform.
The cost is control. Expect some or all of these limits:
- Certain plugins blocked, usually caching, backup or security plugins that duplicate the host's own tools.
- A cap on simultaneous PHP processes, which becomes the bottleneck for a busy store or membership site where pages cannot be cached.
- No way to install extra services such as a search engine or a queue worker, and limited control over cron jobs.
- Pricing that rises with visits or storage, which can surprise a growing site.
If your site lives comfortably inside those rules, managed hosting frees you from server work entirely. Our WordPress development projects frequently launch on it.
A VPS: Control and Value, If Someone Looks After It
A VPS from a provider such as DigitalOcean, Hetzner or Linode gives you a dedicated amount of CPU and memory, a predictable monthly cost and the freedom to run anything: a Laravel or Node.js application, background workers, Redis, a search engine, several sites at once. For custom applications with steady traffic it is often the best value there is.
The catch is that an unmanaged VPS is a blank server. Someone has to:
- Apply operating system and software security updates, and know which ones need care.
- Configure the firewall, SSH access, web server, PHP or Node.js and the database properly.
- Set up off-server backups and check that they restore.
- Monitor uptime, disk space and certificate renewals, and respond when an alert fires.
A server control panel such as CloudPanel or Plesk takes some of the effort out of this, but not the responsibility. A VPS that nobody has updated in years is one of the most common starting points for the compromised sites our hacked website cleanup team is asked to fix. It is also a single machine: if it fails, the site is down until it is restored or rebuilt.
The Cloud: When You Need What One Server Cannot Do
AWS, Azure and Google Cloud make sense when the site or application needs things a single server cannot provide well:
- A managed database with automatic failover and point-in-time recovery.
- Several web servers behind a load balancer, scaling with demand.
- Separate production, staging and development environments built from the same definitions.
- Integration with other cloud services, private networks or company sign-in.
- Security and compliance certifications that customers or regulators ask about.
The price is complexity, and a bill that needs watching. A cloud account running everything on one virtual machine gets most of the cost of the cloud and little of the benefit. Our cloud migration team plans moves so that the extra capability is actually used, and our guide to whether you need Kubernetes covers the next step up, which most sites never need.
Questions That Settle the Choice
- What does the site run? A standard WordPress site points one way; a custom application with workers and scheduled jobs points another.
- What does an hour offline cost you? If the honest answer is very little, single-server hosting with good backups is enough. If it is lost orders and staff unable to work, pay for redundancy.
- How does traffic behave? Steady traffic suits a fixed-size server; sharp peaks from campaigns or seasonal sales favour hosting that can scale.
- Who is responsible for the server? If nobody, choose managed hosting or pay someone to manage the VPS. An unmanaged server with no owner is the worst option of all.
- Where must the data be? Contracts or regulations may require a particular country or region.
One more point: keep your business email separate from your web hosting. Hosting email on the same server as the website ties two unrelated services together, so a problem with one becomes a problem with both.
Mismatches We See Often
- A busy online store on shared hosting, hitting process limits every time a newsletter goes out.
- A five-page brochure site on a multi-server cloud setup that costs more each month than the site earns.
- A VPS set up by a developer who has since moved on, running software several major versions out of date.
- A straight copy of an old server into the cloud, now costing more for the same performance.
Each of these is fixable, usually by moving to the option that matches the site rather than the most impressive one. When it is time to move, our article on moving hosting and DNS without downtime sets out the order of work.
If you are not sure your site is in the right place, tell us what it runs, how busy it gets and who looks after it now. We will recommend a home for it, and manage it for you if you would rather not.
Frequently Asked Questions
Is a VPS faster than managed WordPress hosting?
Not automatically. A well-tuned managed host with page caching can outperform a VPS that has been set up with default settings. A properly configured VPS gives you more dedicated resources and freedom to add tools such as Redis or a search engine, which matters most for stores and applications where many pages cannot be cached.
When is it time to move off shared hosting?
Common signs are slow page loads at busy times, errors during campaigns or sales, resource limit warnings from the host, needing software the host will not install, or running an online store where speed and reliability affect revenue. If two or more of these apply, managed hosting or a VPS is usually the next step.
Can one VPS host several of our websites?
Yes, and it is common. Each site gets its own system user, web server configuration and database so a problem in one does not spread to the others. The trade-off is that all sites share the same resources and the same single point of failure, so a busy or important site may deserve a server of its own.
Do we need a developer to manage a VPS for us?
You need someone with Linux server experience, whether that is a staff member, a developer or a managed service. The ongoing work is security updates, backups, monitoring, certificate renewals and fixing problems when alerts fire. Without that, a VPS slowly becomes a security and reliability risk, however well it was set up initially.





