Web Hosting Explained: Shared, VPS, Cloud and Managed

By Grocito13 October 2026

Web hosting is the service that stores your website's files and data on a computer that is always connected to the internet, so visitors can load it. The main types are shared, VPS, dedicated, cloud, managed or platform, and static or edge hosting. Choose by traffic, the skills of your team and how much responsibility you want to carry, not by the cheapest plan.

Key takeaways

Hosting decides speed, uptime, security and how much maintenance lands on you.
Shared hosting is simple and economical for small sites. VPS and cloud give control and room to grow. Managed and platform hosting trade control for less work.
Static and edge hosting can be very fast and secure for sites that do not need a database on every request.
Ask about backups, support, security and exit options before you sign up.
Match hosting to the team who will run it. A powerful server nobody maintains is a liability.

What hosting does

When someone types your address, their browser asks a server for your pages. The server runs software, such as a web server, a database and your application, and sends back the result. Hosting is the rented space, computing power, network connection and often the management that make this happen reliably. Your domain name points visitors to that server, which we cover in our domain name strategy guide.

The main types of hosting

Shared hosting

Many websites share one server and its resources. It is easy to start, usually includes a control panel, and suits small brochure sites and simple blogs. The trade-offs are limited control and the risk that a busy or poorly secured neighbour slows you down, depending on how the provider isolates accounts.

VPS hosting

A virtual private server is a slice of a physical machine with dedicated amounts of memory and processing, and its own operating system. You get more control and predictable performance, but someone must configure, secure and update it. It suits growing sites, custom applications and teams with technical skills.

Dedicated server

You rent a whole physical machine. It gives maximum control and consistent performance but demands the most administration, and scaling means changing hardware. It is now less common for small businesses, though some regulated or specialised workloads still use it.

Cloud hosting

Your site runs on pooled infrastructure that can be resized, duplicated or spread across locations. It suits variable traffic and applications that need resilience. The flexibility is real, but so is the complexity, and costs can drift if nobody watches usage. See our guide to cloud cost optimisation for how to keep that under control.

Managed or platform hosting

The provider handles servers, updates, caching and often backups for a specific stack, such as WordPress or a modern JavaScript framework. You pay for convenience and expertise. The trade-off is less low-level control and some dependence on that platform's conventions.

Static and edge hosting

Pages are built in advance and served from many locations close to visitors, often through a content delivery network. It is quick, relatively easy to secure and scales well for content sites, documentation and marketing pages. Dynamic features then come from separate services or APIs. This pairs naturally with headless CMS setups.

Matching hosting to your situation

Think about four things.

Traffic pattern: Steady and small, or spiky because of campaigns and seasons?
Application type: A static brochure site, a content-managed site, a store, or a custom web application with a database?
Team skills: Do you have someone who can manage servers, or do you need the provider to do it?
Risk tolerance: What does an hour of downtime cost your business in practice?

Choose by scenario

A small local business brochure site, rarely changed: Shared or static hosting.
A content site with an editor team and moderate traffic: Managed hosting for your CMS, or static hosting with a headless CMS.
An online store with seasonal peaks: Managed or cloud hosting with caching, tested ahead of campaigns.
A custom web application with a database and integrations: VPS or cloud, ideally with automated deployment and monitoring.
A marketing site that must stay up under sudden traffic: Static or edge hosting with a content delivery network.
A business with no technical staff: Managed hosting with clear support commitments.
A regulated or sensitive workload: Talk to a qualified adviser about where data must live, then choose a provider and region accordingly.

Questions to ask any hosting provider

Write the answers down and compare.

Uptime and support

What uptime do you commit to in writing, and what remedy applies if you miss it?
Is support available by chat, phone or email, and at what hours? Who answers technical questions, not just billing ones?
How are outages communicated?

Backups

How often are backups taken, how long are they kept and where are they stored?
Can I restore a single file or database without rebuilding everything? Has the restore process been tested?
Are backups stored separately from the main server? Our backup and disaster recovery guide goes deeper.

Security

Are operating system and server software patched, and by whom?
Is there a firewall, malware scanning and protection against brute-force login attempts?
Is HTTPS included, and are certificates renewed automatically?
How is access controlled, and is two-step verification available on the account?

Limits and growth

What happens if traffic spikes: throttling, extra charges or an outage?
Can I upgrade without moving the site?

Performance factors

Hosting speed is rarely only about the server.

Location: A server far from your visitors adds delay. Pick a region close to the majority of your audience.
Content delivery network: A CDN stores copies of static files near visitors, reducing load times and server work.
Caching: Storing prepared pages or database results avoids repeated work. Configure it carefully so logged-in or personalised content is not shown to the wrong person.
Software efficiency: Heavy plugins, large images and slow database queries cause more slowness than people expect. Fixing these is often cheaper than buying a bigger server. See Core Web Vitals.

Scaling, lock-in and migration

Scaling

Vertical scaling means a bigger server. Horizontal scaling means more servers sharing the load, which needs your application to be designed for it, for example by keeping sessions and uploaded files outside a single machine.

Lock-in

Convenience features such as proprietary build tools, special databases or platform-specific services make leaving harder. That is not always a reason to avoid them, but know where the dependency sits. Keep your code in version control, your content exportable, and your DNS under your own control.

Migration

Moving hosts is manageable with a plan: lower DNS time-to-live settings in advance, copy files and data, test the new site on a temporary address, freeze changes briefly, switch DNS, then monitor. Keep the old host running for a while as a fallback. Our cloud migration checklist and DevOps services cover bigger moves.

Common mistakes

Choosing purely on the lowest plan, then discovering backups or support are extras.
Running a server with no one responsible for updates.
Leaving the hosting account in a former employee's or agency's name.
Assuming backups work without ever testing a restore.
Over-buying cloud complexity for a small static site.
Ignoring location and CDN, then blaming the design for slowness.
Having no monitoring, so you learn about outages from customers.

A worked example

Imagine a small training company with a marketing site, a blog and a booking form. It starts on a basic shared plan, which is fine. After a successful campaign the site slows and the booking form times out. The company does not need a giant server. Moving the marketing pages to static hosting with a CDN and the booking function to a small managed application host would separate the quiet part from the busy part, and automated backups with a tested restore would remove the biggest risk.

FAQ

What is the difference between shared hosting and VPS hosting?

Shared hosting puts many sites on one server and manages most of it for you, with limited control. A VPS gives your site its own reserved resources and operating system, with more control and more responsibility. Choose VPS when you need predictable performance or custom software and have someone to manage it.

Is cloud hosting better than shared hosting?

Cloud hosting is better for resilience and variable traffic, but it is not automatically better for every site. A small brochure site may be perfectly served by simple hosting, and cloud adds complexity and cost if nobody manages it.

What is managed hosting?

Managed hosting means the provider looks after server setup, updates, security hardening, caching and often backups for your platform. You focus on content and features. It costs more than basic hosting but saves time and reduces technical risk.

How do I know my website needs better hosting?

Warning signs include frequent downtime, slow response times even after optimising the site, errors during traffic peaks and limits you keep hitting. Measure first, because slow code and heavy images are often the real cause.

Next steps

List your site type, expected traffic, who can maintain servers and how much downtime you can tolerate, then shortlist two providers and ask the questions above. If you would like help choosing or moving, contact us, or see our cloud services.