VPS for SaaS: 4GB RAM if the database shares the box

A small SaaS can run on one VPS. Size the whole stack — API, database, workers, reverse proxy, deploys, backups — not just the app process.

Buying rule: 4GB RAM if the database lives on the same VPS. 2GB only for prototypes or tiny internal tools.

Minimum

2GB RAM for a small API plus database; 4GB RAM if the database is important.

Recommended

2 vCPU / 4GB RAM / 60GB+ SSD for a small but serious production backend.

Upgrade when

Upgrade when database memory, background jobs, search, or traffic spikes become visible bottlenecks.

What matters for a SaaS VPS

The server needs to handle the API, database, workers, deploys, logs, backups, and monitoring. The early advantage is simplicity. The risk is putting every failure mode on one box.

Recommended provider fit

  • Hetzner CX32
  • Vultr 4GB
  • DigitalOcean Basic 4GB
  • Linode 4GB

Buying rule

Use 4GB RAM for a customer-facing SaaS backend if the database lives on the same VPS. Use 2GB only for prototypes or very small internal tools.

Updated Sep 15, 2026

If that SaaS already runs on OVH Public Cloud or a Gen 2024/2026 dedicated server, 1 October 2026 is a bill date, not a sizing date. Compute hourly rates stay; local disk and public IPv4 unbundle. Dedicated renewals on or after that day use the new scale. Checklist and OVH sources: OVH October 2026 price change. The 4GB rule on this page does not move.

Small SaaS VPS FAQ

Can a small SaaS run on one VPS?
Yes in the early stage. One well-managed VPS can run an API, database, reverse proxy, and workers, but backups and monitoring are not optional.
When should a SaaS move off one VPS?
Move when database load, uptime requirements, deployment risk, or team workflow make one box too fragile.
What should I avoid for a SaaS VPS?
Avoid plans with unclear support, weak backups, tiny disks, or pricing that looks cheap only because renewal terms are hidden.