What you are actually choosing between
A VPS gives you a machine and root access. Everything above the operating system is yours: web server, runtime, database, TLS certificates, patching, backups, monitoring.
A managed platform takes the deployment and the runtime. You push code and it runs, with scaling, certificates and patching handled underneath.
The cost difference per unit of compute is large and consistently favours the VPS. The time difference favours the platform, usually by more than the money.
The work a VPS actually involves
- Initial hardening: firewall, SSH keys rather than passwords, disabling root login, automatic security updates
- Web server and TLS certificate setup and renewal
- Runtime installation and version management
- Database installation, tuning and, importantly, backups that you have tested restoring
- Monitoring and alerting so you find out about problems before your users do
- Ongoing patching, indefinitely
None of this is difficult. All of it is recurring, and it is the part people underestimate.
When a VPS is clearly right
When you need specific control the platform will not give you, when the software is unusual or legacy, when cost per unit of compute genuinely dominates, or when you enjoy and are competent at systems administration and the time is not a cost you are counting.
Hetzner in particular makes this compelling: the price-to-performance gap against a managed platform is wide enough that for some workloads it is not a close call.
When a managed platform is clearly right
When the application is ordinary, when the team is small and shipping features matters more than infrastructure, and when nobody on the team wants to be woken up because a disk filled with logs.
The honest framing is that the platform premium buys back hours every month. If those hours are worth more than the difference, the platform is cheaper.
A middle path that works well
Run the application on a VPS and use managed services for the parts that hurt most when they go wrong. A managed database is the usual first candidate, because backups, failover and patching are where self-hosting most often causes real damage.
This keeps the cost advantage on compute while removing the highest-consequence operational risk.
Related accounts
Accounts on the platforms discussed here: Buy DigitalOcean Accounts, Buy Linode Accounts, Buy Hetzner Accounts.
Related cloud accounts
Accounts on the platforms discussed here, with every configuration and price published up front:
- Buy DigitalOcean Accounts — from $25.00. Droplets, managed Kubernetes and Spaces.
- Buy Linode Accounts — from $25.00. Akamai-backed compute and SMTP-capable accounts.
- Buy Hetzner Accounts — from $50.00. German infrastructure, GDPR compliance, strong price to performance.
Further reading
- AWS vs Hetzner: Which Cloud Account Should You Buy?
- DigitalOcean vs OVHcloud: Which Cloud Account Should You Buy?
- Hardening SSH on a New Cloud Server
- Hetzner vs OVHcloud: Which Cloud Account Should You Buy?
Official documentation
Provider behaviour, quotas and pricing are defined by the platform itself. These are the first-party references for the services discussed above:
Frequently asked questions
It requires you to do the securing, which a platform does by default. The steps are well documented, but they are your responsibility and they continue indefinitely.
Usually yes, and containerising the application first makes it much easier.
Tested backups. Many people configure backups and never verify that a restore actually works.
