Quick answer: Cloud Server for Odoo, ERP or database workloads should not be selected from CPU/RAM pricing alone. Size it by concurrent users, modules, reports, imports, integrations, database growth, backup and restore requirements, and operations ownership. A small Odoo/ERP system may start on a 4 vCPU / 8GB RAM / NVMe VPS. As users, reports and accounting or inventory data grow, the better path may be a split application/database architecture, Dedicated Server or Private Cloud.
Why ERP hosting is different from normal website hosting
A brochure website is mostly traffic-driven and caching can absorb many requests. Odoo, ERPNext and custom ERP applications behave differently. Users stay logged in all day, open multiple tabs, create sales orders, update inventory, export reports, run cron jobs, send email, call external APIs and constantly read or write PostgreSQL. The bottleneck is often not pure CPU. It can be RAM pressure, weak disk I/O, database locks, wrong worker settings, backup jobs during business hours or slow reporting queries.
The common mistake is to treat ERP like a heavier website. It may run during the first month, then slow down when records, attachments and reports grow. The right cloud decision starts from workload ownership, not from buying the largest package.
What must be included in an ERP server estimate?
- Application layer: Odoo, ERPNext or custom application, workers, long-polling, cron and custom modules.
- Database layer: PostgreSQL, MariaDB, MySQL or MSSQL, database size, indexes, reporting queries and connections.
- Files and attachments: invoices, documents, images, imports, PDF reports and monthly growth.
- Reverse proxy: Nginx or Apache, SSL, upload limits and static asset handling.
- Backup: database dump, snapshot, filestore, source code, configuration and offsite copies.
- Monitoring: CPU, RAM, disk, I/O, services, slow queries, backup status and capacity alerts.
Reference sizing table
| Need | Reference resources | Suggested architecture | Operations note |
|---|---|---|---|
| Pilot or light usage | 2-4 vCPU / 4-8GB RAM / NVMe | Application and database on one VPS | Good for validation, not high availability |
| SME production | 4 vCPU / 8-16GB RAM / NVMe | Optimized single VPS or planned DB split | Needs monitoring, offsite backup and restore tests |
| Multi-department or heavy reporting | 8 vCPU+ / 16-32GB RAM+ | Separate app server and database server | Review slow queries, workers, I/O and backup window |
| Core ERP platform | Dedicated Server or Private Cloud | Separated app, DB, backup and replica layers | Requires RPO/RTO, security ownership and DR plan |
One server or a separate database server?
For smaller businesses, keeping the ERP application and PostgreSQL on one VPS is simpler and cheaper. It is acceptable when RAM headroom is clear, disk is fast, worker settings are controlled and backup does not block the system during office hours. This is usually the starting point for pilots and small teams.
When database size, reporting, custom modules or external integrations grow, the database should be treated as a separate layer. Splitting the database allows better RAM and I/O allocation, less competition with application workers, cleaner backup or point-in-time recovery planning and a clearer upgrade path toward Dedicated Server or Private Cloud.
Configuration mistakes that make ERP slow
- Running production ERP on 2GB RAM while enabling too many workers.
- Putting web, database, backup, mail and extra apps on the same VPS without capacity checks.
- Watching CPU only and ignoring disk I/O or database locks.
- Saving database backups on the same production disk with no offsite copy.
- Never testing restore, then discovering that filestore or custom modules are missing.
- Leaving SSH/RDP and admin accounts unmanaged.
- No staging environment for updates before production changes.
Backup requirements for Odoo and ERP
ERP backup is more than a virtual machine snapshot. At minimum, protect the database, filestore or attachments, custom modules, configuration files and version information. For important databases, define RPO and RTO: how much data the business can lose and how long the ERP can be down during restore. If those numbers are unknown, the backup design is not complete.
Important workloads need offsite backup, clear retention, failed-backup alerts and scheduled restore tests. See Cloud Backup for business if backup and restore ownership must be part of the hosting plan.
When VPS is no longer enough
VPS fits moderate workloads with predictable growth. When ERP becomes a core business platform, many branches use it at once, reports are heavy, private networking is required, HA/DR matters or database I/O must be more predictable, consider Dedicated Server or Private Cloud. The goal is not to buy the biggest server, but to choose the right infrastructure layer before urgency forces a rushed migration.
Checklist to request an accurate recommendation
- Software name: Odoo, ERPNext, custom ERP, PostgreSQL, MySQL or MSSQL.
- Total users and concurrent users during peak hours.
- Database size, filestore size and monthly growth.
- Heavy modules: accounting, inventory, manufacturing, sales, POS or BI/reporting.
- Import/export schedules, API integrations, cron jobs and background tasks.
- Backup requirements: RPO, RTO, retention, offsite copy and restore-test frequency.
- Need for staging, VPN, IP whitelist, admin access rules and operations reporting.
Recommended next pages
If you are still estimating resources, review VPS configuration advice and VPS Cloud pricing. If you already have a workload to quote, use the Cloud VPS order page. For the broader infrastructure option, see Cloud Server/VPS for business.
Frequently Asked Questions
Can Odoo run on a VPS?
Yes. Many SME deployments can start on VPS if RAM, NVMe storage, backup and operations ownership are handled properly. ERP should not run on a very small or unmanaged VPS without monitoring.
Should PostgreSQL run on a separate server?
Separate it when the database is large, reports are slow, concurrent users increase, integrations grow or backup/PITR requirements become stricter. A database server can be tuned and scaled independently.
How is Cloud Server different from Dedicated Server for ERP?
Cloud Server is flexible and easy to start. Dedicated Server is better when resource isolation, stronger I/O, large database workload or predictable long-term cost matters more.
Need a server recommendation for Odoo or ERP?
Send your workload, user count, database size, backup schedule and RPO/RTO requirements. IT Systems can recommend VPS, Managed VPS, Dedicated Server or Private Cloud based on actual operations risk.
