Odoo VPS Requirements: CPU, RAM, Workers & PostgreSQL Sizing Guide

Odoo VPS requirements should be sized around concurrent users, workers, PostgreSQL memory and custom modules — not employee count. Odoo’s official deployment documentation gives a useful rule of thumb for multi-process deployments: roughly (CPU × 2) + 1 as a theoretical worker ceiling, with approximately one worker per six concurrent users in its example guidance. It also provides a memory-estimation model for light and heavy requests.

VPSWala’s current Odoo hosting page uses an 8 GB VPS as a practical starting point for a modest deployment with up to about ten concurrent users and scales upward as user count grows. Treat that as a commercial starting point, then validate it with your modules and database.

Odoo VPS sizing at a glance

How Odoo worker sizing works

Odoo 19’s production deployment documentation describes multi-processing as an opt-in configuration using --workers. Its rule of thumb is:

theoretical max workers ≈ (CPU × 2) + 1

The same guidance uses roughly one worker per six concurrent users as a planning approximation. Cron workers also consume CPU. This is a rule of thumb, not a capacity guarantee: custom modules, integrations, reporting and long-running requests can change the result substantially.

How much RAM does Odoo need?

Odoo’s documentation estimates lighter workers around 150 MB and heavy workers around 1 GB in its example model, with an assumed mix of 80% light and 20% heavy requests. That gives a framework for estimating application memory, but PostgreSQL, the operating system, caching, reverse proxy and background jobs also need RAM.

Do not allocate every gigabyte to Odoo workers. Leave headroom and monitor actual resident memory.

PostgreSQL matters as much as Odoo

Odoo uses PostgreSQL. A server can have enough CPU for application workers and still feel slow if PostgreSQL is memory-starved or storage latency is high. Monitor:

• database size and growth;
• slow queries;
• cache hit rate;
• storage latency;
• connection count;
• backup duration.

4 vCPU / 8 GB: when it is enough

VPSWala positions its 4 vCPU / 8 GB / 80 GB RAID NVMe tier as a starting point for a modest Odoo deployment. It can be reasonable for a small team with ordinary modules and limited concurrency.

It may be too small if the business uses many custom modules, heavy reports, ecommerce, manufacturing workflows, large attachments or multiple integrations.

When to choose 16 GB or 32 GB

Add memory when the application working set and PostgreSQL cache no longer fit comfortably. Add CPU when worker queues and sustained CPU utilisation show that concurrency is the problem. Do not increase both blindly.

Odoo production security

Odoo’s official deployment documentation recommends running production behind a reverse proxy with HTTPS and properly configuring proxy mode. It also recommends restricting database-management routes and using a strong administrative master password.

For a public VPS:

• keep Odoo and the OS updated;
• put HTTPS termination in front;
• restrict SSH administration;
• protect database-management interfaces;
• use a non-superuser PostgreSQL role for the application;
• monitor login abuse and unusual requests.

Backups

Back up both the PostgreSQL database and Odoo filestore/attachments as a consistent recovery set. Keep an independent off-server copy and test restoration. A VM snapshot by itself is not a complete application-consistent backup strategy.

Odoo VPS or dedicated server?

Stay on VPS when demand is moderate and the ability to resize is valuable. Compare dedicated hardware when CPU is continuously saturated, storage I/O is highly sensitive, RAM requirements become large or the business needs stronger single-tenant isolation.

Odoo VPS checklist

1. Count concurrent users, not total staff.
2. List custom modules and integrations.
3. Measure current CPU and database load.
4. Estimate workers, then validate in production.
5. Leave RAM for PostgreSQL and the OS.
6. Use HTTPS and secure database management.
7. Back up database + filestore together.
8. Monitor and resize from evidence.

Bottom line

Odoo VPS sizing starts with concurrent users and worker requirements, but PostgreSQL and custom modules often decide the real server size. An 8 GB VPS is a reasonable starting point for a modest deployment; scale when measurements prove that CPU, memory or storage is constrained.

Next step: compare VPSWala Odoo hosting and the full VPS catalogue.

Sources

• Odoo 19 production deployment/system configuration
• VPSWala Odoo hosting
• VPSWala VPS catalogue