A VPS vs a big cloud for a small SaaS

You’ve got a small SaaS with a few hundred users, one database, and a background worker. You keep reading that a plain VPS is way cheaper than a big cloud. That’s true, but the price tag isn’t the whole story. Here’s what each one actually charges you for, and where the cheap option costs you later.

The raw numbers

Let’s price a realistic setup: one app server, one Postgres database, some storage, and enough bandwidth to serve real traffic. Say 4 vCPU, 16 GB RAM, 160 GB disk, and about 1 TB of outbound traffic a month.

Item	VPS	Big cloud
Compute (4 vCPU / 16 GB)	~€16/mo	~€110/mo (on-demand instance)
Managed Postgres	Self-run, €0 extra	~€120/mo (managed database tier)
1 TB outbound traffic	Included (20 TB cap)	~€85/mo (€0.09/GB after 100 GB free)
Block storage 160 GB	Included on the box	~€16/mo
Rough monthly total	~€16-40	~€330

That’s not a typo. The big-cloud bill for the same shape of workload runs roughly 8x to 10x the VPS one, and bandwidth is the biggest hidden driver. A big cloud charges about €0.09 per GB to send data out. A VPS gives you 20 TB with the box and charges around €1 per extra TB. If your app serves images, files, or lots of API responses, egress alone can dwarf your compute cost on a big cloud.

What the big-cloud premium actually buys

A big cloud isn’t overpriced by accident. You’re paying for things a plain VPS doesn’t sell:

Managed services breadth. A managed database service handles Postgres failover, patching, and backups for you. There’s also managed Redis, queues, object storage, and dozens more. On a VPS you run all of that yourself.
Global regions. A big cloud has data centers on every continent. A VPS provider typically covers Europe, a few US locations, and not much else. If you need low latency in Singapore or Brazil, a big cloud covers it and a VPS doesn’t.
Elastic scale. A big cloud can hand you 100 servers in five minutes and take them back an hour later. A VPS scales fine for steady growth, but it’s not built for sudden 50x spikes.
Compliance paperwork. A big cloud ships SOC 2, HIPAA, and a long list of certifications enterprise buyers ask for. A VPS provider might have ISO 27001 and solid EU data residency, but a shorter list overall.

If any of those map to a real need you have today, the premium is buying you something. If they map to a need you imagine having someday, you’re paying for insurance you may never claim.

The part the sticker price hides

The VPS box is cheaper, but “self-run Postgres” isn’t free. Someone has to set up backups, test that a restore actually works, patch the OS, watch disk space, and handle the 2 a.m. page when the disk fills. On a managed database service, the cloud does most of that. On a VPS, that’s you or someone you pay.

For a lot of small SaaS apps, that work is a few hours a month once it’s set up right. For others, it’s the thing that eats every weekend. The honest version: a VPS saves you €300 a month in cash and costs you some hours in ops. Whether that trade is good depends on how much your hours are worth and how comfortable you are running a database.

If you want the real math on that trade, we broke it down in the total cost of ownership post.

A concrete example: an app that serves images

Numbers on a table are easy to wave away, so here’s a real shape. Say you run a small SaaS where users upload and view photos: a design tool, a real-estate listing app, whatever. Traffic is modest, maybe 500 daily users, but each page view pulls several images. That adds up to about 3 TB of outbound traffic a month.

On a big cloud, that 3 TB of egress alone costs around €260 a month at €0.09 per GB, on top of your compute and database bill. Your total lands north of €500. On a VPS, that 3 TB sits comfortably inside the 20 TB the server already includes, so your egress cost is €0. Same app, same traffic, and the bandwidth line goes from €260 to nothing.

This is the case where the VPS gap stops being “nice savings” and becomes “different order of magnitude.” Media-heavy apps, file downloads, video, and chatty APIs all hit this. If your app is text-light and mostly serves small JSON responses, the gap shrinks and a big cloud’s managed convenience looks more reasonable. Know which kind of app you’re running before you pick.

What switching later actually costs

People worry about picking wrong and getting stuck. The good news: if you build on standard tools, moving between a VPS and a big cloud is a database dump and a redeploy, usually a day of work. Postgres is Postgres on either one. Docker containers run the same place. A plain Linux app doesn’t care which company owns the metal.

The trap is leaning on proprietary cloud-only services. If you wire your app to a proprietary NoSQL store, serverless functions, a proprietary queue, and a proprietary auth service, you’re not on that cloud the way you’re on a VPS, you’re on it the way a house is on its foundation. Ripping those out later is a rewrite, not a migration. If keeping your options open matters, stick to portable tools and treat the managed services as a convenience you can walk away from, not a dependency you build around.

Or, we do it for you

We run apps on a VPS so you get the cheap-infrastructure price without the ops work: tested backups, patching, monitoring, and a human on call. See what that costs on our pricing page.

FAQ

Is a VPS reliable enough for production?

Yes. VPS providers run real production workloads for thousands of companies, with solid uptime and ISO 27001 certification available from most of them. The difference from a big cloud isn’t reliability of a single server, it’s the managed services and global reach around it. A well-configured VPS is not a weekend-project risk.

Why is big-cloud bandwidth so expensive?

A big cloud charges about €0.09 per GB for outbound traffic, and that adds up fast for any app serving media or heavy API responses. It’s one of the least visible parts of a big-cloud bill and often the biggest surprise. A VPS typically includes 20 TB per server, which covers most small apps completely.

Can I start on a VPS and move to a big cloud later?

Yes, and plenty of teams do the reverse too. If you build on standard tools (Postgres, Docker, plain Linux) rather than cloud-only proprietary services, moving between them is straightforward. The lock-in risk comes from leaning on proprietary managed services, not from the server itself.

Does cheaper hosting mean worse performance?

No. A mid-tier VPS and a comparable big-cloud instance give you similar CPU and memory. For a lot of workloads a VPS’s dedicated-core plans actually feel snappier than big-cloud burstable instances, which throttle CPU once you exhaust credits. You’re paying the big cloud for services and reach, not for raw speed.