"Managed hosting" sounds like someone else handles everything. Then your developer pushes code on Friday, something breaks, and support says that is outside scope. Welcome to the gap between marketing and reality.
Managed hosting is valuable when you know what is in the box. Here is what it usually includes, what it often excludes, and how to read a proposal without assuming unlimited babysitting.
What "managed" typically covers
Definitions vary by provider and plan tier. On a well-run Canadian managed VPS or managed WordPress plan, you generally get:
- Server operations: OS patching, security updates on the stack the host controls, firewall baselines, monitoring for uptime and resource alerts
- Backups: Scheduled backups with documented retention and a restore process (ask if restores are included or billable)
- SSL: Certificate issuance and renewal on managed endpoints
- Support for infrastructure: "MySQL will not start," "disk is full," "site returns 502 at the server level"
- Migration assistance: Often included or available as a project, especially on onboarding
The word managed refers to the server and platform layer. Not your entire digital life.
What managed hosting usually does not cover
Read the fine print. Common exclusions:
- Application bugs: Your custom PHP, plugin conflicts, theme errors, bad deploys
- WordPress plugin updates: Some plans include it; many do not beyond core OS patches
- Content changes: Editing pages, uploading images, SEO copy
- Third-party services: DNS at Cloudflare, email at Google, payment gateways, CRM integrations
- Unlimited custom development: Building new features is a project, not a support ticket
Expecting your host to debug WooCommerce checkout logic because you pay for managed hosting leads to frustration on both sides. Know the boundary up front.
Managed vs unmanaged in one sentence
Unmanaged VPS: you get root, you patch, you monitor, you fix services. Cheaper, more control, more responsibility.
Managed hosting: the provider runs the platform; you run the app (with varying degrees of help). We compared the contractor angle in managed hosting vs hiring a DevOps contractor.
Questions to ask before you buy
- What exactly is patched automatically, and on what schedule?
- Who restores backups, and how fast is RTO/RPO documented?
- Is support 24/7 for outages, or business hours for "best effort"?
- Are WordPress/plugin updates included or billable?
- What monitoring do you get, and who gets alerted?
- Where is data stored (Canadian regions if that matters to you)?
- What is explicitly out of scope in writing?
Good providers answer plainly. Vague answers mean assume exclusions.
SLA vs actual support experience
Uptime SLA is one line on a page. Support quality is what you feel at 9 PM when checkout is down. Read our SLA without the marketing gloss piece, then ask for real escalation paths and recent incident examples.
Managed should mean someone competent answers when the server layer fails. It does not always mean someone holds your hand through every plugin update.
When managed is worth paying for
Canadian businesses without in-house ops, agencies hosting client sites, accounting firms on RDS, and anyone who cannot afford to learn Linux at 2 AM. You are buying time and sleep.
When you have a strong dev team that wants root, CI/CD, and custom stacks, unmanaged or hybrid often fits better.
Red flags in "fully managed" sales copy
- No written scope of support
- "We monitor 24/7" with no mention of who acts on alerts
- Backups mentioned without restore testing or retention numbers
- Everything included until the first ticket gets declined
- Same price as unmanaged with no explanation of what labor you are paying for
Bottom line
Managed hosting is platform operations with defined boundaries. It is not unlimited application support. Clarify scope before migration, put plugin and content ownership in writing, and match the plan to how much ops work your team can actually carry.
Shopping managed plans in Canada? Talk with Swift Host. We will spell out what we manage, what stays yours, and what tier fits without the fuzzy brochure language.
