A website is just files and code sitting on a computer that is always on and always connected to the internet. That computer is a host. Choosing one shapes how fast your site feels, how much traffic it survives, and how much you pay. This guide translates the jargon into decisions you can actually make.
Shared, VPS, and cloud
Hosting comes in tiers that trade cost against control:
- Shared hosting puts many sites on one server. It is inexpensive and simple, ideal for small sites and early projects, but you share resources with neighbours — a busy site next door can slow yours.
- VPS (virtual private server) carves a physical server into isolated virtual machines. You get guaranteed resources and root control at a moderate price, at the cost of managing more yourself.
- Cloud hosting spreads a site across a pool of servers that scale on demand. It handles traffic spikes gracefully and you pay for what you use, but it rewards people who understand the platform.
Most projects start on shared or managed hosting and graduate to VPS or cloud when traffic or complexity demands it. There is no prize for over-provisioning early.
The old question: Linux or Windows?
Servers historically ran either Linux or Windows, and the choice used to matter a great deal. Today it mostly comes down to your stack. Choose Linux — the default for the overwhelming majority of the web — for PHP, Python, Ruby, Node, and most open-source software. Choose Windows only if you specifically need Microsoft technologies such as ASP.NET or MSSQL. For a typical content site, Linux hosting is faster, cheaper, and better supported.
What actually matters in a host
Marketing pages shout about unlimited everything; the things that matter are quieter. Look for genuine uptime (99.9% or better), fast storage (SSD or NVMe), a data-centre location near your audience, straightforward backups, and responsive support. A host that makes it easy to restore yesterday's site after a mistake is worth more than one that advertises a slightly bigger number.
HTTPS is non-negotiable
Every site should be served over HTTPS, and there is no longer any excuse not to: Let's Encrypt issues trusted certificates for free and most hosts automate the whole process. HTTPS protects visitors, is a ranking signal, and unlocks modern browser features. If a host makes TLS difficult, choose a different host.
Performance lives closer to the user
Even a good server benefits from a content delivery network (CDN) — a global cache that serves your static files from a location near each visitor. Pairing a modest host with a CDN often beats an expensive host alone, especially for an international audience. Combined with sensible caching and compressed assets, it is the cheapest performance win available.
Security is shared responsibility
Hosts secure the infrastructure; you secure your site. Keep software updated, use strong credentials, take backups you have actually tested, and understand the common web risks catalogued by the OWASP project. A hosting plan is only as safe as the habits around it.
Next steps
Hosting and addressing go hand in hand — once a site has a home, it needs a name. Continue with Domain Names and Registration, or step back to Web Development to see what you are actually hosting.
Managed hosting: paying for peace of mind
Between raw servers and simple shared plans sits managed hosting, where the provider handles updates, security, backups, and performance tuning for a specific type of site. For a business without an engineer on staff, this is often the wisest money spent: it converts a class of problems that used to arrive at 2 a.m. into someone else's job. The trade is cost and a degree of control, but for most owners whose expertise is their business rather than server administration, managed hosting is not an indulgence — it is a rational division of labour.