Your company needs an Odoo extension. Can settings handle it, or does it require a code module your current hosting cannot run? Answering that early gives you a clearer project budget and development path. Compare Online, Odoo.sh and self-hosting to understand what you can change, who operates it and where your team can test before going live.
What is the difference between Online, Odoo.sh, and a private server?
The short rule: more control means more responsibility.
Odoo Online: hosted and managed
According to the 19.0 documentation (Online reference), there is no local installation, and neither custom modules nor the Apps Store are supported. No-code customization is possible and depends on your plan. The documentation describes test copies of 15 days, up to 5 copies. Online suits a company that runs standard apps and does not want to manage a server.
Odoo.sh: development, staging, production
The 19.0 documentation (Hosting reference) splits Odoo.sh builds into development, staging, and production, and staging copies production when a new build is made. You try a change on a copy before it touches live operations. Responsibility for custom-code maintenance and business-process testing still needs to be assigned to your implementation team. It suits a company that needs custom code and disciplined testing without running the server itself.
Private server (self-hosting)
The server may be on your premises or with a cloud provider you contract with. Your company, or its appointed operator, owns security, updates, backups and testing under the contract. This suits specific control requirements when a responsible team is clearly appointed.
The cloud is familiar in the Saudi market: GASTAT’s 2025 bulletin shows that 51.3% of establishments use cloud services (total, Table 25). What matters is who carries responsibility in your environment. At ToDoOps we review business and customization needs alongside the environment that will run them. You can read about our approach on the homepage.
What happens when you need a custom module after starting on Online?
A hypothetical example: the manager of a packaging plant with no technical team chose Online because the apps were standard and he did not want to own a server. He wrote one line in the decision memo: “If we need a custom code module, the environment itself will change.” Later the sales manager asked for a report the settings could not deliver. The plant manager was not surprised, because he had already framed the question: does a no-code solution within our plan suffice, or is it worth moving? What changed the situation was not the first choice but writing its condition down early.
Can you move from Online to Odoo.sh or a server later?
Yes, but the Hosting 19.0 documentation treats two cases differently:
- Intermediate Online versions (such as 19.1): you must wait for, or upgrade to, the compatible major version before moving to Odoo.sh or a server.
- Everything else: not every move requires the next major version, but moving is not a link swap. Test before you transfer.
So ask early which version you will run on and what customization you expect over the next few years. For modules you may need, see Odoo apps, and for a view by business type see industries.
Where are backups kept, and how many?
Odoo’s published cloud hosting policy, reviewed on 28 October 2026, describes retention of 14 full backups: 7 daily, 4 weekly, and 3 monthly (Cloud SLA reference). Backups are kept in Europe and Canada, and their locations cannot be restricted.
In practice:
- Identify the primary database location and backup locations separately. A hosting-region name alone does not establish that all data and copies remain in Saudi Arabia.
- Ask the vendor to state in writing where backups are kept, how many, and for how long.
- If your company has regulatory requirements, take them to your compliance officer before signing, not after.
What are you paying for: licence, hosting, or operations?
Four items are often blended into one budget line. Price each separately:
| Item | The question it separates |
|---|---|
| Licence | Which apps and how many users are covered? |
| Hosting | Who runs the environment and keeps the backups? |
| Operations | Who handles updates, incidents, and permissions? |
| Testing | Where are changes tried before production? |
Ask for offers that separate these items. Use our Odoo pricing guide for licences and the ToDoOps calculators for an initial implementation budget and potential time savings. Add the actual hosting and operations proposal when comparing the total.
Which environment fits my company?
| Company situation | Closest fit |
|---|---|
| Standard apps, no technical team | Online |
| Custom code plus a need for structured testing | Odoo.sh |
| Technical team and strict control policies | Private server |
Use it as a starting point for internal discussion, then test the answers against your actual needs.
Common questions before choosing
Is no-code customization enough on Online?
It may be, and what it allows depends on your plan. List the changes you need. If any of them requires a code module, Online does not support it.
How do I test a change before production?
On Odoo.sh, through a staging build copied from production. On Online, through test copies, which the documentation describes as 15 days, up to 5 copies.
Does every move from Online require the next major version?
No. That applies to intermediate Online versions such as 19.1. Other moves do not require it, but they need testing before transfer.
Can I choose where backups are kept?
Per the Cloud SLA, their locations cannot be restricted, and they are in Europe and Canada. If that conflicts with your requirements, it should steer your choice of environment.
Who is responsible on a private server if an update fails?
Your team, per the contract. Decide before you start who owns updates and who restores a backup.
Prepare three answers before you meet the vendor
- Will we need a custom module in the coming years?
- Who owns updates and restoration in our company?
- Is the backup location acceptable for our company?
With these answers, the environment becomes a deliberate decision. See how ToDoOps approaches Odoo implementation and use the calculators for an initial implementation estimate. Then discuss your hosting needs with us so we can identify what needs configuration or development and what the operating proposal should include.
References
- Odoo 19.0 documentation, Odoo Online page: managed hosting, no support for custom modules or the Apps Store, test copies. Reviewed: 28 October 2026.
- Odoo 19.0 documentation, Hosting and Odoo.sh Builds pages: version compatibility when moving, plus development, staging and production. Reviewed: 28 October 2026.
- Odoo — Cloud Hosting Service Level Agreement: the currently published backup policy. Reviewed: 28 October 2026.
- General Authority for Statistics, Establishments ICT Access and Usage Statistics 2025: bulletin tables (Table 25) and the Arabic bulletin.