VPS vs serverless: fixed-price servers versus usage-based bills
Serverless platforms bill per request, per gigabyte and per function-second with no natural ceiling; a dedicated VPS bills a fixed amount for fixed resources. This page compares the two models factually so you can pick the one whose failure mode you can live with.
Side by side
| Dimension | Dedicated VPS | Serverless platform |
|---|---|---|
| Billing | Fixed price per month for fixed CPU, RAM, storage and transfer. | Per request, per GB transferred, per function-second, per read/write; no ceiling unless the provider offers one. |
| Traffic spike or attack | The server slows down or rate-limits; the invoice does not change. | Every extra request, byte and invocation is billed; publicly documented cases reach five and six figures. |
| Runaway code (loops, retries) | Consumes the CPU you already paid for. | Consumes billable units until someone notices; several published incidents came from a single stuck loop. |
| Idle cost | The full plan price even at zero traffic. | Near zero at zero traffic. |
| Cold starts | None; the process stays running. | Possible after idle periods, depending on the platform. |
| Long-running work | Background workers, queues, cron and websockets run normally. | Execution-time limits; often needs extra services. |
| Databases | Run next to the app on the same machine or private network. | Usually a separate metered service with its own quotas. |
| Control | Root-level: any runtime, any port, any binary. | Only what the platform's runtime allows. |
| Operations | Someone has to patch, monitor and back up the server (VibingView's agent does the hosting part). | Fully managed; you own only the code. |
When serverless is the better choice
- Traffic is tiny or extremely bursty and idle time dominates.
- The workload 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 cap you have tested.
When a dedicated VPS is the better choice
- You need a predictable monthly cost regardless of traffic, bots or bugs.
- The app runs continuously: websockets, queues, cron, long requests, or a database next to it.
- You want root-level control over runtimes, ports and binaries.
- Public exposure matters: a server that is attacked slows down; a metered account that is attacked gets billed.
VibingView workspaces are dedicated servers with fixed resources prepaid from a euro wallet, so the bill cannot move. See pricing and the glossary.
Questions
Is a VPS always cheaper than serverless?
No. At very low or very bursty traffic serverless can cost less because idle time is free. A VPS wins once the app is used continuously, runs background work, or when a predictable bill matters more than the lowest possible idle cost.
How does VibingView protect against bill shock?
Plans are prepaid from a wallet at a fixed price and include fixed transfer. There is no metered compute or bandwidth overage, so a traffic spike or a bug in your code cannot produce a surprise invoice.
Can serverless bills really reach thousands of euros?
Yes. Public incident write-ups document bills from a few hundred to over a hundred thousand dollars caused by DDoS traffic on bandwidth-billed sites, infinite loops in event-driven functions and storage reads in a tight loop, often with no hard spending cap available.