comparison Hosting
Managed vs unmanaged hosting
“Managed” describes which jobs a provider performs, not whether the machine is shared, virtual or dedicated.
What it means
Managed hosting means a provider takes responsibility for specified operational tasks. Unmanaged hosting usually leaves more of those tasks to the customer. The labels do not define a universal checklist. The contract and product documentation determine who patches systems, monitors failures, maintains backups and responds to incidents. Shared responsibility
A VPS may be managed or unmanaged; so can a dedicated machine or a web application platform. Management level is a different axis from server size, physical tenancy and virtualization. Do not compare “managed” with “VPS” as if one excludes the other.
Try it
Example — assign each task. These are two hypothetical contracts; neither is a claim about a particular supplier.
| Task | Example managed plan | Example unmanaged VM |
|---|---|---|
| Patch guest OS | Provider | Customer |
| Update the site's own plugins | Customer | Customer |
| Monitor service availability | Provider alerts; customer checks application | Customer |
| Restore deleted site content | Customer requests provider restore | Customer restores backup |
The lesson is in the gaps. Even the hypothetical managed plan still has customer tasks. Ask who owns every step and what response time is promised. Security responsibility boundaries
Compare the same criteria
| Criterion | Managed service | Unmanaged service |
|---|---|---|
| Platform maintenance | Some patching, monitoring and operational work included | Customer usually operates guest software |
| Access/control | Provider may restrict risky changes | Greater access to system configuration |
| Support | Scope and response commitments can be broader | Often limited to underlying infrastructure |
| Backups | May be included but retention/restore terms vary | Must arrange unless explicitly included |
| Total cost | Fees can cover operational work | Lower sticker price can hide time and risk |
| Best fit | Limited operations capacity or standardized workloads | Special requirements with capable operators |
AWS's responsibility guidance shows why this depends on service type: a VM customer patches the guest OS, while more abstract services move some platform work to the supplier. Responsibilities for content, identity, application security and compliance do not vanish. Service-dependent duties
What to ask before paying
Read the plan, not just the marketing label. Does “managed” cover the operating system, web server, runtime, databases, CMS plugins, mail, TLS renewal, malware cleanup and restoring from backups? Is monitoring merely an alert, or does it include incident response? Can you export content and configuration? What happens when the application breaks at night?
For an unmanaged VM, verify that you can safely maintain access, install updates, rotate credentials, restrict network exposure, make backups and recover after a failed change. The freedom to administer is also an obligation. Instance security
In practice
Write a small responsibility matrix before choosing a plan. Put an owner next to operating-system updates, app updates, data backups, restore tests, DNS, TLS, monitoring and security incidents. If any row has no owner, the plan is not operationally complete. Hosting selection procedure
Common mistake: interpreting the word “managed” as an unlimited warranty. It rarely removes the need to safeguard domain credentials, application data or deployment changes.
Sources & model boundaries
Primary references used for this explanation. The example above is illustrative; it is not a live check.
- Amazon EC2 — Security
Security in the cloud responsibilities. Customers manage guest OS, credentials, updates and exposed networking on self-managed VM services.
Checked .
- Amazon Lightsail — Instances FAQ
What is a Lightsail instance?. A VPS is a virtual server with a plan-defined virtual resource bundle, not dedicated hardware.
Checked .