What does Odoo.sh actually cost on top of the license?

Odoo.sh hosting is sized by 'workers' (concurrent request processors) and storage. A small project (1 worker, 20 GB) is around USD 60/month; mid-market (4 workers, 100 GB) is around USD 240/month; larger (8+ workers, 500 GB) ranges from USD 500/month upward. For a 50-user manufacturer, expect to be in the USD 200–400/month range for .sh hosting on top of license fees. Odoo S.A. publishes a calculator on their website; .sh pricing has been stable for several years.

Can I move from Odoo Online to Odoo.sh later if I outgrow Online?

Yes — and it's a common path. The migration is straightforward: Odoo S.A. handles the database transfer; your partner sets up the .sh project, deploys any custom modules you've decided to add, and tests. Allow 1–2 weeks for the switch. The opposite direction (.sh → Online) is harder because Online won't run your custom modules — you'd have to audit and remove them first.

Why does Odoo Online not allow custom modules?

Two reasons. (1) Odoo S.A. runs Odoo Online as a multi-tenant SaaS where uniformity is what makes it cheap and reliable — admitting custom code per customer breaks the operational model. (2) Studio (the no-code customization editor) was designed specifically to cover the customization needs that Online cannot accept as code. For a meaningful slice of small-business use cases, Studio is enough. For everyone else, Odoo.sh is the answer.

What about self-hosted? When does that make sense?

Three real cases: (1) you're on Odoo Community (Odoo.sh and Online both require Enterprise); (2) you have strict data residency requirements that Odoo's regional hosting doesn't satisfy (e.g. a specific country's data sovereignty law, on-premises sensitive data); (3) you have a strong in-house DevOps team and want full control over infrastructure decisions, cost, and tuning. Outside these cases, self-hosting Enterprise is usually a worse trade — you take on operational burden for marginal savings.

Does Odoo.sh handle automatic upgrades?

Partially. Odoo S.A. publishes the upgrade scripts and runs them against a staging copy of your database when a new Odoo version is released. Your team (or partner) then merges any code changes needed for your custom modules to work on the new version, tests on staging, and deploys to production when ready. So .sh removes the infrastructure work of an upgrade but not the code work. Odoo Online upgrades require no code work because there is no custom code.

Odoo S.A. publishes uptime statistics for both Odoo.sh and Odoo Online — typically 99.9%+ across both. Real-world incident history is comparable. Self-hosted uptime is what your team makes it; many self-hosted deployments underperform managed options because hosting isn't the team's core competence.

Can I run Odoo.sh + Odoo Online together?

Yes — they're separate subscriptions and can coexist. We've seen a few legitimate patterns: production on .sh and a sandbox / training environment on Online; multi-entity groups with one large entity on .sh and small subsidiaries on Online. Most businesses don't need both; pick one based on the primary production workload.

What about deploying via CI/CD?

Odoo.sh has native CI/CD — pushing to a Git branch triggers a build, runs tests if you have them, and deploys to the matching environment. It's the only Odoo hosting option with this workflow. Odoo Online has no equivalent. Self-hosted CI/CD is whatever your team builds.

Is data on Odoo Online and Odoo.sh encrypted?

Yes — both. Encrypted at rest (database, file storage) and in transit (HTTPS). Odoo S.A. publishes the details in their security documentation. SOC 2 Type II compliance is in place for the Odoo cloud infrastructure. Self-hosted encryption is up to you.

How do partners typically deploy on Odoo.sh?

Most partner-led .sh deployments follow the same pattern: a GitHub or GitLab repo with the project's custom modules, branches for production / staging / development, pull requests for new work, deployment by merging to production. The .sh project provisions environments matching each major branch. This is significantly more controlled than self-hosting and significantly more flexible than Odoo Online.

Final recommendation in one line?

Mid-market with any real customization: Odoo.sh. Small business with no customization beyond Studio: Odoo Online. Community edition, strict data residency, or strong DevOps team with reason to self-host: self-hosted. Most businesses end up on .sh; many start on Online and migrate later.

Comparison

Odoo.sh vs Odoo Online

Last reviewed: May 12, 2026

Three real options, three different buyers. Odoo Online is the simplest and cheapest, but it's a walled garden — you cannot install custom modules, you cannot deploy via Git, you cannot access the server. Odoo.sh is the managed-but-flexible middle ground: full Git-based development, custom modules supported, multiple environments per project, but Odoo S.A. handles infrastructure, backups, and the upgrade machinery. Self-hosted is full control: you pick the cloud, the database tuning, the backup strategy, the upgrade cadence — but you also own the operational burden. The honest hierarchy for partner-led mid-market deployments is Odoo.sh first, Odoo Online for genuinely no-customization cases, self-hosted only when there's a specific reason (Community edition, regulatory data residency, deep DevOps capacity).

Product A

Odoo.sh

Odoo S.A.'s managed PaaS platform. Git-based deployments, per-branch staging environments, scheduled backups, full server access, and the ability to install custom modules and third-party apps. Built for businesses that want managed infrastructure without the customization restrictions of Odoo Online.

Visit site

Product B

Odoo Online

Odoo S.A.'s fully managed SaaS. Zero infrastructure decisions, no Git, no custom modules, no third-party apps. Just standard Odoo Enterprise modules with Studio for no-code customization. The simplest, cheapest managed option — but with the strictest customization limits.

Visit site

Scorecard

Category	Odoo.sh	Odoo Online	Notes
Cost (license + hosting, 50 users)	8/10	10/10	Odoo Online: license only (~USD 15,000–24,000/year). Odoo.sh: license + hosting (~USD 3,000–8,000/year on top, sized by project size). Self-hosted Enterprise: license + your own infrastructure cost (typically USD 6,000–18,000/year for comparable performance).
Customization freedom	10/10	5/10	Odoo.sh: any custom module, any third-party app, full Python/JS modifications, Git-based deployment. Odoo Online: standard modules + Studio only; no custom modules, no third-party apps. Self-hosted: same as Odoo.sh (anything goes).
Server access	9/10	3/10	Odoo.sh: SSH access, shell access, log streaming, database access. Odoo Online: no server access at all. Self-hosted: complete root access.
Backup + disaster recovery	9/10	9/10	Odoo.sh: automated daily backups, multiple retention periods, one-click restore. Odoo Online: same. Self-hosted: depends on your DevOps maturity (often where self-hosted deployments fail).
Upgrade smoothness	9/10	10/10	Odoo Online: upgrades managed entirely by Odoo S.A., usually a click. Odoo.sh: Odoo S.A. provides upgrade machinery, you (or your partner) merge it into your Git branch and test. Self-hosted: full responsibility on you and your partner.
Staging / dev environments	10/10	4/10	Odoo.sh: per-Git-branch staging environments, click-to-create dev environments, drop them when done. Odoo Online: one production environment per database, no staging. Self-hosted: as many environments as your team builds.
Performance + scaling	9/10	8/10	Odoo.sh: dedicated containers per project, configurable sizing (worker count, memory), scales with project plan. Odoo Online: shared infrastructure tuned for standard usage, sufficient for most. Self-hosted: only as good as your DevOps.
Data residency	7/10	6/10	Odoo.sh: regional hosting (US, EU, India, etc.) selectable per project; specific country requirements may need self-hosted. Odoo Online: same regional choices. Self-hosted: choose any cloud or your own data centre — strictest data residency needs default here.
Support	9/10	9/10	Odoo S.A. directly supports both .sh and Online (Enterprise license included). Partner support handles everything custom on .sh and self-hosted. Self-hosted: same Odoo S.A. support for the core Enterprise modules, you/partner cover infra.
Time to first production go-live	9/10	10/10	Odoo Online: instant signup, days to configure. Odoo.sh: project setup is a few hours, then standard implementation cadence. Self-hosted: weeks if not already running on Odoo.
Total	89/100	74/100

Feature comparison

Feature	Odoo.sh	Odoo Online
Pricing model	License + per-project hosting fee (sized by workers and storage)	License only; hosting included
Custom Python modules	Fully supported via Git deployment	Not supported
Third-party Odoo App Store apps	Fully supported	Only Odoo S.A.-published apps; no third-party
Studio (no-code customization)	Supported	Supported
Git workflow	Native (GitHub/GitLab/Bitbucket integration)	Not available
Staging environments	Unlimited per-branch staging + dev environments	Production only
SSH / shell access	Yes	No
Direct PostgreSQL access	Yes (read-only by default, configurable)	No
Server logs	Real-time log streaming + retained history	Limited via interface; no raw access
Worker / memory configuration	Adjustable per project plan	Fixed (managed by Odoo S.A.)
Cron / scheduled jobs (custom)	Yes (deploy as part of code)	Only standard Odoo crons
Backup retention	Configurable, 7–90 days depending on plan	Configurable, similar retention
Restore a backup	One-click to any environment	Self-service via Odoo Online interface
Multiple databases per project	Yes	One database per subscription (Standard plan)
Multi-company	Fully supported	Supported on Custom plan, not Standard
Typical fit	Mid-market, partner-led, any customization	Small business, standard config, Studio-only

Who each is best for

Best for Odoo.sh

Mid-market businesses (10–500+ users) whose Odoo implementation will include any custom development or third-party apps — which is most of them. Odoo.sh is also the right call for businesses on Odoo who anticipate growing into manufacturing, e-invoicing, custom integrations, or any module that requires either custom Python or a vendor app from the Odoo App Store. If your partner is using Git for the implementation (and reputable Gold Partners do), .sh is the natural fit. The annual hosting premium over Odoo Online is small relative to the customization freedom.

Best for Odoo Online

Small businesses (under 25 users typically) running standard Odoo flows with Studio as the only customization layer. Genuinely zero-customization use cases — pure CRM + Invoicing + Inventory with the country's default localization — work beautifully on Odoo Online for years. Also a good fit for businesses that want minimum operational overhead and minimum partner dependency; if you can configure it yourself in Studio, you don't need a developer. Worth considering as a starting point even if you anticipate growing into .sh later; migration between the two is supported.

Migration considerations

Switching between hosting options is a common operation and well-supported. Odoo Online → Odoo.sh: standard migration path; Odoo S.A. handles the database move; allow 1–2 weeks for the switch + any customization work to deploy. Odoo.sh → Odoo Online: technically supported but means giving up custom modules and third-party apps — only do this if you've audited the codebase and confirmed nothing on production depends on custom code. Self-hosted ↔ Odoo.sh: also well-trodden, especially Odoo.sh-bound moves; we've migrated 20+ self-hosted instances to .sh to eliminate DevOps burden. Self-hosted Community → Odoo.sh requires switching to Enterprise as well (Odoo.sh doesn't host Community). The data migration itself is rarely the hard part; deciding the right destination is the hard part — start there before you move.

Frequently asked questions

What does Odoo.sh actually cost on top of the license?

Odoo.sh hosting is sized by 'workers' (concurrent request processors) and storage. A small project (1 worker, 20 GB) is around USD 60/month; mid-market (4 workers, 100 GB) is around USD 240/month; larger (8+ workers, 500 GB) ranges from USD 500/month upward. For a 50-user manufacturer, expect to be in the USD 200–400/month range for .sh hosting on top of license fees. Odoo S.A. publishes a calculator on their website; .sh pricing has been stable for several years.
Can I move from Odoo Online to Odoo.sh later if I outgrow Online?

Yes — and it's a common path. The migration is straightforward: Odoo S.A. handles the database transfer; your partner sets up the .sh project, deploys any custom modules you've decided to add, and tests. Allow 1–2 weeks for the switch. The opposite direction (.sh → Online) is harder because Online won't run your custom modules — you'd have to audit and remove them first.
Why does Odoo Online not allow custom modules?

Two reasons. (1) Odoo S.A. runs Odoo Online as a multi-tenant SaaS where uniformity is what makes it cheap and reliable — admitting custom code per customer breaks the operational model. (2) Studio (the no-code customization editor) was designed specifically to cover the customization needs that Online cannot accept as code. For a meaningful slice of small-business use cases, Studio is enough. For everyone else, Odoo.sh is the answer.
What about self-hosted? When does that make sense?

Three real cases: (1) you're on Odoo Community (Odoo.sh and Online both require Enterprise); (2) you have strict data residency requirements that Odoo's regional hosting doesn't satisfy (e.g. a specific country's data sovereignty law, on-premises sensitive data); (3) you have a strong in-house DevOps team and want full control over infrastructure decisions, cost, and tuning. Outside these cases, self-hosting Enterprise is usually a worse trade — you take on operational burden for marginal savings.
Does Odoo.sh handle automatic upgrades?

Partially. Odoo S.A. publishes the upgrade scripts and runs them against a staging copy of your database when a new Odoo version is released. Your team (or partner) then merges any code changes needed for your custom modules to work on the new version, tests on staging, and deploys to production when ready. So .sh removes the infrastructure work of an upgrade but not the code work. Odoo Online upgrades require no code work because there is no custom code.
What about uptime?

Odoo S.A. publishes uptime statistics for both Odoo.sh and Odoo Online — typically 99.9%+ across both. Real-world incident history is comparable. Self-hosted uptime is what your team makes it; many self-hosted deployments underperform managed options because hosting isn't the team's core competence.
Can I run Odoo.sh + Odoo Online together?

Yes — they're separate subscriptions and can coexist. We've seen a few legitimate patterns: production on .sh and a sandbox / training environment on Online; multi-entity groups with one large entity on .sh and small subsidiaries on Online. Most businesses don't need both; pick one based on the primary production workload.
What about deploying via CI/CD?

Odoo.sh has native CI/CD — pushing to a Git branch triggers a build, runs tests if you have them, and deploys to the matching environment. It's the only Odoo hosting option with this workflow. Odoo Online has no equivalent. Self-hosted CI/CD is whatever your team builds.
Is data on Odoo Online and Odoo.sh encrypted?

Yes — both. Encrypted at rest (database, file storage) and in transit (HTTPS). Odoo S.A. publishes the details in their security documentation. SOC 2 Type II compliance is in place for the Odoo cloud infrastructure. Self-hosted encryption is up to you.
How do partners typically deploy on Odoo.sh?

Most partner-led .sh deployments follow the same pattern: a GitHub or GitLab repo with the project's custom modules, branches for production / staging / development, pull requests for new work, deployment by merging to production. The .sh project provisions environments matching each major branch. This is significantly more controlled than self-hosting and significantly more flexible than Odoo Online.
Final recommendation in one line?

Mid-market with any real customization: Odoo.sh. Small business with no customization beyond Studio: Odoo Online. Community edition, strict data residency, or strong DevOps team with reason to self-host: self-hosted. Most businesses end up on .sh; many start on Online and migrate later.