VPS vs serverless: fixed-price servers versus pay-per-use bills
Serverless platforms charge per request, per gigabyte and per second of function time, with no natural limit. A private VPS costs a fixed amount for fixed resources. This page compares the two honestly, so you can pick the one whose worst case you can live with.
Side by side
| Topic | Private VPS | Serverless platform |
|---|---|---|
| Billing | A fixed price per month for fixed CPU, memory, storage and transfer. | Per request, per GB transferred, per second of function time, per read/write; no upper limit unless the provider offers one. |
| Traffic spike or attack | The server slows down or limits requests; the bill does not change. | Every extra request, byte and call is billed; public cases reach five and six figures. |
| Runaway code (loops, retries) | Uses the CPU you already paid for. | Uses billable units until someone notices; several published incidents came from a single stuck loop. |
| Cost with no traffic | The full plan price, even with zero traffic. | Close to zero with zero traffic. |
| Cold starts | None; the app keeps running. | Possible after quiet periods, depending on the platform. |
| Long-running work | Background workers, queues, scheduled jobs (cron) and websockets work normally. | Time limits per run; often needs extra services. |
| Databases | Run next to the app, on the same machine or private network. | Usually a separate pay-per-use service with its own limits. |
| Control | Full control: any runtime, any port, any program. | Only what the platform’s runtime allows. |
| Upkeep | Someone has to update, monitor and back up the server (VibingView’s agent takes care of the hosting part). | Fully managed; you only own the code. |
When serverless is the better choice
- Traffic is tiny or comes in rare bursts, and the app is mostly idle.
- The work is short, stateless request handling with no background jobs.
- Nobody on the team wants to think about a server at all, and the platform offers a hard spending limit you have tested.
When a private VPS is the better choice
- You need a predictable monthly cost, whatever the traffic, bots or bugs.
- The app runs all the time: websockets, queues, cron, long requests, or a database next to it.
- You want full control over runtimes, ports and programs.
- Being public matters: a server under attack slows down; a pay-per-use account under attack gets billed.
VibingView workspaces are private servers with fixed resources, prepaid from a wallet in euros, so the bill cannot move. See pricing and the glossary.
Questions
Is a VPS always cheaper than serverless?
No. With very little traffic, or traffic in rare bursts, serverless can cost less because idle time is free. A VPS wins once the app is used all the time, runs background work, or when a predictable bill matters more than the lowest possible idle cost.
How does VibingView protect me from surprise bills?
Plans are prepaid from a wallet at a fixed price and include a fixed amount of transfer. There are no pay-per-use computing or bandwidth charges, so a traffic spike or a bug in your code cannot create a surprise bill.
Can serverless bills really reach thousands of euros?
Yes. Public incident reports describe bills from a few hundred to over a hundred thousand dollars, caused by DDoS traffic on sites billed for bandwidth, endless loops in event-driven functions, and storage reads in a tight loop, often with no hard spending limit available.