Serverless vs VPS Hosting: A Cost & Ops Guide
Hosting choices split cleanly into two philosophies: pay per request and let the platform scale (serverless), or rent a box and run everything yourself (a VPS). Both are correct — for different traffic shapes and different tolerances for ops work. The mistake is picking one on vibes and discovering the cost curve or the operational burden the hard way at 2 a.m.
How they actually differ
| Factor | Serverless | VPS |
|---|---|---|
| Cost at low/spiky traffic | Near-zero when idle | Fixed monthly, paid even when idle |
| Cost at steady high traffic | Can get expensive per-request | Predictable, often cheaper |
| Scaling | Automatic, instant | Manual — you provision |
| Cold starts | Yes, first request lag | None |
| Ops burden | Platform handles patching, uptime | You own the box: patches, restarts, monitoring |
| Long-running jobs | Awkward (timeouts) | Natural |
| Lock-in | Higher (platform-specific) | Lower (portable) |
Choosing between them
Run through this checklist. More boxes on one side is your answer.
Lean serverless if:
- Traffic is spiky, seasonal, or unpredictable
- You want to pay ~nothing while pre-launch or between spikes
- Nobody on the team wants to be on-call for a server
- Workloads are short request/response, not long batch jobs
Lean VPS if:
- Traffic is steady and high enough that per-request billing hurts
- You run long jobs, WebSockets, or background workers
- You want predictable monthly cost and full control
- Portability and avoiding platform lock-in matter to you
For many early products the honest answer is serverless first: it's near-free until you have traction, and by the time per-request cost becomes real you'll know your traffic shape well enough to move the hot paths to a VPS. Premature VPS ops is a tax you pay before you have users.
Sizing it with CraftMyStack
Hosting cost compounds with your database and backend choices. Use the AI stack recommendations to get a hosting model matched to your traffic pattern and budget, then browse hosting and infra tools to compare providers on price and features before you provision anything.
Key takeaways
- Serverless wins on spiky traffic and near-zero idle cost; a VPS wins on steady high traffic, long-running jobs, and predictable billing.
- Cold starts and platform lock-in are the serverless taxes; patching and on-call are the VPS taxes.
- Serverless-first is a sane default early — move hot paths to a VPS once traffic is understood.