Hosting Guide

What Managed Hosting Actually Means

Managed hosting is not a product tier — it is a description of which operational responsibilities the host assumes. What is managed, and what remains with the user, varies significantly across products that all call themselves managed.

Overview

'Managed hosting' appears on shared hosting plans, managed WordPress platforms, managed cloud services, and dedicated server packages. The word managed is doing very different work in each case. A managed shared hosting plan typically means the server infrastructure is managed — the user doesn't touch the OS. A fully managed WordPress platform means WordPress core, plugins, security, and backups are also managed. Understanding what is managed — specifically — is what makes the label meaningful.

How to think about it

Hosting operations exist at distinct layers. Infrastructure layer: the physical hardware, network, and hypervisor. Server layer: the operating system, web server, PHP, and system software. Application layer: WordPress core, plugins, themes, and database. Content layer: the site's content and user data.

Every hosting product manages the infrastructure layer — no consumer hosting product asks the user to maintain the physical hardware. What varies is how far up the stack the managed scope extends. Some products manage only the infrastructure. Others extend to the server layer. The most comprehensive extend to the application layer.

A product's managed scope determines what the user doesn't have to do — and what they can't control. The two are inseparable: management requires predictability, predictability requires constraints, constraints mean reduced configuration freedom at that layer.

How it works

Infrastructure management (all hosting): hardware maintenance, network operations, datacenter management, hypervisor updates. The user never touches this. It is the baseline that all hosting provides.

Server management (mid-tier and above): OS security patches, web server updates, PHP version management, system software maintenance, basic security hardening. Shared hosting typically includes this. VPS typically doesn't unless explicitly managed.

Application management (managed WordPress, some managed cloud): WordPress core updates, plugin updates, security scanning, managed caching, staging environments, and in some cases automated backup and restore. This is what distinguishes fully managed WordPress platforms from shared WordPress hosting.

Where it breaks

The managed scope ends at a specific layer — everything above it is user-owned. The failure occurs when the user assumes management extends further than it does. A 'managed WordPress host' that manages the server layer but not the application layer leaves WordPress updates to the user. If those updates don't happen, the managed infrastructure sits under an unmanaged, potentially vulnerable application.

Managed scope also creates problems when user requirements conflict with platform management. A plugin that implements its own caching may be blocked because it conflicts with the platform's managed caching. A deployment workflow that requires direct database access may not be supported because the database is managed. The restriction is a feature of management, not a bug — but it can be a feature that conflicts with requirements.

In context

Budget shared hosting: infrastructure managed, server managed at a basic level, application entirely user-owned. The 'managed' label refers to infrastructure and basic server operations.

Managed WordPress (WP Engine, Kinsta): infrastructure, server, and WordPress application layer managed. Updates, security, backups, and performance optimization are platform responsibilities. The user manages content and plugin selection within the platform's constraints.

Managed cloud (Cloudways): infrastructure and server layer managed, application layer user-owned. The user gets a maintained server without server administration; WordPress operations remain their responsibility.