Managed Hosting vs. VPS: Who's Responsible When Your Site Goes Down?

The question of managed hosting vs. VPS rarely comes up on the day you sign up. It arises at 2 AM, with your website down, when someone discovers that the provider "only delivers the machine." This comparison shows who handles each layer in both models, what each truly costs, and in which situations each choice makes sense for your business.

TL;DR: Managed Hosting vs. VPS in Four Key Points

• With an unmanaged VPS, the provider is responsible for hardware and network. The operating system, web server, database, SSL, backup, and security are your problem.
• A 99.99% VPS SLA doesn't cover application failures or configuration errors. Any credit, if available, is proportionate to the VPS's value itself.
• The monthly VPS fee is the smallest part of the cost. What truly adds up are the hours of the administrator and the losses from each hour of downtime.
• A VPS makes sense when you have a technical person with dedicated time and on-call availability. Without that, managed hosting is cheaper annually.

What Really Changes in Managed Hosting vs. VPS

Both models can run on the same type of machine. Often, they literally run in the same data center. The difference isn't in the hardware: it's in who is responsible for what happens on top of it.

A VPS (virtual private server) is a slice of a physical server, with dedicated CPU, memory, and disk for you. You receive an IP, root access, and generally a panel to start, stop, and reinstall the machine. From there up, everything is yours. DigitalOcean states this clearly in its Droplet policies: the machines are "completely unmanaged," and even the support team doesn't have access to them.

AWS calls this arrangement a shared responsibility model: it handles the security "of" the cloud (facility, hardware, virtualization), and the customer handles the security "in" the cloud, which includes updating and applying patches to the instance's operating system.

With managed hosting, a team assumes these upper layers by contract. They install, update, monitor, back up, test restoration, and respond when something breaks. You remain the owner of the site and data, but you are no longer on call.

That's why the comparison between managed hosting vs. VPS is rarely about performance. A well-configured VPS is fast. The right question is different: who wakes up when it stops working?

Who Handles What: The Responsibility Matrix

At Agathas Web, we've operated Linux servers since 2008: Moodle for educational institutions, websites, systems in Laravel and Next.js, and integrations with the official WhatsApp API. The table below summarizes the managed hosting vs. VPS division layer by layer. It's the same conversation we have with those who come asking for "just a VPS."

Layer	Unmanaged VPS	Managed Hosting
Data center hardware, power, and network	Provider	Provider (contracted by management team)
Operating system and security patches	You	Management Team
Web server, PHP/Node, database	You	Management Team
SSL certificate and renewal	You	Management Team
Firewall, WAF, fail2ban, hardening	You	Management Team
Backup and restoration testing	You	Management Team
24/7 Monitoring and alerts	You	Management Team
Diagnosis when the site goes down	You	Management Team
Application code	You	You (or separate contract)
Business content and data	You	You

Notice the last two lines. Not even the best managed hosting can fix a bug in your code or a poorly written plugin without a specific agreement for it. Be wary of anyone who promises to "take care of everything" without separating infrastructure from application.

Tasks That Disappear from Your Radar with a VPS

Some responsibilities seem small until the day they fail:

• Expiring SSL. Let's Encrypt ended expiration notification emails in June 2025. And validity will shorten: the default profile drops to 64 days on February 10, 2027, and to 45 days on February 16, 2028, according to the official announcement. Automatic renewal without monitoring is a gamble.
• Outdated PHP Version. PHP 8.2 receives security fixes only until December 31, 2026, according to the supported versions table. Those who don't follow this calendar discover it when a plugin stops working or a public vulnerability emerges.
• Full Disk. Logs that grow without rotation, local backups that are never deleted, accumulated sessions. It's one of the most common causes of database freezes we've seen.
• Untested Backup. Having the file proves nothing. Only a tested restore proves it.

Your VPS SLA Doesn't Cover Your Website

This is the point that most surprises those comparing managed hosting vs. VPS by the price list. The VPS provider advertises 99.99% availability, and the client understands that their site is guaranteed. It's not.

The DigitalOcean Droplet SLA is a good example because it's clear. It counts as unavailability the loss of connectivity or disk access caused by a failure in DigitalOcean's infrastructure. And it expressly excludes problems arising from application code or client configuration errors.

Translating this to everyday scenarios:

1. Did PHP-FPM crash due to lack of memory? That doesn't count.
2. Did MySQL corrupt a table after an abrupt shutdown? That doesn't count.
3. Did the certificate expire and the browser block access? That doesn't count.
4. Did a brute-force attack bring down the server? That doesn't count.

And when it does count, credit is applied only to the value of the affected machine, on a future bill. If your VPS costs the equivalent of $40 per month, that's the cap for compensation, even if the downtime cost you an entire day of sales.

It's worth calculating how much downtime each SLA level allows in a 30-day month, because it changes how you compare managed hosting vs. VPS in any proposal:

Monthly SLA	Allowed Downtime per Month
99%	approx. 7h 12min
99.9%	approx. 43min
99.99%	approx. 4min

The SLA number matters less than the question: what exactly is covered, and who is on the other side when it breaks?

When the Site Goes Down at 2 AM: The Two Scenarios

Imagine the same outage on both sides of the managed hosting vs. VPS equation and see what happens. The database stops responding on a Friday night into Saturday morning.

Scenario with Unmanaged VPS

No one is notified because no external alert was configured. The first sign is a client complaining on WhatsApp at 8 AM. Whoever handles IT (sometimes the owner, sometimes a freelancer) tries to access via SSH, discovers the disk is 100% full, deletes logs in a hurry, and restarts the service. If the table corrupted, the search for the backup begins. If the backup was on the same disk, the situation becomes much more difficult.

If the company uses the official WhatsApp API with a webhook hosted on this VPS, messages that arrived overnight might not have been processed. Customer service starts the day without knowing who wrote in.

Scenario with Managed Hosting

External monitoring triggers within minutes. The on-call team receives the alert, identifies the cause, frees up space, restores the service, and logs the incident. In the morning, the client receives a report: what happened, how long it lasted, and what was done to prevent recurrence (log rotation, 80% disk alert, off-server backup).

The difference between the two scenarios isn't technical talent. It's process and on-call coverage. A competent person, working alone, sleeps, travels, and gets sick.

Real Cost: The VPS Monthly Fee Is the Smallest Part

The classic argument for those weighing managed hosting vs. VPS is price. It remains valid but became less flexible in 2026. Hetzner, a benchmark for affordable VPS in Europe, adjusted its cloud prices starting June 15, 2026 for new orders: in Germany and Finland, the CX23 went from €3.99 to €5.49 per month, and the CPX22 from €7.99 to €19.49, excluding taxes and IPv4.

Even so, the machine itself is inexpensive. What isn't cheap is everything else.

What Goes into the VPS Cost

• Administration Hours. Monthly updates, log review, SSL renewal and verification, firewall adjustments, backup testing. Even a simple server requires a few hours per month from someone who knows what they're doing.
• Separate Tools. External storage for backup, uptime monitoring, potentially a WAF.
• On-Call Availability. If the site generates revenue, someone needs to be available outside business hours. This has a cost, even if it's you.
• Downtime Cost. Do the simple math: monthly online revenue divided by the hours in the month. This is the approximate value of each hour of downtime, not counting reputation.

What Goes into the Managed Hosting Cost

A higher monthly fee, with operations embedded. For our managed hosting, the reference range is $250 to $500 per month for informational websites and blogs, and $600 to $2,500 per month for e-commerce and SaaS, with setup fees from $800 to $3,500 depending on complexity. Larger operations receive custom quotes.

The fair comparison of managed hosting vs. VPS, therefore, isn't "$40 versus $400." It's "$40 + technical hours + tools + risk" versus "$400 with all of that included in the contract."

When a VPS Is the Right Choice (and When It Isn't)

There's no universal winner when it comes to managed hosting vs. VPS in all cases. We've recommended VPS to clients and will continue to do so when it makes sense.

Choose a VPS when

• Someone on your team has real Linux expertise and dedicated time in their schedule for it.
• The project is for testing, staging, or internal use, and a few hours of downtime won't cause significant loss.
• You need total control over versions and configurations that no managed provider would agree to maintain.
• The budget is very tight, and the risk of downtime has been consciously accepted.

If this is your case, start with security basics. Our Linux server hardening checklist and the guide on how to protect your web server with WAF, fail2ban, and rate limiting cover the minimum an internet-exposed VPS needs on day one.

Don't Choose a VPS when

• The website or system sells, generates leads, or serves customers, and no one in the company knows what to do if MySQL stops.
• Your "IT team" is a freelancer who responds when they can.
• Sensitive personal data is involved. Under privacy laws, the data controller remains responsible, and US state privacy laws often mandate reporting relevant security incidents within specific timeframes, sometimes as short as 72 hours. Discovering a breach a week later is a legal problem, not just a technical one.
• The platform is critical and has predictable peaks, such as Moodle during exam week or an e-commerce site during a promotional event.

For educational platforms, the comparison gains other variables. We detail this in the article on Moodle on AWS vs. Managed Hosting.

Pitfalls When Contracting Managed Hosting

"Managed" has become a marketing buzzword. There's shared hosting reselling with that name and VPS with a panel installed and nothing more. Anyone comparing managed hosting vs. VPS needs to know what they are actually buying. Before signing, ask these questions in writing:

1. What happens when the site goes down outside business hours? Who receives the alert, and how quickly do they respond? Ask for the number in the contract.
2. Is the backup stored off-server? How often is restoration tested? Backup on the same disk doesn't protect against disk failure or ransomware.
3. Who applies security patches and how quickly after a public vulnerability is disclosed? "When we get to it" is not an answer.
4. Does the SLA have consequences? Promising 99.9% without penalties or credit is an intention, not a commitment.
5. Can I leave with everything? Request access to your data, backups, and environment documentation. Long-term contracts and undocumented environments are the same problem with different names.
6. Who responds? A Level 1 agent reading a script, or someone who has operated the type of system you use?

If the answers are vague, you're buying a VPS with another name and a higher price.

How Agathas Web Solves This

Our managed hosting exists for those who want the performance and control of a dedicated server for their project, without becoming its on-call administrator. In practice, the contract includes:

• Environment configured for your stack: WordPress, Laravel, Next.js, Node, Python, Moodle, or custom systems, on AWS, Hetzner, Cloudflare, or bare metal, as the project requires.
• Security by default: Cloudflare WAF, fail2ban, system hardening, automatic SSL, and MFA.
• Daily and incremental backup, off-server, encrypted, with restoration tested monthly.
• 24/7 Monitoring with alerts to the technical team and critical incident response within 15 minutes.
• Contractual SLA: 99.9% monthly uptime (maximum approx. 43 minutes per month), critical incident resolution within 2 hours, and critical patch within 72 hours after public disclosure of the vulnerability, with penalties if we fail to comply.
• Direct support with the team operating the environment, via dedicated WhatsApp, and a monthly report with uptime, backups, and events.

Onboarding begins with a free diagnostic of your current infrastructure, delivered within 3 business days. If it makes sense to proceed, we migrate your site, database, emails, and DNS within 7 business days, with a staging environment for you to validate beforehand and the old environment preserved for 30 days for rollback. The contract is monthly, with no long-term commitment, and requires 30 days' notice to cancel.

And if the diagnostic shows that, in your case, the balance of managed hosting vs. VPS tips toward a simple VPS, we will tell you so.

Conclusion: Choose Who Wakes Up When Your Site Goes Down

Ultimately, the choice between managed hosting vs. VPS is a choice about responsibility. A VPS delivers a good, inexpensive machine and leaves everything else to you. Managed hosting charges more to assume the rest by contract.

If you have a technical person with dedicated time and on-call availability, a VPS might be the best value for money. If not, the hidden cost appears on the first night your site is down.

Want to know which side of the managed hosting vs. VPS debate your business falls on? Request a free diagnostic on the Agathas Web managed hosting page. Within 3 business days, you'll receive the risks, costs, and a recommendation, with or without a contract.