Odoo Online
A private database that Odoo hosts and manages, reached through a web browser. Customization covers changes that need no custom code.
Certified Odoo Implementation Partner
Odoo can be hosted three ways: Odoo Online (Odoo manages a standard database for you), Odoo.sh (Odoo's cloud platform for projects with custom code) or a server you control. A Canadian business chooses by answering three questions: whether it needs custom modules, who will run updates and backups, and how much control it needs over where the data is stored.
Solvync is a Certified Odoo Implementation Partner based in Calgary. We implement and support Odoo on the hosting the client chooses, and the comparison below follows the Odoo 20.0 documentation.
Three ways to host Odoo
A customer's security questionnaire arrives, and one line asks which country stores your data. The accounting server is in the back room, and the person who used to patch it has left. Hosting decides how you answer that line.
A private database that Odoo hosts and manages, reached through a web browser. Customization covers changes that need no custom code.
Odoo's official cloud platform, with code in a GitHub repository and production, staging and development branches.
Odoo's documentation calls this on-premise. A server rented in a Canadian cloud region counts, and your team carries the updates, backups and security.
Comparison table
Each cell comes from the Odoo 20.0 documentation or from Odoo's privacy policy.
| What you are comparing | Odoo Online | Odoo.sh | Self-hosted (on-premise) |
|---|---|---|---|
| Custom modules | Incompatible with custom modules and with modules from the Odoo Apps Store. | Supported, with the code in a GitHub repository. | Supported on your installation. |
| Versions available | Major versions and the intermediary versions released every two to three months. | Major versions only, such as 20.0. | Major versions only, such as 20.0. |
| Who runs updates | Odoo, automatically. | Odoo, automatically. | You, by reinstalling the latest revision on your server. |
| Who runs backups | Odoo, daily, under its Cloud Hosting SLA. | Odoo, daily for production. Seven daily, four weekly and three monthly backups are kept. | You. Odoo's guide lists daily backups copied to a separate archiving server. |
| Staging environment | Up to five test duplicates, each expiring after 15 days. | Staging branches build neutralized duplicates of the production database. | You build it, by duplicating production into a neutralized test database. |
| Data location control | The Odoo cloud region closest to you. A change of region can be requested. | You select the hosting region when the project is deployed. | You choose the provider, the region and the backup location. |
| Best fit | Standard apps and no server to run. | Custom modules tested in staging, on a platform Odoo runs. | A written requirement to control the server, and people to operate it. |
Odoo subscription prices are on the Odoo pricing in Canada page.
Decision
Start with custom code, because that one answer removes Odoo Online from the list or keeps it there. Then ask who will carry the operations work.
The Odoo Standard vs Custom page covers the custom code question.
Worked example
This scenario is illustrative. It describes no client.
A distributor in Western Canada runs accounting and stock on a server in its warehouse office. Its largest customer wants every order confirmed through a purchasing portal, which calls for one custom module, and has sent a questionnaire asking where the distributor's data is stored.
The portal connection is a custom module, and Odoo Online is incompatible with custom modules.
Odoo Online is ruled out.
The distributor has no IT staff, so updates, backups and security would fall to the controller.
Self-hosting is ruled out.
On Odoo.sh a staging branch runs the module against a neutralized duplicate of production before release.
Odoo.sh fits.
The distributor selects a hosting region at deployment and asks Odoo to confirm the production country and backup locations in writing. That reply goes into the questionnaire.
Data location
Read on November 18, 2026 on odoo.com and on the Privacy Commissioner of Canada's website.
Odoo's privacy policy, effective September 24, 2026, lists five cloud hosting regions. The Americas region names the United States and Canada as production locations, with backups in Europe (France and the Netherlands) and Canada.
A database is hosted in the region closest to the customer, and backup locations cannot be chosen or restricted. A buyer with a Canada-only requirement should get the production country and backup locations from Odoo in writing before signing.
PIPEDA applies to private-sector organizations across Canada that collect, use or disclose personal information in commercial activity. Alberta, British Columbia and Quebec each have a private-sector privacy law.
The Privacy Commissioner's guidelines state that PIPEDA does not prohibit transferring personal information to another jurisdiction for processing, and that the transferring organization stays accountable for it. Regulated sectors and public bodies can carry stricter residency terms. Treat this as general information and take the legal question to your counsel.
Changing hosting
Odoo documents a path between every pair of hosting types. A hosting move is separate work from a version upgrade.
If you may leave Odoo Online later, start on a major version. The Odoo version upgrade page covers the upgrade an intermediary version needs first.
Common Questions
Short answers for Canadian owners, controllers and IT leads.
Bring the security questionnaire and the list of what your team has customized. You leave the call with one of the three hosting options named and the questions to send Odoo in writing. On Monday the back-room server has a retirement date and the questionnaire has an owner.