Odoo.sh Hosting Setup & Management

Odoo Online is Odoo's SaaS: the simplest to run, but limited to standard apps and Studio, with no custom Python modules. Odoo.sh adds custom code and a Git-based workflow while Odoo still runs the infrastructure; it's sold to Odoo Enterprise customers, whose subscription must include Odoo.sh, and the hosting fee is separate from the Enterprise licence. Self-hosting, on your own servers or a cloud provider, gives full control over the stack — and full responsibility for security, backups and upgrades.

If you run Odoo Community, plan to self-host it, because Odoo.sh and Odoo Online are sold with Enterprise. The right choice usually follows from your fit-gap analysis: how much custom code and integration you need.

• Odoo Online: standard apps & Studio
• Odoo.sh: custom modules, managed hosting
• Self-hosted: full control & responsibility
• Community edition: self-hosted

Every Odoo.sh project has one production branch, plus staging and development branches. Development branches build a fresh test database and run automated tests on each commit. Staging branches build from a neutralised copy of production — outgoing email and other external actions are disabled — so changes can be tried on real data, and staging databases are temporary, so they're refreshed regularly.

Emails generated on development and staging are kept in a mail catcher rather than sent. Odoo.sh also provides logs in the browser, a web shell and SSH access to each build.

Odoo.sh makes deployment easy; discipline keeps it safe. We work in short-lived feature branches, merge into staging for testing with your key users, and only merge into production once changes are signed off. Module version numbers are raised when data or views change, so the module is updated on deployment.

For larger releases, we take a manual backup first and schedule the merge outside busy hours, with a clear rollback plan if something behaves differently in production.

• Feature branches with automated tests
• Staging sign-off on real data
• Version bumps that trigger updates
• Pre-release backup & rollback plan

Odoo.sh backs up production databases every 24 hours across three data centres and keeps 14 backups for up to three months — daily for a week, weekly for a month and monthly for three months. A backup can be restored into production or a staging branch. Development and staging builds aren't backed up, so nothing important should live only there. We test restores periodically, because a backup only matters if it restores.

Odoo.sh has an Upgrade tab for requesting an upgraded copy of production. The upgraded database is tested on a staging branch with custom modules ported to the new version, and production is only upgraded once that combination works.

Odoo.sh runs the platform, not your application. It doesn't write, review or maintain custom modules, fix failing integrations or scheduled actions, port code at upgrade time, or test your business processes. Choosing workers and storage for your workload is your decision too. That's the gap we fill.