Managed vs Unmanaged Dedicated Servers: Assign the Work
The difference between managed and unmanaged hosting is the work included in the service agreement. It is not a universal promise that a provider will fix every application problem or that an unmanaged customer receives unrestricted support.
Before comparing fees, make a responsibility matrix for the software you actually use. Mark the owner, scope, response route and evidence for each recurring task.
Build the matrix before choosing a plan
| Task | Question to resolve |
|---|---|
| Hardware and network | Who detects failure, raises a case and replaces components? |
| Operating system | Who applies patches, chooses maintenance windows and handles rollback? |
| Web and database services | Which versions and configurations are supported? |
| Application | Who maintains custom code, plugins and business integrations? |
| Backup and restore | Who checks the job, protects copies and demonstrates restoration? |
| Security incident | Who investigates, revokes access and restores an acceptable service? |
Do not leave an entry as “the host probably handles it”. Have the supplier confirm disputed or missing tasks before accepting the service.
Read the product’s access rules
Some managed services restrict root access or supported software. Others offer administrator access with exclusions. Hetzner’s managed and bare-metal comparison shows one product-specific distinction.
A restriction may be compatible with your application, but check it before migration. If you need an unsupported package or a specific maintenance policy, ask whether a different service is required.
Check what monitoring leads to
An alert, an initial support response and a completed repair are different outcomes. Establish which events are monitored, who receives alerts and what the provider does without asking the customer first.
Liquid Web publishes separate managed and self-managed descriptions. Treat them as examples of scope to investigate, not an endorsement that either model guarantees uptime or compliance.
Compare complete operating cost
Add the staff or contractor work remaining with each plan. Include onboarding, after-hours coverage, migration and excluded incidents. Do not rely on a generic management premium or assume a fixed number of monthly maintenance hours.
The cost checklist helps normalise the quotes. Keep the same backup, recovery and application requirements in both estimates.
Have the intended operator demonstrate the process
Before production handover, verify access, alert delivery, support escalation and restoration in a protected test environment. Use the backup guide to avoid confusing a completed job with a usable recovery process.
Choose the plan whose documented scope leaves a manageable set of duties with your team. Even with extensive management, someone must still own accounts, application changes, business data and the decision to accept recovery results. The handover checklist provides the final acceptance questions.








