hostinglinks.
PRACTICAL TECH, EXPLAINED

HOSTING MODEL

Shared hosting vs VPS vs managed hosting

Choose who will operate the website before comparing processor counts. A server you cannot maintain is a poor fit even when its specification looks generous.

Editorial update: 24 October 2026. These are decision examples, not performance tests or provider rankings.

“Managed” describes a service, not a server size

Shared hosting places customers on shared infrastructure, usually with a control panel and limited server access. A VPS gives you a virtual server with more control. Management can be added to a VPS, and shared hosting can include managed WordPress services. The labels overlap, so ask what work the contract actually covers.

Typical starting points; verify the actual plan
ResponsibilityShared hostingUnmanaged VPSManaged service
Operating system and web serverProviderYouCheck scope
Application and plugin updatesUsually youYouMay be included
Backup retention and restore testingCheck plan; verify recovery yourselfYou unless separately purchasedCheck retention, restore support and exclusions
Custom background servicesOften restrictedYou configure themDepends on platform support
Outage investigationProvider for platform; you for applicationYou, with provider infrastructure supportDepends on support agreement

Scenario 1: a small WordPress information site

If you need standard PHP, a database, modest storage and a few mailboxes, suitable shared hosting may cover the job. Check renewal pricing, backup access and restore instructions. You still need to maintain WordPress, plugins and user accounts unless that is explicitly included.

Move to a more capable service when measurements show a resource limit or you need a feature the plan cannot provide. A low visitor count does not guarantee a light workload: a badly configured plugin can consume resources without much traffic.

Scenario 2: a custom app with a background worker

Write down the runtime, database, scheduled jobs, persistent storage and background processes first. A conventional shared plan may not support them. A VPS can, but you must deploy the app, secure access, patch software, manage certificates and recover after a failure.

A managed application platform can reduce server work, but confirm support for your runtime, job duration, database connections and file persistence. A successful deployment is not proof that an uploaded file survives the next deployment.

Scenario 3: a business that needs someone to call

If a broken form costs enquiries and nobody can investigate it, support scope may matter more than disk space. Ask whether the provider investigates application faults, restores backups and helps after a compromised plugin. “Server online” support is different from restoring a working checkout or contact form.

Count the operating time

As a hypothetical example, a £10 monthly VPS plus one hour of maintenance valued at £30 costs £40 a month before backups and incident work. A suitable £25 managed plan could be cheaper overall. If you enjoy administration and already have the skills, the comparison changes. Use your own time and quotes.

Ask for a recovery plan before buying

  1. Identify who receives outage and renewal alerts.
  2. Confirm where backups live, how long they last and how to download them.
  3. Ask how to restore both files and databases, and whether a restore costs extra.
  4. Check how domains and email would be moved independently.
  5. Record how to export the application if you leave.

If those answers are unclear, resolve them before moving a working website. The useful question is not which hosting category is best, but which plan supports the workload and assigns every essential task to someone.