Many companies spend months choosing their Odoo modules, then settle the hosting question in a single meeting. It should be the other way round. The hosting model determines what you are allowed to develop, who backs up your data, how fast you can move to a new version, and what you will have to negotiate the day you want to leave.
This guide compares the four models without inventing prices: where an amount depends on your context, we list the cost items to quantify and point to public price lists and to quotes. Statements about Odoo’s offers come from the official documentation and pages consulted on 20 November 2026.
The four hosting models
Odoo Online: the SaaS
Odoo hosts, runs and backs up a private database accessible from a browser. According to the Odoo Online documentation, the platform is incompatible with custom modules and with those from the Odoo Apps Store, and databases are backed up daily in line with Odoo’s cloud hosting SLA. Version upgrades are launched from the database management interface.
The trade-off is clear: zero operations, but zero custom Python code. Customization goes through configuration and Odoo Studio.
Odoo.sh: the PaaS
Odoo.sh is the vendor’s official cloud platform for teams that develop. The Odoo.sh documentation describes shell access, continuous integration, branch management, automated backups, GitHub integration, hosting of custom modules and upgrade management.
It is the middle ground: Odoo still manages the infrastructure, but your code, versioned in your own repository, runs on the platform. You remain responsible for the quality of that code.
The partner host
This is an integrator or hosting provider that installs Odoo (usually Community, or Enterprise under licence) on its own infrastructure, with its own operations team, and bills you for a managed service. This model is not described in Odoo’s documentation because its terms depend on each provider: everything is decided in the contract. Its main appeal: a choice of location, a single point of contact for both functional and technical matters, and often negotiable service commitments.
On-premise and private cloud
You install Odoo on your own servers, or on IaaS infrastructure that you administer (OVHcloud, Scaleway, AWS, Azure). According to Odoo’s official hosting types page, customization is fully possible and the data stays under your control, but you must maintain the entire infrastructure and have advanced technical skills.
What each model allows or rules out
| Question | Odoo Online | Odoo.sh | Partner host | On-premise / private cloud |
|---|---|---|---|---|
| Custom Python code | No | Yes | Yes (depending on contract) | Yes |
| Third-party modules (Apps Store, OCA) | No | Yes | Yes | Yes |
| Direct database access | No | Depends on the platform (shell, backups) | Depends on contract | Full |
| Version choice | Driven by the vendor | You decide, with support | You decide | You decide |
| Test environments | Limited duplicates | Dev, staging and production branches | To be set in the contract | To be built |
Third-party modules and custom code
This is the sharpest dividing line. If your requirements include a custom connector to a WMS, an industry-specific module, or a commission calculation that Studio cannot express, Odoo Online is ruled out. Do not let a salesperson promise that “we’ll look at it later”: the blocker is both contractual and technical.
Conversely, if your scope is standard (sales, purchasing, inventory, accounting, CRM), Odoo Online spares you an entire infrastructure project. Our guide on customizing Odoo, SAP and Dynamics without developers shows how far configuration can go before you need code.
Database access and troubleshooting
On Odoo Online you cannot run a SQL query to understand a slowdown or fix a batch of data. You go through the vendor’s support. For an SME with no technical team, that is acceptable. For a mid-sized company feeding a data warehouse or a BI tool directly from the database, it is a serious constraint (the external API remains the integration route).
Test environments
On Odoo Online, the documentation states that duplicates expire after 15 days, with a maximum of five per database. That is enough for a one-off acceptance test, not for a continuous development pipeline. Odoo.sh was designed around development, staging and production branches. With a partner host or self-hosting, these environments exist only if someone builds and maintains them.
Comparison: control, responsibilities, cost
| Criterion | Odoo Online | Odoo.sh | Partner host | On-premise / private cloud |
|---|---|---|---|---|
| Control | Low | Medium to high | Medium to high | Maximum |
| Customization | Configuration and Studio | Code and third-party modules | Code and third-party modules | Code and third-party modules |
| Updates | Driven via the vendor interface | Planned by you | Planned with the provider | Entirely your responsibility |
| Backups | Daily (Odoo SLA) | Automated | Per contract, to be tested | To be designed and tested |
| Data location | To be checked with Odoo | To be checked with Odoo | Chosen in the contract | Chosen by you |
| In-house skills | Very low | Odoo developers | Contract management | Sysadmin and security |
| Cost structure | Per-user subscription | Subscription plus development | Subscription plus managed service | Infrastructure plus team |
On licensing: according to Odoo’s pricing page (consulted on 20 November 2026), the Standard plan is hosted on Odoo Online, while the Custom plan lets you choose between Odoo Online, Odoo.sh or On-Premise. In other words, leaving Odoo Online for a hosting model with custom code also means changing plan. Check the amounts in force when you request your quote: they change and differ between annual and monthly commitments.
Three-year TCO: the cost items to quantify
Comparing a subscription with a server is the classic trap. The subscription looks expensive, the server looks free, and everyone forgets that the server needs someone to look after it. Here are the items to include in each scenario.
- Licences: per-user subscription (Online, Odoo.sh, On-Premise Enterprise) or no licence with Community, at the functional cost of missing the Enterprise modules.
- Hosting: included in the subscription on Online, billed on top on Odoo.sh depending on resources, billed by the provider or by your IaaS vendor elsewhere. Use the public price lists and request a quote for your data volume.
- Operations: system patches, security updates, certificate management, on-call duty. None on Online, partial on Odoo.sh, outsourced with a partner, entirely in-house on-premise.
- Backup and restore: storage space, off-site copy, and above all staff time for regular restore tests.
- Monitoring: metrics, alerts, logging.
- Security: firewall, hardening, vulnerability scanning, privileged access management.
- Development and maintenance of custom code: to be counted in every scenario except Odoo Online, and weighed against the cost of an upgrade at each cycle.
- Version upgrades: a recurring workstream, more expensive when the volume of custom code is high.
A tip on method: model three scenarios (optimistic, central, major incident) rather than just one. The cost of a day of production downtime or a failed restore often outweighs the subscription gap. For the full structure of such a calculation, see our 5-year ERP TCO method and the breakdown of real Odoo project costs.
Compliance and sovereignty
GDPR and data location
The GDPR does not require hosting in any particular country, but it does require you to know where your data is, who accesses it, and on what legal basis it may be transferred outside the Union. With Odoo Online, the documentation we consulted does not detail the geographic location of the data centres: ask Odoo for written confirmation or for the contractual terms. With a partner host or self-hosting, you choose the region, which simplifies your record of processing activities and customer audits.
NIS2 for the companies concerned
The NIS2 Directive (EU) 2022/2555 requires cybersecurity risk-management measures from the entities it covers, including supply chain security and incident handling. If your company is in scope, the ERP and its host become part of your risk analysis. In practice: ask for the host’s certifications, incident notification deadlines, and how responsibility is shared in the event of a breach. Our article on Odoo’s ISO 27001 certification (in French) gives a starting point for the vendor side.
Reversibility and exit plan
Whatever the model, write the exit before you sign:
- a full export of the database and attachments in an open format, within a defined time frame;
- return of the custom code and documentation (clear intellectual property);
- a transition period during which the old environment remains accessible read-only;
- no hidden fees for retrieving your data.
One structural fact works in Odoo’s favour: its core is open, so the database and the Community modules remain usable elsewhere. For a comparison with other open-source ERPs, see our Dolibarr, ERPNext, Axelor and Odoo comparison.
Shared responsibilities
| Responsibility | Odoo Online | Odoo.sh | Partner | On-premise |
|---|---|---|---|---|
| Infrastructure | Odoo | Odoo | Provider | You |
| System security | Odoo | Shared | Provider | You |
| Quality of custom code | Not applicable | You or your integrator | You or the provider | You |
| Restore test | To be requested | To be organised | Contractual | You |
| GDPR compliance (data controller) | You | You | You | You |
The last row never changes: you remain the data controller, whoever hosts the system.
Version upgrades and environments
The version upgrade is the moment when your hosting choice either pays off or costs you. On Odoo Online, the upgrade is launched from database management, which works as long as you have no custom code to adapt. On Odoo.sh, you test the migration on a branch, with your modules, before switching production. With a partner, the schedule is negotiated. On-premise, you build the procedure: copy production, migrate the copy, acceptance testing, cutover, documented rollback.
The useful rule: an upgrade must never be tested for the first time in production. Plan for at least one staging environment fed by a recent copy of production, and build it into the annual budget. To gauge the effort of a version change, see our Odoo 18 vs 17 and migration guide.
Backups: a backup that has never been restored is a hypothesis, not a guarantee. Schedule one restore test per quarter, measure the actual duration, and compare it with the recovery time your management considers acceptable.
Recommendation by profile
SME with no IT department, standard processes. Odoo Online. You are buying operational peace of mind, and you accept staying within the standard scope and Studio. The warning sign: the first request for a third-party module or custom code.
SME or mid-sized company with moderate customization and a development team (in-house or at the integrator). Odoo.sh. You get branches, staging and versioned code without running servers. Check the platform’s location and contractual terms against your customers’ requirements.
Mid-sized company with heavy customization, location requirements, or operations already handled by a provider. Partner host. You buy a service with a single contact and negotiated commitments. It is the best option when EU location and a reversibility clause are non-negotiable and you do not want to hire system administrators.
Regulated sector, strict security policy, deep integration with the internal IT landscape. Private cloud or on-premise, with a team able to take on security, monitoring and on-call duty. If that team does not exist, total control turns into risk.
When to move from one model to another
Four signals justify a change:
- From Online to Odoo.sh: a recurring need for code or third-party modules, or the need for lasting staging environments.
- From Odoo.sh to a partner or private cloud: a location, certification or contract requirement that the platform does not cover.
- From self-hosting to a partner: the departure of the person who holds the infrastructure knowledge, or an incident that revealed the absence of restore testing.
- From a partner to something else: a repeatedly missed SLA, or excessive dependence on a single provider.
In every case, prepare the migration as a mini-project: inventory of custom code, import test on a copy, cutover and rollback plan.
Going further
A hosting choice should be judged on multi-year TCO, not on the price of the first month. For a broader framing of the debate, read our guide to cloud-native, on-premise and hybrid ERP for mid-sized companies and our article on multi-tenant, single-tenant and private cloud hosting. To compare several scenarios side by side, download our ERP evaluation grid: 30 criteria to benchmark three solutions and three hosting modes on the same scale.