Vercel vs $5 VPS: The 60-Second Test That Decides

Everyone compares sticker prices, nobody compares bills

"$20 vs $5, VPS wins" is as lazy as "serverless scales, VPS doesn't." The real comparison has four axes and they point different directions depending on your traffic. The bill-shock autopsies put a $700+ spike at 88% egress, 8% edge requests, ~0% compute — the meter that bites is bytes and request count, not CPU.

Meanwhile VersusStack's 2026 bake-off crowns Vercel on DX and Cloudflare on cost at every scale. Both true.

Here's the whole board:

The decision rule (60 seconds)

Stay on Vercel if: spiky unpredictable traffic with real money attached, a team that ships PR previews all day, zero DevOps appetite, and bills still near the seat. Move to VPS if: steady or growing traffic, bandwidth past 60% of the bundle, background jobs hitting timeouts, or one surprise invoice already burned trust.

The levels in between — Lambda/OpenNext at ~$67, Coolify at ~$25–40 — split the difference and are all honest answers for their shapes.

BoringPush refuses to pick for you: the same Next.js stack deploys to Vercel with a hosted database such as MongoDB, to Lambda or Coolify, or to a bare VPS with SQLite, with zero query rewrites. Run both for a month — Vercel for previews, VPS for prod — and let the invoices vote.

Ship from anywhere either way; the repo doesn't care where it runs, only that the loop stays one command.

FAQ

Is the latency gap really 300x?

Per query, yes: 0.1ms local vs 35ms+ network hop is the physics, not marketing. Pages doing 3–5 queries feel it most — that's 0.5ms vs 200ms+ of pure waiting before any compute.

What breaks first on a $5 box?

Disk (past ~50GB — snapshot strategy), then write contention, then geography. Reads basically never — page cache handles absurd throughput.

The flip triggers are writes/backups/regions, documented in the SQLite guide.

Can I mix: Vercel frontend, VPS backend?

Yes, and it's underrated: marketing pages on the edge, app + DB on the box. Two bills, each minimal, best of both physics.

BoringPush's env-per-target setup supports exactly this.

Do preview deployments exist off Vercel?

Staging hostname on the same box (staging. tunnel, second PM2 process) — $0 extra. Less magical than per-PR URLs, equally effective for review.

Which is better for AI-agent workflows?

VPS, slightly: persistent filesystem state, no function timeouts killing long agent runs, and the agent edits the exact tree that deploys. Serverless sandboxes add a translation layer agents occasionally mistranslate.