← All Services

HOSTING / DECIDE WHO DOES THE WORK

Managed Hosting & Support Explained

Managed hosting describes responsibility, not a particular server size. It can apply to a website, VPS, database or dedicated server. The useful question is: exactly what work is someone agreeing to do?

What You Are Buying

Possible tasks include patching, monitoring, backups, restores, security configuration and incident response. Some plans manage only the underlying operating system; others include an application. A support desk answering questions is not necessarily monitoring your site or fixing it without a ticket. “Fully managed” has no single scope that fits every contract.

When You Would Use It

  • Assign ongoing maintenance when you lack time or specialist staff.
  • Set a response process for failures that matter to your organization.
  • Reduce repetitive operational work while keeping clear ownership of accounts and data.

What You Still Manage

Name an owner for every task, including failed updates and after-hours incidents. Protect access with individual accounts and least privilege. You remain responsible for business decisions and for checking that agreed backups and recovery work are actually happening.

Privacy Considerations

Support staff may need privileged access to solve a problem. Ask how that access is approved, limited, logged and removed, and whether subcontractors can receive data. A ticket can contain sensitive screenshots or log exports. Redact secrets and personal information before sending it, and agree on ticket and diagnostic-file retention.

Compare provider access, logs, retention and encryption →

Consumption, Allowances & “Unlimited”

Support can be per server, per user, per incident, hourly or retainer-based. “Unlimited tickets” may mean unlimited requests to the desk—not unlimited engineering hours, project work or instant resolution. Response time is a first reply; resolution time is when the problem is fixed. SLA credits are generally contractual remedies, not a guarantee that nothing fails.

Read the plan’s resource limits and acceptable-use policy together. Ask what happens at the threshold: an extra charge, reduced speed, rejected requests or suspension. Understand the billing language →

Questions to Ask Before Buying

  • Who handles OS, application and plugin updates—and a failed update?
  • Is the commitment a response time or a restoration target?
  • Are emergencies, migrations, malware cleanup and restores included?
  • Do I retain administrator access and exportable backups when the contract ends?

The takeaway: A task-by-task responsibility list is more useful than the word “managed.”

Build a complete buying checklist →