Jumpino
Updated
Start with the application
For a business website, I first list what must run: public pages, the API, a database, uploaded files and background jobs. The question is whether someone can operate that combination reliably within the budget. A virtual server can suit an application that needs control over its runtime. Managed hosting can suit a team that wants fewer operational tasks.
On this portfolio, Astro serves the public pages and a separate Rust API handles the content. PostgreSQL stores records and object storage holds uploads. Those components have different recovery needs. Treating them as a single folder would make a backup plan incomplete.
Check resources and the full bill
Hetzner offers shared and dedicated CPU resource categories. A virtual CPU count alone does not tell you which category you are buying. Check the current plan documentation rather than assuming that every VPS has dedicated CPU capacity.
I also account for IP addresses, storage, backups and the time needed for updates. I do not publish a fixed price comparison here: provider prices and included allowances change. The useful comparison is the cost of the required configuration and its operation.
| Question | What to verify |
|---|---|
| What runs on the server? | Runtime, database and background work |
| Where do files live? | Local disk, attached volume or object storage |
| Who handles an incident? | Access, monitoring and an agreed contact |
| How is recovery checked? | Restore records and files in isolation |
A snapshot is not the whole recovery plan
Hetzner states that server backups and snapshots exclude attached Volumes. That matters if the database or uploads live there. Write down each data location and its own recovery procedure. Keep credentials out of the repository and test a restore before relying on the setup.
When I would choose something else
If the owner needs a mostly static website and does not want server administration, a managed platform can remove work. If the application needs its own services and a maintainer is available, a VPS is worth evaluating. The right choice follows the application and the support arrangement.
For an existing system, I start with an inventory and a proposed hosting and maintenance plan. That makes the responsibilities visible before moving anything.
Sources
Hetzner server categories · Backup and snapshot coverage · Portfolio source