Managed vs unmanaged hosting

A managed plan next to an unmanaged server with the same specifications looks overpriced, sometimes by multiples. That comparison is how people end up running production sites as unpaid, untrained system administrators. The specifications are not the product. The operations are.

What unmanaged means

On an unmanaged VPS or cloud instance, the provider's duty ends at the hypervisor. Inside the machine every recurring task is the customer's: operating-system and stack updates, firewall and TLS configuration, backups with tested restores, monitoring that alerts a person, and the diagnosis when something breaks at the worst possible hour. None of these is hard on its own. Together they are a role, and the role exists whether or not anyone has been assigned to it.

The arithmetic

• Count the hours: setup, then the recurring maintenance, then incidents, multiplied by what the owner's time earns elsewhere.
• Count the risk: an unpatched server or an untested backup is not a saving; it is a deferred bill with interest.
• Then compare the managed premium against those two numbers, not against the raw server price. For most businesses without an operations person, the premium wins.

When unmanaged wins

Three cases. The owner has the skills and enjoys the work, in which case unmanaged is cheaper and keeps the skills sharp, and DigitalOcean is the natural home. The owner is learning, and a disposable server is the best classroom there is. Or the organisation is at a scale where an operations capability is already on the payroll and the managed premium would multiply across a fleet. Absent from the list: the managed plan looked expensive.

Reading a managed plan's scope

Managed has no legal definition, so the scope-of-service page is the product description. It should include operating-system and stack updates, security hardening, monitoring with human response, backups with restores the customer can trigger, and stated support response times. Application-level plans, managed WordPress or managed WooCommerce, should also update the application itself and provide staging. Anything not written down is not included; the scope is the contract.

The two managed picks in the comparison split the territory by stakes: Cloudways for the self-service middle rung, Liquid Web where the site is the business and support depth is what is being bought.

Going unmanaged is also a learning decision, and exams exist for the skills it demands: the RHCSA tests live-server administration with no multiple choice, LPIC-1 covers the same ground vendor-neutrally and in German, and CompTIA Linux+ adds automation and containers. None is required to run a VPS; all three are what employers ask for when they pay someone to.