Choosing the right infrastructure for your Odoo deployment is crucial for ensuring smooth performance, future scalability, and cost-efficiency. Whether you are starting with a small team of 10 users or managing 150+ users across multiple departments, this updated 2026 guide for Odoo 19 Enterprise will help you design a solid server architecture that supports your business goals.
Odoo server requirements depend on concurrent activity, installed apps, background jobs, database size, and attachments. Use the hardware table below as a starting point for production planning, not as an official minimum or a guarantee of capacity. A test installation and a business-critical production system have different requirements.
Choosing the Right Deployment: Odoo Online, Odoo.sh, or On-Premises
When implementing Odoo, businesses usually face three deployment options:
Odoo Online:
Ideal for small companies who want a fast setup with standard functionality and no technical management overhead.
However, it has limited customization capabilities and relies on Odoo's managed hosting environment.
Odoo.sh:
An option for companies that need custom modules, staging environments, deployment workflows, and managed backups.
Compare total operating costs, including infrastructure, administration, backups, and support, rather than server rental alone.
On-Premises or Dedicated Cloud Hosting:
Recommended for companies with complex business processes, high customization needs, large user bases, or specific security requirements.
This option provides full control over the infrastructure, allowing advanced performance tuning, security hardening, and scalability.
✅ Tip: If you anticipate major customizations or high database loads (e.g., ecommerce, manufacturing operations), we recommend starting with a dedicated environment from day one.
Professional Odoo Hosting Benefits
Our hosting service offers:
- Full root access to your server (no hidden limitations).
- Daily automated backups with off-site replication.
- Monitoring systems to predict potential issues before they affect users.
- Scalability options — CPU/RAM upgrades without downtime.
- High Availability (HA) setups for mission-critical environments.
✅ We can provision a ready-to-run Odoo server within 24–48 hours, tailored to your specific needs.
Updated Odoo Server Hardware Requirements
Odoo 19 system requirements: the official source-install documentation specifies Python 3.10 or later and PostgreSQL 13 or later. These are compatibility minimums, not recommended production versions. PostgreSQL 13 reached end of support in November 2025; choose a maintained PostgreSQL version and validate the complete stack with your modules. PostgreSQL 15 remains supported in 2026. The official Odoo 19 Debian package targets Ubuntu 24.04 LTS; source installations require their own dependency checks. PDF reports with headers and footers require the documented wkhtmltopdf 0.12.6 package.
Enterprise uses the Community server with additional Enterprise add-ons. Size the server for the apps and workload you actually run; the edition name alone does not determine CPU or RAM. Sources: Odoo 19 source installation, packaged installation, and PostgreSQL version support.
Recommended planning ranges: the user bands below refer to team size, not simultaneous requests. They assume routine business activity; imports, manufacturing calculations, large reports, ecommerce traffic, and integrations can change the requirements substantially. For a single server, RAM must cover Odoo, PostgreSQL, and the operating system. For separate servers, size each role independently.
| Criteria | Up to 10 Users | Up to 50 Users | More than 50 Users |
|---|---|---|---|
| CPU | 4 cores | 6–8 cores | 8–16 cores |
| RAM | 8 GB | 16–32 GB | 32–64 GB |
| Storage (SSD) | 50 GB | 100–160 GB | 200+ GB |
| Database | PostgreSQL 15+ | PostgreSQL 15+ | PostgreSQL 15+ |
| Operating System | Ubuntu 24.04 LTS | Ubuntu 24.04 LTS | Ubuntu 24.04 LTS |
| Notes | Use SSD, regular backups, performance monitoring | Consider separate app and DB servers if measurements justify it | Assess workload, availability targets, and scaling needs |
✅ Tip: Treat 20% spare storage as an initial buffer, not a complete capacity plan. Budget separately for PostgreSQL, the filestore (attachments and documents), logs, temporary files, retained backups, and staging copies. Adjust headroom to measured growth and retention requirements.
✅ Tip: Monitor continuously with alerts and review capacity regularly. Investigate sustained memory pressure, swap activity, worker restarts, slow requests, and disk latency before deciding which resource to upgrade; RAM utilization alone is not enough.