Disclosure: We earn commissions from partner links. This doesn't affect our rankings. Learn more

VPSchart Editorial Team

This guide compares the responsibility described in linked provider and Ubuntu documentation. It does not rank providers by an unverified test or score.

Published: Jan 20, 2026 · Updated: Oct 21, 2026 · Our methodology

Managed vs Unmanaged VPS: Who Handles What?

Choose the service contract before you compare CPU, RAM or price. A self-managed VPS gives you administrative control, but the operating system, firewall, applications, monitoring and recovery remain your work. A managed service can take over some of those tasks, but only the written scope tells you which ones.

Checked October 21, 2026: Hetzner Cloud, Hostinger VPS and DigitalOcean Droplets are self-managed offers. The links on this page lead to those self-managed products, not to a managed VPS service.

The short answer

Choose self-managed only if someone can own patching, access control, firewall rules, monitoring, backups, restores and incident response. Choose managed when you need a named party to perform defined operating tasks under a support agreement. Do not treat a dashboard, one-click installer or support chat as proof that the server is managed.

Responsibility matrix

The managed column is intentionally a contract checklist. Providers use the word managed for different scopes. Ask who performs each task, how often it is performed and what happens outside business hours.

Task	Self-managed VPS	Managed service: verify in writing
Physical host and network	The infrastructure provider operates the underlying hardware and network.	Usually the same provider responsibility. Ask whether network or hardware incidents have a stated response target.
Operating system	You choose, configure and maintain the installed OS.	Confirm supported distributions, patch cadence, reboot handling and version upgrades.
Firewall and access	You control SSH keys, users, open ports and host firewall rules.	Confirm whether the provider changes rules or only advises you. Ask who retains emergency access.
Applications and databases	You install, update, configure and troubleshoot the software.	List every application that is included. Server management does not automatically include WordPress, Docker, a database or custom code.
Monitoring and response	You define alerts and respond when a service, disk or certificate fails.	Ask what is monitored, who receives the alert and whether remediation is included.
Backups and restores	You select backup coverage, retention and an off-server copy, then test restoration.	Confirm what is backed up, retention, restore assistance, recovery target and excluded disks or application data.
Security incident	You investigate, contain, rebuild and restore the server and applications.	Confirm the escalation path, response hours and whether compromise cleanup is included or billable.

What the three linked VPS offers actually provide

These are commercial paths already used by VPSchart. They remain on this page because they are valid self-managed options. None is presented as a managed VPS recommendation.

Hetzner Cloud

Hetzner states that Cloud Server clients are responsible for server management, maintenance and security. Hetzner maintains the underlying cloud infrastructure.

Check Hetzner Cloud

Hostinger VPS

Hostinger states that its VPS plans are self-managed. Its dashboard adds tools for SSH, firewall, backups, monitoring, OS changes and recovery, while you still manage the software environment.

Check Hostinger VPS

DigitalOcean Droplets

DigitalOcean describes Droplets as completely unmanaged and states that its support team cannot access a user's Droplet directly. Its setup guide documents the controls you operate yourself.

Check DigitalOcean

The three buttons above are affiliate links. The provider documentation linked below is the source for the management scope. Recheck that scope and the current checkout terms before purchase.

Self-managed readiness test

A self-managed VPS is a reasonable fit only when every required task has an owner. Answer these questions for the actual person or team operating the server:

Who applies operating-system and third-party software updates?
Who reviews public ports, SSH access and firewall rules after a change?
Who receives disk, memory, certificate and availability alerts?
Who responds when the service fails at night or during a holiday?
Where is the off-server backup, and when was a restore last tested?
Who upgrades the application and database without losing data?
Who can use the provider console or recovery mode after an SSH lockout?

If one of these tasks has no owner, compare a managed service or hire operational support before placing production data on the server. The cost decision should include that work, not only the VPS invoice.

Questions to put in a managed-service contract

Which operating systems, control panels, applications and databases are covered?
Are security updates automatic, reviewed or installed only after a request?
Are version upgrades and reboot coordination included?
Does monitoring cover only the host, or also web, database and application health?
Is response available around the clock, and is the target a reply or an actual repair?
What backup data, retention, locations and restore tests are included?
Who handles a compromised server, and which recovery work costs extra?
Can you retain root access, and does using it change the support scope?

Minimum operating baseline for a self-managed VPS

DigitalOcean's recommended setup uses SSH keys, a non-root administrative user, a firewall, monitoring and backups as part of a production baseline. Ubuntu documents ufw as its default firewall configuration tool and includes unattended-upgrades for automatic security updates on supported Server installations.

Those tools reduce repetitive work, but they do not transfer responsibility. Check update logs, include third-party repositories deliberately, monitor failed jobs and prove that a backup can be restored. A green provider dashboard cannot confirm that the application data is recoverable.

Ready for a self-managed server?

Use the responsibility checklist first. Hetzner Cloud is one of the existing self-managed commercial paths on this page. Confirm the current product scope and checkout terms before creating the server.

Open Hetzner Cloud

Continue with the operating task

Choose and secure a first VPS VPS security checklist Managed VPS guide Hetzner provider guide Hostinger provider guide DigitalOcean provider guide

Official sources checked

These sources were checked on October 21, 2026. Support scope and product controls can change, so confirm the provider documentation and contract again when you buy.