Odoo Server Requirements in 2026 - The Definitive Guide

Undersize your Odoo server and you get slow page loads, failed report generation, and frustrated users. Oversize it and you pay for resources you never touch. This guide gives you concrete numbers for every deployment size, from a solo freelancer testing Odoo on a $4 VPS to a 500-user enterprise running a multi-server cluster.

These numbers apply to Odoo 18 (the LTS stream through October 2027), Odoo 19, and Odoo 20 (the current major release, shipped 2026-09-24). CPU, RAM, and storage sizing is nearly identical across the three. The software baseline is where Odoo 20 differs: it needs Python 3.12 or later, PostgreSQL 16 or later, and the pgvector extension for embedding and AI features. If you are still running Odoo 16 or 17, the hardware numbers below still hold. Older versions use slightly less RAM but more CPU due to less efficient ORM queries.

Minimum Requirements (Odoo 18/19/20)

The bare minimum to install and run Odoo on a single server with PostgreSQL. The hardware numbers are the same across v18, v19, and v20. Odoo 20 raises the Python and PostgreSQL baseline and adds the pgvector extension.

Odoo 20 Baseline Changes

Odoo 20 shipped on 2026-09-24 as the current major release. CPU, RAM, and storage sizing is unchanged from v18 and v19 for a given user count. Three software baselines moved up:

If you are migrating a running v18 or v19 instance to v20 on the same server, the fastest path is: upgrade PostgreSQL to 16 if needed, install Python 3.12, install the postgresql-16-pgvector package, and enable the extension inside each Odoo database with CREATE EXTENSION IF NOT EXISTS vector;. For a step-by-step install, see our Odoo Ubuntu install guide.

Requirements by User Count

The most common way to size an Odoo server is by user count. “Users” here means concurrent active users - not total user accounts. If you have 100 user accounts but only 30 people are logged in and active at peak hours, size for 30. A good rule of thumb: concurrent users are typically 25-40% of total registered users.

Each Odoo worker process handles one request at a time and consumes 150-300 MB of RAM. The formula is simple: you need 1 worker per 4-6 concurrent users, plus 1-2 cron workers for background tasks. PostgreSQL needs its own share of RAM (at least 25% of total) and connections (at least 2x the number of workers).

All tiers assume Odoo Community or Enterprise with a typical mix of modules. If you run heavy modules like MRP or eCommerce, add 50-100% more RAM. See the module-specific section below.

The 100-user threshold is where single-server setups start struggling. At this point, PostgreSQL and Odoo compete for CPU and RAM on the same machine. Separating the database onto a dedicated server (or using a managed PostgreSQL service like AWS RDS or DigitalOcean Managed Databases) dramatically improves response times. The Odoo application server can then use all available RAM for workers, while PostgreSQL gets its own dedicated resources for query caching and connection handling.

Use our server calculator to get a personalized recommendation based on your exact user count and module selection, or check the server requirements tool for quick reference.

Requirements by Module

Not all Odoo modules hit the server the same way. A company using only CRM and Invoicing has very different server needs than one running Manufacturing, eCommerce, and Point of Sale at the same time. Here is how the major modules affect your resource budget:

If you are running multiple resource-heavy modules, add their extra requirements together. A company using Accounting + MRP + eCommerce should plan for 2 extra vCPUs (Accounting) + 4-8 GB extra RAM (MRP) + NVMe storage and CDN (eCommerce) on top of the base requirements for their user count.

PostgreSQL Sizing Guidelines

PostgreSQL does the heavy lifting for Odoo. Every page load, every search, every report hits the database. Get this wrong and your whole instance suffers no matter how much CPU and RAM you give the Odoo application server.

Connection pooling becomes critical beyond 50 users. Odoo opens one PostgreSQL connection per worker, and each connection uses 5-10 MB of RAM on the database server. Without a connection pooler, 16 workers with 2 connections each means 32 database connections at all times. Use PgBouncer in transaction pooling mode to multiplex connections - it can serve 100+ Odoo workers through 20-30 actual PostgreSQL connections, reducing database memory usage by 60-70%.

For a deeper dive into PostgreSQL configuration, see our PostgreSQL Tuning for Odoo guide, which covers indexing strategies, autovacuum tuning, and query optimization specific to Odoo workloads.

Storage Planning

Odoo storage has three components: the database, the filestore, and system overhead. Here is how each one grows over time:

The filestore is where Odoo stores file attachments, product images, report PDFs, and email attachments. By default, these are stored on the local filesystem in ~/.local/share/Odoo/filestore/. For larger deployments, moving the filestore to S3-compatible object storage (AWS S3, DigitalOcean Spaces, MinIO) saves disk space and makes backups simpler.

NVMe vs SATA SSD: Always choose NVMe when available. PostgreSQL is I/O-heavy, and NVMe drives provide 3-5x better random read performance than SATA SSDs. The performance difference is most noticeable on reports and searches that scan large tables. Every major VPS provider now offers NVMe as standard or as an affordable upgrade.

Always leave 20% free disk space. PostgreSQL needs free space for VACUUM operations (which reclaim dead tuples), WAL files, and temporary sort files. If your disk hits 95%+ utilization, PostgreSQL can refuse new writes and your Odoo instance will crash.

Network Requirements

Network bandwidth and latency tend to get ignored when sizing Odoo servers. Here is what you actually need:

Development vs Staging vs Production

Running three environments (development, staging, production) is standard practice. But you do not need to triple your server costs. Each environment has a different job and different resource needs:

Pro tip: Development environments can run on the cheapest VPS tier your provider offers. A Hetzner CX22 at ~4 EUR/month or a DigitalOcean $6/month droplet is more than enough for a single developer. Staging should mirror production in software configuration (same Odoo version, same modules, same PostgreSQL version) but can use a smaller instance size. For detailed staging setup, see our Odoo staging environment guide.

Cloud Provider Recommendations by Budget

Now that you know your server specs, here is where to run them. We tested seven providers head-to-head and wrote a detailed comparison. Here is the quick summary:

For region-specific recommendations, see our guides for Europe, India, and other regions. For VPS-specific sizing advice, check our best VPS for Odoo guide.

Frequently Asked Questions