Usage load
Concurrent users, transactions, reports, scheduled jobs, and active integrations.
Pricelist
Odoo is installed and made ready to use. Server capacity and technical configuration are based on actual requirements, not simply the cheapest package.
Capacity planning
Before installation, requirements are mapped to determine sensible vCPU, RAM, storage, and service configuration. The result is enough capacity for the workload without paying for resources that are not yet needed.
Assessment output
Initial capacity recommendation, service design, backup requirements, and growth headroom.
Concurrent users, transactions, reports, scheduled jobs, and active integrations.
Odoo worker count, memory limits, timeouts, and background processing needs.
Current database and filestore size, data growth, and backup retention period.
Service hours, downtime tolerance, recovery needs, and room for growth.
Technical scope
More than running an installer. Each component is prepared as one Odoo service that can be operated and maintained.
Reverse proxy, HTTPS/SSL, proxy headers, timeouts, and request limits aligned with Odoo.
Services, workers, proxy mode, memory limits, and logs sized for server capacity.
Connections, memory, and baseline database parameters aligned with application load.
Firewall, SSH access, system updates, and service permissions restricted as needed.
Schedules, retention, off-site storage, and recovery tests are available by package.
Uptime checks and incident notifications are available with the selected package.
Basic
Rp500.000
one-time payment
Covers the initial installation.
Standard
Rp750.000
one-time payment
Safer for production use.
Standard
Rp140.000
/ monthRp1.680.000 / year
For initial needs and standard usage.
Recommended
Rp200.000
/ monthRp2.400.000 / year
More room for growth and usage spikes.
Server recommendation basis
Recommendations are prepared through capacity assessment and service configuration design, covering the Nginx web server, Odoo application processes, database, storage, backup, and monitoring. Final sizing considers operational needs, usage patterns, data volume, and room for growth. Detailed calculations and technical configuration are determined during implementation.
Annual estimates use the current monthly rate × 12. Server prices may change; final pricing is confirmed when ordering.
Domain + SSL
Based on requirements
Server maintenance
IDR 500,000–1,000,000/month
Separate backup storage
Based on required capacity
Technical proof
How I investigate Odoo performance, choose server architecture, and handle large databases. Articles are in Indonesian.
2,8 menit → 9 detik
A PostgreSQL bottleneck resolved without changing application logic.
Read case studyOdoo 17 / 18 / 19
Architecture notes covering Python isolation, ports, and databases for multiple instances.
Read case studyDatabase puluhan GB
An analysis of I/O, virtual disk capacity, memory, and parallel restores for a large database.
Read case studyKetik untuk mulai mencari...