OOmnistu

Blog / Web Fundamentals

Web Fundamentals

Web hosting types explained: shared, VPS, dedicated or cloud?

Shared, VPS, dedicated and cloud hosting differ in who shares the server and who manages it. What each type fits, what none of them can fix, and a practical check for a small site.

OOmnistu
Reviewed 2026-11-20 · 5 min read

Every website lives on a server somewhere, and the hosting plan you pick decides who else shares that server, who manages it, and how much control you get. This guide explains the four hosting types most providers offer - shared, VPS, dedicated and cloud - what each one fits, what none of them can fix, and a practical check for a small site. It is grounded in AWS's web hosting explainer, with plan details left to providers' current pages.

What hosting actually is

A web host stores your site's files and serves them to visitors over the internet. Beyond storage, plans differ along two axes: how much of the server's capacity is reserved for you, and how much of the setup and maintenance you do yourself. The four common types are different points on those axes, not different products.

Shared hosting

With shared hosting, your site sits on one server alongside many other customers' sites - AWS notes that a provider can run hundreds of sites on the same machine. You share CPU, memory and disk; you cannot see other customers' files, and they cannot see yours. Shared plans are typically the cheapest option and the easiest to start with, which makes them the common first home for personal sites, blogs and new small businesses.

The trade-off: you have little control over server configuration, and because capacity is shared, another site's traffic spike can slow yours down. Costs can also rise as your traffic grows beyond what the plan assumes.

VPS hosting

A virtual private server (VPS) partitions one physical server into separate virtual servers. You get your own operating system and far more control over the environment. Plans advertise an allocation of memory and processing power, though whether CPU time is dedicated or burstable depends on the plan's terms, so check before assuming a fixed allocation - AWS describes the fit as medium-sized businesses with growing traffic or sites that need custom server software. The trade-off is responsibility: an unmanaged VPS expects you to handle configuration, updates and security, so providers also sell managed VPS plans where they do that work for a higher fee.

Dedicated hosting

Dedicated hosting leases you an entire physical server. Nothing is shared, so you get full control over hardware and configuration and no neighbor effects. It suits large or complex applications with heavy processing needs - and it is expensive to lease and maintain, and generally expects in-house technical capability. For most small sites it is more than the workload justifies.

Cloud hosting

Cloud hosting spreads your site across a cluster of servers rather than one machine. AWS describes how providers use resource sharing and replication across servers to improve availability, and how many cloud plans can scale resources with demand on pay-for-what-you-use pricing. Those are plan features, not automatic guarantees: the scaling range, failover behavior and billing model vary by provider and plan, so check what a specific plan actually includes. Many modern platforms also blur the lines: managed hosting and website builders often bundle a CDN, certificates and backups, so check what a plan already includes before paying twice.

What hosting cannot fix

A bigger plan does not repair a slow application. If pages are slow because of heavy database queries or uncached dynamic work, the answer is in the application, not the server size - our TTFB guide covers measuring server response time, and our HTTP caching guide covers what can be cached. Similarly, hosting is not a CDN: a host serves your site from its servers, while a CDN caches copies near visitors to cut distance, as our CDN explainer describes. The two solve different problems and often work together.

A practical check for a small site

FAQ

Does a new small website need a VPS?

Usually not. A new site with modest traffic typically fits shared or entry-level managed hosting. A VPS starts to make sense when you need custom server software, a defined resource allocation, or more control than shared plans allow - and when someone can administer it.

Is cloud hosting the same as a CDN?

No. Cloud hosting runs your site across a cluster of servers that scale with demand. A CDN caches copies of your content on servers near your visitors to cut latency. Many sites use both: hosting serves the origin, the CDN serves the cacheable parts.

Can I switch hosting types later?

Yes, migrations are routine - many sites start on shared hosting and move to a VPS or cloud plan as they grow. Plan the move: providers' migration tools and support vary, and DNS changes take time to propagate.

Does server location matter?

It can. Latency grows with distance, so a server near most of your visitors responds faster for uncached requests. A CDN reduces that penalty for cached content, which is why location matters less once static assets are served from the edge.