Shared, managed, or VPS: who does the work?
The useful distinction is not simply speed or price. It is which resources you receive and which responsibilities stay with you.
Document research and editorial guidance. No hands-on hosting tests were performed for this guide.
Start with responsibilities
Choosing hosting means assigning work. Someone must maintain the operating system, configure the web server, update the application, recover data and investigate failures. A product name does not tell you where every responsibility sits. Ask for the actual scope of service and write down which tasks belong to you.
The AWS shared-responsibility documentation offers a useful example of this principle: infrastructure responsibilities and customer responsibilities are distinct, and the customer’s work depends on the service selected. That document describes AWS, not a universal contract for hosting companies. Apply the question—who maintains what?—to each provider’s own terms.
Shared hosting
Shared hosting usually packages website space and tools on infrastructure serving multiple customers. It can be a practical starting point for a modest site using a supported runtime. You generally operate within the account features and limits the provider exposes. Check process limits, memory limits, database capacity, scheduled tasks, and the runtimes available to your account.
The tradeoff is control. If your application needs a persistent worker, a custom system package or a specific network service, ask whether it is supported before buying. Disk space alone does not establish application compatibility. Do not infer that “unlimited” marketing means unlimited CPU time, concurrent requests or database resources.
Virtual private servers
A VPS gives you a virtual machine environment rather than just a website account. The exact degree of resource isolation and the allocation of CPU still need checking. Root access can make custom deployment possible, but it also introduces operational work. On an unmanaged service, you should expect to arrange patching, access security, monitoring and recovery unless the contract says otherwise.
A small VPS can be appropriate for a developer who needs control and has time to maintain it. It is not automatically an upgrade for a business owner who wants someone else to fix application problems. Include your own maintenance time and backup arrangements in the comparison.
Managed is a scope, not a benchmark
“Managed” can describe very different things: an operating system, a control panel, a WordPress installation, or a broader application service. Ask whether the provider handles application updates, plugin conflicts, malware cleanup, incident response and restores. Ask when support ends at the infrastructure boundary. Get the answer for the exact plan.
Management does not eliminate the need for your own change process. You may still control content, user access, custom code and integrations. A service can be well managed yet unsuitable for a particular application’s deployment model.
A practical decision
Write down three requirements before looking at prices: the software that must run, the tasks you can maintain, and the amount of data or downtime you can tolerate losing. Then compare products in the same category. If two offers assign very different work to you, their prices are not measuring the same service. Use the provider directory as a research worksheet, not a universal ranking.
Sources
Related reading
- SSD or NVMe? Look beyond the storage label.
- WordPress or a custom app? Start with the runtime.
- A backup is only useful if you can restore it.
- The real cost of hosting starts at renewal.
Reader discussion
No published contributions yet. Thoughtful questions and useful answers are welcome.