Two categories in this directory answer the same question, and people arriving at either one are usually deciding between both. A virtual server gives you a machine. A platform as a service gives you a deploy command. Everything else follows from that.
This post has no prices in it, which is deliberate: the figure that decides this is almost never the invoice.
What each one asks of you
| Virtual server | Platform as a service | |
|---|---|---|
| You provide | A machine, and everything on it | A repository |
| Operating system updates | Yours | Theirs |
| TLS certificates | Yours to install and renew | Issued and renewed for you |
| Deploys | Whatever you build | Push to a branch |
| Scaling | Resize the box, or build for more than one | Usually a setting |
| Backups | Yours to configure and test | Usually included, worth verifying |
| Database | Install and operate it, or buy one | Attached as a managed add-on |
| Debugging a bad night | Shell access to everything | Whatever the dashboard exposes |
| Moving away | Copy the files, rent another box | Depends entirely on how much of the platform you used |
The last row is the one people underweight when choosing and overweight afterwards.
The cost nobody puts in the comparison
A virtual server is cheaper on the invoice and more expensive in attention. That trade is real, and it is not constant: it depends almost entirely on how many hours you have and how much you already know.
If you have run a Linux server before, the operational work on a small deployment is genuinely small. Unattended upgrades, a reverse proxy that renews its own certificates, a backup that you have restored from at least once. It is a weekend to set up and very little after that.
If you have not, the same list is a month of learning, and you will learn some of it during an outage. That is not an argument against doing it. It is an argument for being honest about which column the time comes out of.
The middle option most comparisons miss
There is a third answer, and in European developer communities it is the common one: a self-hosted deployment platform on a virtual server you rent.
Coolify, Dokploy, CapRover, Dokku and Cloudron all install onto a plain server and give you most of the platform experience on top of it. You get Git deploys, certificates and a dashboard, and you keep the server's price and the server's obligations.
The search data backs this up as a European pattern rather than a niche one. Self-hosted platforms take 2.97 times the share of hosting search in Europe that they take in the United States, and virtual servers take 2.13 times the share. The pairing of an inexpensive European server with a self-hosted platform on top is not a workaround here; it is the default.
Where each one wins
A virtual server wins when you want one machine you fully control, your workload is steady rather than spiky, you care about the invoice, or you have a compliance requirement that is easier to satisfy when you can point at a single server in a single country.
A platform wins when deploying is the thing you do most, the team is small enough that an evening of operations work is an evening not spent shipping, or your traffic is uneven enough that scaling by hand would be a recurring chore.
A self-hosted platform wins when both of the above are true at once, which is more often than either category's marketing admits.
European options in each
Every provider below is a European company, taken from this directory rather than from a list of the largest vendors. Northflank is the one to read carefully: it is a United Kingdom company, which puts it outside the CLOUD Act and also outside the European Union, and those are different facts that a requirement written against EU membership will treat differently.
| Category | European options |
|---|---|
| Virtual servers | Hetzner (Germany), Scaleway (France), UpCloud (Finland), netcup (Germany), Exoscale (Switzerland), Gcore (Luxembourg), Cherry Servers (Lithuania), Time4VPS (Lithuania), Webdock (Denmark) |
| Platform as a service | Clever Cloud (France), Scalingo (France), Upsun (France), Koyeb (France), Northflank (United Kingdom) |
| Self-hosted platforms | Coolify (Hungary), Cloudron (Germany), YunoHost (France) |
The self-hosted row is the one where the sovereignty question resolves differently: the software's origin does not matter much, because the data sits on whichever server you installed it on. That is either the simplest answer to a data residency requirement or an extra thing to be responsible for, depending on how you look at it.
A short checklist
- Count the hours you can spend on operations in a normal month. Be pessimistic.
- Decide whether you need shell access to debug your own system. Some workloads genuinely do.
- Check whether your compliance requirements are written against a country, a company, or a certification. They are different questions and only the first is answered by picking a region.
- Look at how you would leave. Not because you plan to, but because the answer tells you how much of the platform you are actually buying.
- Only then compare prices.
Every provider named here has a page in the directory with its company location, its European regions and its CLOUD Act exposure recorded. Pricing appears once someone has checked it.