Managed hosting
A web hosting service in which the provider handles server administration, software updates, security, backups, and performance optimization on the customer's behalf.
Also known as: managed WordPress hosting, fully managed hosting
Managed hosting is a web hosting service in which the provider handles server administration, software updates, security, backups, and ongoing performance optimization on the customer’s behalf. The customer focuses on their website and content; the provider takes responsibility for the underlying infrastructure.
The opposite is self-managed (or “unmanaged”) hosting, in which the customer is responsible for server administration.
What managed hosting typically includes
Common services bundled into managed hosting:
- Operating system updates and security patches
- Web server configuration (Apache, Nginx, Caddy)
- Database administration (backups, optimization)
- Application updates (e.g., WordPress core, plugins, themes for managed WordPress hosting)
- Caching layers (page cache, object cache, CDN)
- Security monitoring and mitigation (firewalls, malware scans, DDoS protection)
- Daily or hourly backups with restore tools
- Staging environments for testing changes
- Performance monitoring
- Specialized support familiar with the application being hosted
Common managed hosting categories
| Category | Examples | Typical customer |
|---|---|---|
| Managed WordPress hosting | WP Engine, Kinsta, Flywheel, Pressable, Pantheon | WordPress sites of any size |
| Managed application hosting | Heroku, Render, Fly.io, Railway, Platform.sh | Custom apps in Ruby, Node, Python, Go, etc. |
| Managed Magento / Shopify | Shopify Plus, Adobe Commerce Cloud | Ecommerce stores |
| Managed Drupal | Acquia, Pantheon | Enterprise Drupal sites |
| Managed databases | Amazon RDS, PlanetScale, Supabase, Neon | Database operations without DBA work |
| Fully managed cloud | AWS Elastic Beanstalk, Google App Engine | Apps where deployment is automated |
Managed vs unmanaged hosting
| Aspect | Managed hosting | Unmanaged hosting (e.g., VPS) |
|---|---|---|
| Server administration | Provider | Customer |
| Software updates | Provider | Customer |
| Security patching | Provider | Customer |
| Backups | Included, often automated | Customer-configured |
| Performance optimization | Built-in caching, CDN | Customer-configured |
| Cost | Higher | Lower base cost |
| Required technical expertise | Lower | Higher (Linux administration, web server config) |
| Flexibility | Constrained to provider’s stack | Full control |
Managed WordPress hosting specifics
Managed WordPress hosting is the most common managed offering. Typical features:
- Pre-installed and pre-optimized WordPress
- Automatic WordPress core updates
- Plugin update management (varies by provider)
- WordPress-specific caching
- Staging environments
- One-click backups and restores
- Restricted plugin lists (some providers block plugins known to cause performance or security issues)
- Specialized support familiar with WordPress
Managed application hosting (PaaS)
Platform-as-a-Service (PaaS) providers offer managed hosting for custom applications. The customer pushes code (typically via Git); the platform builds and deploys it. Common features:
- Git-based deployment
- Automatic dependency installation
- Built-in databases and add-ons
- Automatic SSL and CDN
- Auto-scaling
- Logs and monitoring
Examples: Heroku, Render, Fly.io, Railway, Platform.sh.
Strengths of managed hosting
- Lower operational burden. No need to manage servers
- Better security defaults. Provider expertise applied to known threats
- Faster recovery. Backups, monitoring, and incident response are part of the service
- Performance. Pre-optimized stacks (caching, CDN) often outperform default self-managed configurations
- Specialized support. Help available for the specific application
Limitations of managed hosting
- Higher cost. Managed plans typically cost more than equivalent unmanaged infrastructure
- Less flexibility. Cannot install arbitrary software or change server configuration freely
- Vendor restrictions. Some providers limit plugins, themes, or specific operations
- Lock-in risk. Custom features and proprietary integrations may complicate migration
- Resource limits. Managed plans often cap concurrent visits, database queries, or other usage
When managed hosting tends to fit
- Teams without dedicated server administration capacity
- Sites where uptime, performance, and security are business-critical
- WordPress sites where the maintenance burden is significant
- Customers willing to pay for predictability and reduced operational work
When unmanaged or static hosting tends to fit better
- Static sites that do not require server management at all (Cloudflare Pages, Netlify, GitHub Pages handle this differently)
- Custom applications where the team has server administration expertise
- Cost-sensitive projects where the operational savings of managed hosting are not worth the price difference
- Highly customized stacks that managed providers do not support
Common misconceptions
- “Managed hosting handles everything.” It handles infrastructure and platform-level concerns. Site content, design, plugin choices, and application code remain the customer’s responsibility.
- “Managed hosting prevents all problems.” It reduces operational risk but does not eliminate it; site-specific issues (broken plugins, content errors, application bugs) still occur.
- “Static hosting is the same as managed hosting.” Static hosting (Cloudflare Pages, Netlify) requires no server management because there are no servers to manage in the traditional sense; managed hosting refers specifically to provider-handled administration of dynamic infrastructure.