What server do I need to host a self-hosted SaaS script?
A 2 vCPU / 4 GB RAM VPS with 80 GB of SSD, costing $8–$20 a month, runs almost every ready-made SaaS script comfortably through its first few hundred tenants. The usual stack is Ubuntu 22.04 or 24.04, Nginx, PHP 8.2+ with the standard extensions or Node 20+, and MySQL 8 or PostgreSQL 15. Shared hosting is the wrong choice: most of these applications need background workers, cron and a persistent process, which shared plans do not give you.
Written by ZoopCoder, who build and sell SaaS source code. That makes us an interested party in this answer, so we have kept it to things you can verify yourself.
The numbers
2 vCPU / 4 GB
Sensible starting VPS
Handles a few hundred tenants in most categories.
80 GB SSD
Starting disk
Media-heavy platforms need object storage instead of a bigger disk.
$8–$20 / mo
What that costs
From any mainstream provider.
Requirements by category
The stack barely changes between categories; the disk and bandwidth change enormously. Use the row that matches what you are launching rather than a single global recommendation.
| What you are running | Start with | The constraint that bites first |
|---|---|---|
| Form builder, payment links, billing, helpdesk | 2 vCPU / 4 GB / 60 GB | Nothing, for a long time. These are database-light. |
| Inventory and POS, matrimonial, QR menu ordering | 2 vCPU / 4 GB / 80 GB | Database size once product images and profile photos accumulate. Move uploads to object storage early. |
| Multi-vendor marketplace, classifieds, crowdfunding | 4 vCPU / 8 GB / 160 GB | Image storage and search queries. A search index becomes worth it around ten thousand listings. |
| WhatsApp marketing | 2 vCPU / 4 GB / 80 GB, plus a reliable queue worker | Not the server — the API rate limits and the per-conversation cost. |
| Food delivery with live tracking | 4 vCPU / 8 GB / 80 GB | Concurrent websocket connections during peak dinner hours. |
| OTT streaming | 4 vCPU / 8 GB, plus object storage and a CDN from day one | Egress. Never serve video from the application server. |
The checklist before you buy the server
Six things to confirm, in this order. The first two eliminate most of the cheap options that look like a bargain.
- Root or sudo access. You will need to install extensions, set cron entries and run a process manager. If a host does not give you a shell, it cannot run this software.
- The ability to run background workers and cron. Queues, scheduled reports, subscription renewals and retry logic all live here. Shared hosting typically restricts or kills long-running processes.
- Outbound port 25 policy, or a mail relay. Most providers block port 25. Plan to send transactional email through a relay with SPF, DKIM and DMARC set, not from the box.
- Snapshot support. Take one before every upgrade. It converts a bad deploy from an incident into a five-minute rollback.
- Bandwidth allowance and egress price. Read the number, especially if you are in video. “Unlimited” is always metered somewhere.
- A region near your customers. Latency to the database matters more than raw CPU for perceived speed, and data-residency rules may make it mandatory.
When to upgrade, and what to upgrade
Upgrade on evidence, not on anxiety. The signals below each point at a different resource, and the common mistake is buying more CPU when the problem is disk I/O or a missing index.
| Symptom | Usual cause | What to do |
|---|---|---|
| Pages slow only at peak hours | PHP-FPM or Node process count, not CPU | Raise worker counts first; add CPU only if they are saturated |
| Everything slow, all the time, as data grows | Missing database indexes | Read the slow query log before buying anything |
| Disk filling steadily | User uploads on the local filesystem | Move media to object storage; do not buy a bigger disk twice |
| Out-of-memory kills | Database buffer pool plus workers exceeding RAM | Double RAM — the one upgrade that is usually genuinely needed |
| Video buffering for distant viewers | Serving media from the origin | Put a CDN in front; this reduces cost as well as latency |
Where to go next
These pages carry the detail this answer summarises.
Frequently asked questions
Can I run a SaaS script on shared hosting?
Usually not well. Shared plans commonly forbid long-running processes, restrict cron frequency and limit the extensions you can install, and background workers are how subscription renewals, queued messages and scheduled reports get done. A basic VPS costs about the same and removes the whole class of problem.
Do I need Docker?
No. Docker is convenient for reproducing an environment, but a plain Ubuntu VPS with Nginx, the language runtime and a database is perfectly adequate and easier to debug if containers are unfamiliar. Use whichever you can operate at 2am.
Windows or Linux?
Linux. Effectively every ready-made SaaS package is built and tested on Linux, hosting is cheaper, and the documentation you will need assumes it.
How many customers will a 4 GB server hold?
For a database-light category, several hundred tenants and a few thousand daily users is realistic. The honest answer is that it depends on the query patterns of the specific application, which is why you should watch the slow query log rather than trust any single number.
Get a quote or a guided demo
Tell us your use case and we'll send pricing, a live demo walkthrough and licensing options for SaaS source code. Usually a reply within one business day (IST).