Odoo will start on almost any server, so a production setup can be wrong without anyone noticing. Nothing breaks on day one. Problems show up months later as a slow month-end close, a backup that can't be restored, or an upgrade that takes the whole company offline for a weekend. These do's and don'ts come from running Odoo instances every day. They apply whether you host Odoo yourself or with a provider; for a comparison of the hosting options themselves, see how to host Odoo.
Performance
Do: run Odoo with workers
Out of the box, Odoo runs as a single process with threads, which is fine for development and poor for real use. In production, set workers in the configuration so Odoo serves requests from several processes. Odoo's deployment documentation suggests about two workers per CPU core plus one as a starting point, and roughly six concurrent users per worker. Concurrent means working at the same moment, so the total number of users per worker is higher. Adjust from what you measure.
Do: set memory and time limits
Give each worker sensible limits with limit_memory_soft, limit_memory_hard, limit_time_cpu and limit_time_real. Odoo's defaults (60 seconds of CPU time, 120 seconds in total per request) suit small setups; raise them only as far as your longest legitimate report or import needs, and size the memory limits to the server. Our guide to Odoo server configuration walks through these settings in odoo.conf.
Don't: size the server by guesswork
Watch CPU, memory and database connections for a few weeks before adding capacity. A slow instance is often one badly written module or a missing database index, not a small server.
Security
Do: put Odoo behind HTTPS and a reverse proxy
Serve Odoo through a reverse proxy such as Nginx with a valid TLS certificate, and turn on proxy_mode so Odoo trusts the forwarded headers. Never send logins over plain HTTP.
Do: lock down the database manager
Set a strong admin_passwd (the master password), and set list_db = False so the database list and manager pages aren't public. Use dbfilter so each domain only reaches its own database.
Don't: run Odoo or PostgreSQL as root, or expose PostgreSQL
Run Odoo under its own system user, and keep PostgreSQL reachable only from the Odoo server, not from the internet.
Backups
Do: back up the database and the filestore together
An Odoo backup is two things: the PostgreSQL database and the filestore, where attachments, images and documents live. A database dump on its own restores an Odoo that is missing every attached file.
Do: keep a copy off the server
A backup on the same machine disappears with the machine. Send copies to separate storage, such as an S3 bucket, Google Drive or an SFTP server, and keep several days or weeks of history.
Don't: trust a backup you have never restored
Restore a recent backup into a test instance from time to time. It is the only way to know it works, and how long a real recovery would take.
Changes and upgrades
Do: test on staging first
Install new modules, try configuration changes and rehearse upgrades on a copy of production, with real data, before touching the live instance.
Do: keep custom code in Git
Store your custom and third-party modules in a Git repository, and deploy from a branch. You always know which version is running, and rolling back is a matter of deploying the previous commit.
Don't: edit Odoo's core code
Changes to Odoo's own files are lost on the next update and make upgrades painful. Extend Odoo with a module that inherits what you need to change.
Don't: leave version upgrades for years
Odoo supports each major version for three years, the current one and the two before it. Plan upgrades as projects, one version at a time, rather than jumping several versions at once under pressure.
Day-to-day operations
Do: read the logs
Failed scheduled actions, missing Python dependencies and slow queries all show in the server log before users notice them. Keep logs searchable and check warnings and errors regularly.
Do: configure outgoing mail properly
Invoices and notifications need a real SMTP server with the right sender domain, or they end up in spam. Test the connection after any change.
Don't: install modules without checking their dependencies
Many community modules need Python packages or other modules first. Read the manifest, install what it needs, and try it on staging.
A short checklist
| Area | Before you go live |
|---|---|
| Performance | Workers and memory limits set; usage monitored |
| Security | HTTPS, proxy mode, master password, database list hidden |
| Backups | Database and filestore, off-site copy, restore tested |
| Changes | Staging copy, modules in Git, no core edits |
| Operations | Logs reviewed, outgoing mail tested |
Where Easy Instance takes this off your hands
On Easy Instance, most of this list is already done when an instance starts: SSL and the reverse proxy, the Odoo server configuration, daily backups, monitoring and logs. You still decide the parts that are yours, such as which modules to install and when to upgrade, with a one-step staging copy to test them, GitHub deploys, and backup copies to your own storage. Try it free for 10 days.