ERP and CRM VPS Sizing: A Step-by-Step Guide for Small Teams

Updated on Nov 20, 2026
Kimberly N
8 MINS READ
Table of Contents
ERP and CRM VPS Sizing

Picking a server for your ERP or CRM is hard when every vendor gives a different minimum. This guide shows you what to measure first, then gives two sizing examples with clear assumptions. The VPS hosting requirements for CRM and ERP change with your team size, your data, and your habits, so there is no single number that fits everyone.

VPS Hosting Requirements for CRM and ERP: A Simple Sizing Guide

Software vendors list a minimum that only proves the app will start. It does not tell you if 15 people can work at the same time without waiting. That is why the VPS hosting requirements for CRM and ERP must start from your own workload.

Two businesses can both have 20 users and need very different servers. One uses the CRM for simple notes. The other runs stock, invoices, and large reports all day. We use Odoo as our example because its docs have clear sizing rules. The same steps work for ERPNext, SuiteCRM, and other tools.

Write Down Your Workload

Before you look at any plan, you must collect six numbers and write them in a simple note:

  1. Concurrent users: People who click at the same moment. This is not the same as total accounts. A common starting guess is 20 to 40% of total users.
  2. Background jobs: Scheduled tasks such as email sync, invoice runs, stock updates, and report builds. They use CPU even when nobody is logged in.
  3. Database growth: How many new records you add per month, and how many files, such as PDFs, scans, and attachments, users upload.
  4. Outbound email: How many emails the system sends per day, such as invoices, quotes, and reminders.
  5. Backup retention: How long you must keep old backups.
  6. Uptime need: How long your team can work without the system.

Check your busiest hour, not an average day. Your server must work well at the busiest time, such as month-end invoicing.

What Your ERP or CRM Needs From Each Server Part

Each part of the server has a different job. Here is how the VPS hosting requirements for CRM and ERP look for CPU, RAM, storage, and network.

CPU Needs for Users and Background Jobs

Your ERP app runs several worker processes. A worker is a process that handles user requests. Odoo's docs give this rule of thumb:

use (CPU × 2) + 1 workers, and plan for about 6 concurrent users per worker.

Background jobs, called cron workers, also use CPU, so you must leave some free CPU for them.

RAM Sizing for Workers and Database

RAM use depends on the number of workers, not only on users. Odoo's docs assume that 80% of requests are light, about 150 MB each, and 20% are heavy, about 1 GB each. That is about 325 MB per worker on average. In a small setup, PostgreSQL and the operating system run on the same server, so you must add RAM for them too.

Heavy reports, big imports, and custom modules can use much more RAM. Treat these numbers as a starting point.

Planning Disk Space for Growth

You must use NVMe or fast SSD storage, because databases do many small reads and writes. Plan your disk like this:

  • Operating system and app: 15–25 GB.
  • Database: today's size plus 12 months of growth.
  • File uploads: attachments, scans, and PDFs.
  • Local backup space: at least one fresh dump of the database.
  • Free space: keep 25–30% free so the server never fills up.

Network and Email Needs

Your ERP or CRM does not need a huge network port. Normal use sends small pages and files.

Email is the part that needs care. Do not send bulk email straight from the VPS IP address. You must use an SMTP relay or a mail service, and check if your provider limits port 25. Port 587 with login is the common safe choice.

ERP and CRM VPS Sizing Examples

These are examples, not promises. They show how the VPS hosting requirements for CRM and ERP change with team size. They assume one server runs the app, PostgreSQL, and a web proxy such as Nginx. Always test with your own data.

Item Small team Medium team
Total users 10–25 40–100
Concurrent users Up to 10 Up to 30
Workers (about 6 users each, minimum 2) 2–3 5–6
vCPU 2 4
RAM 4 GB (8 GB if you run big reports) 8–16 GB
NVMe storage 60–80 GB 120–160 GB
Database size assumed Under 5 GB 10–30 GB
Email per day Under 200 Under 1,000
Background jobs A few light jobs Daily jobs plus imports

Here is the math for the medium team:

# Workers: 30 concurrent users ÷ 6 users per workerecho $((30 / 6))              # 5 workers # App RAM: 5 workers × 325 MBecho $((5 * 325))             # 1625 MB (about 2 GB) # PostgreSQL cache: 25% of 8 GBecho $((8 * 1024 * 25 / 100)) # 2048 MB (2 GB) # Operating system: about 1 GB# Total: 1.6 + 2 + 1 = about 4.6 GB

The total is about 4.6 GB, so it fits in 8 GB. Choose 16 GB if you want space for reports and growth.

These numbers are only a starting point. Real needs change with your data, your reports, and your custom modules, so testing matters more than any table.

How to Pick a VPS Plan

When you compare plans, you must match them to your worksheet, not only to the price. Treat the VPS hosting requirements for CRM and ERP as a checklist for each offer. A plan with 2 vCPU, 4 GB RAM, and NVMe storage can suit the small example. A plan with 4 vCPU and 8 GB RAM is a good place to start for the medium team.

If you plan to host on Linux, a Linux VPS with NVMe storage and full root access gives you the control you need to set up workers, PostgreSQL, and backups yourself. Remember that a basic plan uses shared CPU, while reserved CPU gives steadier speed during busy hours. Pick based on your test results.

Backup and Uptime Planning

Backups are a key requirement for VPS hosting for CRM and ERP. If you never test a restore, you can't trust the backup. Plan these two values:

  • RPO: How much data you can afford to lose, for example, one day.
  • RTO: How long you can afford to be down while you restore.

A simple retention plan for a small business is to keep 7 daily, 4 weekly, and 6 monthly backups. Store them off the server, because a backup on the same disk fails with the disk. For the database, use pg_dump for daily copies:

Bash
sudo -u postgres pg_dump -Fc mydb > /backup/mydb_$(date +%F).dump

Do not forget the file store, where uploaded files are kept. Back it up together with the database. If you don't, your restore will have missing attachments. Check whether your host offers snapshots or daily backups, but keep your own copy as well.

Now you must check your uptime goal. A 99.9% monthly target allows about 43 minutes of downtime in a 30-day month. If your team can't accept that, you need a second server and a failover plan. A bigger VPS won't fix it.

Test Your VPS Before You Choose an OS

Only a real test can prove the VPS hosting requirements for CRM and ERP. Run it on a test server with a copy of your real data. Use these pass rules as a starting point:

  1. Common pages load in under 2 seconds with your expected number of users.
  2. CPU stays below about 70 to 75% in the busy hour.
  3. RAM has free space, and the server does not use swap.
  4. A full report or large import does not freeze the other users.
  5. Email sends without delay.
  6. You can restore a backup on a clean server within your RTO.

Useful commands during the test include:

Bash
free -h        # memory and swaptop            # CPU and processesdf -h          # disk spaceiostat -x 5    # disk load (install the sysstat package)

To test the load, use a tool such as k6 or Locust. These tools act like many users at the same time.

Linux vs Windows VPS

Your OS choice also shapes the VPS hosting requirements for CRM and ERP. Choose the OS your software needs.

Odoo, ERPNext, and SuiteCRM are commonly run on Linux, and Linux has no license fee. Windows makes sense if your ERP or CRM only runs on Windows, such as a .NET app or a SQL Server-based product, or if your team only knows Windows. Windows uses extra resources and adds a license cost, so test it with the same checklist. For a Linux-based ERP, Ubuntu LTS or Debian is a simple and safe choice.

When a VPS Is Not Enough

For most small teams, a VPS is enough to meet the VPS hosting requirements for CRM and ERP.

Consider a bare metal server if your database gets very large, CPU stays high all day, or you need full hardware for strict isolation. It can also help when you outgrow one VPS and want a separate database server. 

Conclusion

You must choose your VPS based on your busiest hours, data size, and daily tasks, not just the price. Plan enough CPU, RAM, and storage, and keep backups off the server. Test with your own data before you commit, including a full backup restore. Start with a plan that meets your needs, then upgrade as your business grows.