Odoo Online vs Odoo.sh: which hosting fits your company

Odoo gives you two cloud options: Odoo Online and Odoo.sh. They run the same Odoo apps. The difference is who controls the code and the environment around your database. This guide states what Odoo says about each, as read on odoo.com/pricing and odoo.sh in October 2026, and says which setup fits which company.

Check the numbers and plan names on those pages before you buy. Odoo changes them.

The short answer

• Choose Odoo Online if the standard Odoo apps cover how your team works. Odoo hosts and maintains it, and you do not run any code.
• Choose Odoo.sh if you need custom modules, third-party apps or a place to test changes with your own data before they go live.

For a 10 to 100 person company moving off a CRM and spreadsheets, Odoo Online is the default to test first. Odoo.sh becomes necessary when a process cannot be set up with the standard apps and an Odoo developer writes code for it.

What Odoo Online is

Odoo Online is the cloud version where Odoo runs everything. According to the pricing page:

• It is available on all paid plans and on the One App Free plan.
• Hosting on it is free, with unmetered storage up to 100 GB, per Odoo's pricing FAQ.
• Plans include unlimited support, hosting and maintenance, with no feature or data limits.
• You pay per user per month for a licence. The Standard plan includes all apps. The Custom plan adds Odoo Studio, Agentic AI, Multi-Company and an External API.

On Odoo Online you work with the standard apps. You can adjust fields, views and automations through the interface, and with Studio on the Custom plan you can add fields and screens without code. You do not install custom code.

What Odoo.sh is

Odoo.sh is a hosting platform for developers. Odoo describes it as an all-in-one platform and heads its page "Developers first". From the Odoo.sh page:

• Git integration. It is tightly integrated with GitHub. Pushing a branch creates a development server. Pushing to staging or production updates those servers.
• Staging. You launch a staging server to test new features with your own data, through live database replication.
• Backups. Daily incremental backups on 3 different servers.
• Shell access. Shell access to development, staging and production containers.
• Testing and monitoring. Automated testing of every commit, 24/7 monitoring and a built-in runbot for testing feature branches.
• Community modules. You add them as git submodules.

On the Odoo.sh pricing page, you size the hosting yourself: 1 to 16 workers, 1 to 512 GB of storage and 0 to 20 staging environments. Beyond 16 workers or 512 GB you need dedicated hosting. Odoo shows these as per-month rates per worker, per GB and per environment. We do not quote the rates here because the page did not display amounts when we read it.

Odoo.sh is available on the Custom plan. The pricing page says the Odoo.sh hosting price does not include the Enterprise licence, so you pay for both.

Side by side

	Odoo Online	Odoo.sh
Who hosts it	Odoo	Odoo, on a platform you configure
Plans	One App Free, Standard, Custom	Custom
Custom code	Not installed	Yes, through git
Third-party and community modules	No	Yes
Staging copy with your data	Not listed on the pricing page	Yes, with live database replication
Shell access	Not listed	Yes, to development, staging and production containers
Hosting price	Free, with unmetered storage up to 100 GB	Charged by workers, storage and staging environments, on top of the licence
Who maintains custom code	Not applicable	You or your developer; Odoo's pricing page lists custom code maintenance as not included

Who each fits

Odoo Online fits when:

• Your process fits standard CRM, Sales, Accounting, Purchase, Inventory, Manufacturing, Project or Recruiting.
• Nobody on your team writes code, and you do not plan to hire a developer.
• You want one monthly line per user and no hosting to size.

Odoo.sh fits when:

• You need a custom module because a process cannot be set up in the standard apps.
• You want a third-party app from the Odoo Apps store.
• You have a developer, in-house or external, who works in git.
• Several people change the system, and you need to test changes on a copy before production.

A warning for the finance lead: custom code is a running cost, not a one-off. Someone must keep it working when Odoo upgrades. Odoo's pricing page lists maintenance of custom code as not included. If you cannot name the person who will own it, start on Odoo Online and see how far the standard apps take you.

Questions to answer before you choose

Put these to the people who will own the system. Two or more "yes" answers point to Odoo.sh.

1. Is there a process in your company that no standard Odoo app can run, even after configuration?
2. Does a vendor you depend on offer its Odoo connector only as an add-on module?
3. Do you have a developer who will own custom code for the next two years, including Odoo upgrades?
4. Will more than one person change the system, so that a test copy before each release pays for itself?

If you answer "no" to all four, you gain nothing from Odoo.sh, and you pay for hosting that Odoo Online includes in the licence.

How Ferrify handles the choice

Ferrify works on both. Our eight modules are standard Odoo apps, and a Ferrify project includes no custom code. So the standard answer for a Ferrify project is Odoo Online. We recommend Odoo.sh only when you already know you need code or third-party apps, and then we set up the standard modules and your developer writes the rest.

If you have not decided, say so on the call. We ask three questions: which processes do not fit the standard apps, who would maintain code, and how often you expect to change the system.

The licence is a separate decision from the project price. The cost guide shows the licence prices and what moves the project price. If you are moving data from a CRM, the HubSpot migration guide walks through it, and the migration page lists the other sources. If you are already on Odoo and your team avoids it, the tune-up works on either hosting. See also implementation.