When a website is being built, attention goes mostly to design and features, while hosting is often left until the end and settled with the cheapest option. Yet how fast the site opens, how it behaves when traffic grows, whether data can be lost and whether your emails land in spam all depend on the infrastructure. In this article we explain the types of hosting, which projects each one suits and the details to check when choosing, in plain language.
Types of hosting: a short overview
Shared hosting
The resources of one server (processor, memory, disk) are shared among many websites. The provider manages the server, and you manage your website, database and mailboxes through a control panel. It is easy to start with and inexpensive. However, heavy load on another website on the same server can affect yours, and your ability to change server settings is limited.
VPS (virtual private server)
A physical server is divided into virtual parts, and each VPS is guaranteed its own allocated resources. You get full control at the operating system level: you can install the software you need and choose the PHP version, caching and security settings. In return, someone has to be responsible for managing, updating and protecting the server: either an in-house specialist or a partner providing technical support.
Cloud infrastructure
On cloud platforms, resources can be scaled up and down as needed, and servers, databases, file storage and other services are used as separately managed components. This approach suits variable traffic, high availability requirements and complex architectures. At the same time, it calls for more technical expertise and careful cost control: with pay-as-you-go pricing, unused resources quickly push up the bill.
It is also worth noting that for large projects a fully dedicated physical server is another option: all the resources are yours alone, but managing it takes even more responsibility than a VPS.
Comparison
| Criterion | Shared | VPS | Cloud |
|---|---|---|---|
| Resources | Shared with other websites | Dedicated, fixed | Scaled to demand |
| Control | Control panel level | Full, at server level | Full, per service |
| Management effort | Lowest | Medium | Higher |
| Typical use | Small corporate website, landing page | Business website, online store, web application | Platforms, SaaS, variable traffic |
How to choose for your project
- A corporate website of a few pages or a landing page. Well-configured shared hosting from a reliable provider is often enough. The essentials: a current PHP version, SSL, backups and decent technical support.
- An online store, a client area, an active blog. These make many database queries, and consistent performance matters. A managed VPS is usually the better choice.
- A web application or SaaS. If you need queues, scheduled tasks, a separate cache and file storage, consider a VPS or a cloud architecture.
- Short peaks of heavy traffic around a campaign or an event. A solution that lets you add resources temporarily is the better fit.
The general rule is simple: more infrastructure than you need wastes money, and less than you need loses customers. Choosing hosting before you know the website's technology and expected traffic is not advisable.
Do not treat the choice as permanent. As the website grows, the infrastructure can change too: moving from shared hosting to a VPS, and from a VPS to an architecture of several servers, is a normal path of growth. To make that move smooth, the website should be built on standard technologies, its configuration should be documented and the migration should be tested in advance. DNS changes also need planning so that the website and email keep working without interruption during the move.
Backups: "we have them" is not enough
Many providers promise "automatic backups", but the details are what matter:
- What is backed up? Files, the database and mailboxes alike.
- How often? Once a day is normal for an ordinary website but may not be enough for a busy online store.
- Where are backups stored? If the copy sits on the same server, it can be lost when the server fails. Backups must be kept in a separate location.
- How long are they kept? If you discover a problem a few days later, you need to be able to go back to an earlier version.
- Has restoring been tested? There is no guarantee that a backup that has never been restored actually works. The restore process should be tested regularly.
Business email
An email address on your own domain is a sign of credibility, but setting it up properly is technical work. For messages to reach the recipient's inbox, SPF, DKIM and DMARC must be set correctly in the domain's DNS records. These records prove to the receiving server that the message really was sent from your domain.
Another important decision is whether to keep email on the same server as the website. A separate mail service is usually more reliable: when the website has a problem, email keeps working, and the automatic messages the website sends (order confirmations, password resets) do not affect the reputation of your main mail.
SSL and security
An SSL certificate encrypts the connection between the website and the user and makes it possible to work over HTTPS. Today HTTPS is standard for every website: browsers mark sites without it as "not secure", and forms and payment pages should never be used without it. Free certificates with automatic renewal are widely available; what matters is that renewal really works automatically and that certificate expiry is monitored.
Security is about more than SSL. When choosing hosting, also check:
- Whether the server software and PHP version are updated regularly.
- Whether there is a firewall, protection against malicious traffic and limits on login attempts.
- Whether the server's uptime is monitored and who is notified of a problem.
- Whether access to the control panel and the server is protected with two-factor authentication.
Choosing a domain and a provider
Domain and DNS: a small detail with a big impact
A domain is a separate service from hosting and is often held with a separate registrar. That separation is useful: when you change hosting provider, the domain stays where it is and only the DNS records are pointed to the new server. A few rules matter, though:
- The domain should be registered in the company's name, and the login to manage it should stay with the company, not in a contractor's personal account.
- Automatic renewal should be switched on so the domain does not expire, and the contact email should be kept up to date.
- The list of DNS records (website, email, verification records) should be documented so that none is forgotten during a move.
- Handing DNS management to a reliable service can improve both speed and protection against attacks.
Questions to ask a provider
- Where is the server physically located, and how close is it to your audience?
- What exactly are the resource limits (processor, memory, disk, mailbox size)?
- Through which channels and during which hours does technical support work?
- If you need to move to another provider, how can you export your data?
- In whose name is the domain registered, and who holds the login to manage it?
Conclusion
Choosing hosting is not a technical detail; it is a business decision. Reliable shared hosting for a small website, a managed VPS for online stores and web applications, and cloud infrastructure for platforms with variable traffic are usually the right starting points. In every case, check that backups are stored separately, business email is set up correctly, SSL renews automatically and the domain is in your name. If you would like to work out the right infrastructure for your website together, get in touch with TRUE.
