Managed Hosting vs. Managed Services vs. Self-Hosting

The terminology in this industry is混乱 (that's "chaotic" in Chinese). Managed hosting. Managed services. Self-hosting. SaaS. PaaS. IaaS. Every vendor calls their thing "managed" and it means something different.

This article cuts through the noise.

Three questions to ask first

Before you compare options, answer these three questions:

1. What are you running? A WordPress site? A custom application? A database?
2. Who needs to control it? Do you need root access? Can someone else manage the underlying infrastructure?
3. What happens when it breaks at 2am? Are you calling someone? Are you fixing it yourself?

Your answers determine which model works.

Managed hosting

What it is: Someone else manages the server. You manage your application.

What "managed" includes:

• Server hardware and data center
• Operating system patches and updates
• Web server software (Apache, Nginx)
• Sometimes: staging environments, backups, SSL certificates

What "managed" typically doesn't include:

• Your application code
• Your database (unless it's a managed database add-on)
• Security for your application layer
• Performance optimization for your specific workload

Examples:

• SiteGround, Bluehost, A2 Hosting (shared and managed WordPress)
• WP Engine, Kinsta, Flywheel (managed WordPress specifically)
• DigitalOcean App Platform, Heroku (application hosting)
• AWS Lightsail, Linode (virtual servers with some management)

What it costs (2025-2026):

• Shared hosting: $5-30/month
• Managed WordPress: $25-500/month
• Managed application platforms: $20-500/month
• Managed VPS: $20-100/month

When to use it:

• WordPress sites where you don't want server management
• Simple web applications where the platform provides what you need
• When you want predictable monthly costs

When NOT to use it:

• Applications that need custom server configuration
• Workloads that exceed platform limits
• When you need root access to the underlying server

Managed services

What it is: Someone else manages your entire technology environment. You're buying outcomes, not infrastructure.

What managed services include:

• Everything in managed hosting
• Plus: monitoring, alerting, security updates, backups, disaster recovery planning
• Plus: Often includes someone responding to incidents at 2am
• Plus: Strategic technology guidance (varies by provider)

What managed services typically doesn't include:

• Application development
• Your SaaS subscriptions (Office 365, Salesforce, etc.)
• Your own code if you're building custom software

Examples:

• Vantus Systems (managed IT for SMBs)
• MSPs across the Gulf Coast region
• Fractional CTO services
• AWS Managed Services, Azure Managed Applications

What it costs (2025-2026):

• Small business (under 20 employees): $500-2,500/month
• Mid-size business (20-100 employees): $2,000-8,000/month
• Per-device pricing: $150-400/device/month
• Project-based: $100-300/hour

When to use it:

• When you don't have internal IT staff
• When you need someone to own the entire technology stack
• When 24/7 support matters for your business
• When you want predictable IT costs instead of surprise bills

When NOT to use it:

• When you have strong internal IT capability
• When you only need one specific thing (just hosting, just security)
• When you want to own and manage everything yourself

Self-hosting

What it is: You own and operate everything. You rent or own the hardware. You install the software. You patch it. You monitor it. You fix it at 2am.

What you need:

• Hardware (server or cloud instances)
• Operating system
• Web server, database, application runtime
• SSL certificates
• Backups
• Monitoring
• Security updates
• Someone who knows how to do all of the above

What it costs (2025-2026):

• Cloud VPS (DigitalOcean, Linode, Vultr): $10-100/month
• Dedicated server (Hetzner, OVH): $50-300/month
• Colocation (your server in a data center): $100-500/month
• Your time: 5-20 hours/month for basic maintenance

When to use it:

• When you need complete control over the environment
• When you're running software that can't run on managed platforms
• When you have the technical skills to manage it
• When cost optimization is critical and you're willing to invest time

When NOT to use it:

• When you don't have technical staff or contractors
• When your application doesn't require custom infrastructure
• When uptime matters and you can't afford 24/7 coverage

The honest comparison

| Factor | Managed Hosting | Managed Services | Self-Hosting | |--------|----------------|-------------------|--------------| | Control | Medium | Low | High | | Cost predictability | High | Medium | Low | | Initial cost | Low | Medium | Medium | | Monthly cost | Low-Medium | Medium-High | Low-Medium | | 2am support | No (unless premium) | Usually yes | Your problem | | Flexibility | Limited by platform | Varies | Full | | Time commitment | Low | Low | High |

The trap to avoid

The worst outcome is paying for managed hosting but expecting managed services. You pay $50/month for a managed VPS, something breaks at 2am, and you call support expecting them to fix your application code. They can't. You didn't buy that.

Similarly, buying managed services and expecting them to hand you root access to every server is a mismatch.

Know what you're buying.

Vendor questions (copy/paste)

For managed hosting:

• What exactly is included in "managed"? Does it include my database? My application updates?
• What happens if my site goes down at 2am? Who do I call?
• Can I get SSH or root access if I need it?
• What are the limits of this platform? What happens if I exceed them?

For managed services:

• What exactly do you manage? What falls outside your scope?
• What's your response time for a production outage?
• Do you provide strategic technology guidance, or just operational support?
• What does onboarding look like? How long until I'm fully set up?
• Can I see examples of similar clients you've managed?

For self-hosting:

• Who's managing this when it breaks at 2am?
• Do you have documented runbooks for common failures?
• How are backups tested and verified?
• What's the hardware refresh cycle?

Minimum viable implementation

If you're starting fresh with WordPress:

1. Buy managed WordPress hosting (Kinsta or WP Engine are solid).
2. Set up automatic updates and backups through the platform.
3. Budget $30-100/month and forget about server management.

If you need a managed services relationship:

1. Get three MSP quotes. Ask for references from similar businesses.
2. Understand what's in scope and what's not before signing.
3. Establish a single point of contact and communication rhythm.

If you're committed to self-hosting:

1. Choose a platform (cloud VPS or dedicated server) and learn its management interface.
2. Set up monitoring before you go live (UptimeRobot, Pingdom, or cloud-native monitoring).
3. Document your setup. If you get hit by a truck, someone else needs to understand this.
4. Test your backups monthly.

When to hire help

• You bought managed hosting but you're still debugging server issues at 2am.
• You don't know who to call when something breaks.
• Your self-hosted solution has required emergency fixes more than twice in six months.
• You need someone to own the entire stack, not just one piece of it.
• You're growing and your current hosting model isn't scaling.

Managed hosting, managed services, and self-hosting are all valid choices. The mistake is picking one without understanding what it actually includes.