Odoo.sh is Odoo’s official cloud hosting platform – a Platform-as-a-Service, built and run by Odoo on Google Cloud, designed for teams that run custom Odoo modules. Its defining feature is Git-based deployment: push code to a branch and Odoo.sh builds a staging environment automatically; merge to production and it deploys. It’s priced by infrastructure (workers, storage and staging branches) on top of an Odoo Enterprise subscription.
If you’re choosing how to host Odoo, Odoo.sh sits between the fully managed simplicity of Odoo Online and the full control of self-hosting. This article explains what it is, how the Git workflow works, what it costs in 2026, and honestly, who it fits and who is better served elsewhere.
We deploy and manage client Odoo projects on Odoo.sh, so the workflow and the fit notes below come from running real deployments on it, not from the marketing page.
What is Odoo.sh?
Odoo.sh is a managed development-and-hosting platform for Odoo, operated by Odoo S.A. itself and running on Google Cloud infrastructure. It’s aimed squarely at deployments that involve custom code – bespoke modules, third-party apps from the Odoo App Store, or tailored workflows which the fully managed Odoo Online can’t host.
The trade it makes is deliberate: you get a proper development pipeline and Odoo handles the servers, updates and backups, but you don’t get root access to the underlying machine and the infrastructure lives in Odoo’s Google Cloud account rather than yours. For most teams building on Odoo, that’s a good trade, the platform removes the infrastructure work without removing the ability to run custom code.
How does Odoo.sh work?
The heart of Odoo.sh is a Git-based workflow that mirrors how modern software teams already work. It’s the reason developers like it.
- Connect a Git repository. Your Odoo modules live in GitHub or GitLab, connected to Odoo.sh.
- Branches become environments. Push code to a branch and Odoo.sh automatically spins up a build for it. Development and staging branches each get their own database, copied from production and sanitised, so you test against realistic data safely.
- Merge deploys to production. When a change is approved and merged to the production branch, Odoo.sh deploys it.
Around that pipeline you get the tooling a real deployment needs: a per-branch log viewer, shell (SSH) access, a database manager, performance monitoring, a built-in mail server, a CDN, and automated backups. Odoo also handles weekly code updates and runs version upgrades semi-automatically, the kind of maintenance you’d otherwise carry yourself.
For a team building custom modules, this shortens the cycle from “developer writes code” to “safely tested and live” considerably, because the staging-on-every-branch behaviour is built in rather than something you assemble.
Odoo.sh vs Odoo Online vs on-premise
This is the comparison most people arrive needing, because Odoo has three hosting paths and they suit different situations.
| Odoo Online | Odoo.sh | On-premise | |
|---|---|---|---|
| What it is | Fully managed SaaS | Managed PaaS for custom code | Self-hosted on your servers |
| Custom modules | No | Yes | Yes |
| Git / staging pipeline | No | Yes, built in | Build it yourself |
| Server control / root | None | Limited (shell, no root) | Full |
| Who manages infrastructure | Odoo | Odoo | You |
| Hosting cost | Included, free | Paid — workers, storage, staging | Your server + admin time |
| Best for | Standard deployments, no code | Custom development, teams | Full control, own compliance needs |
The clean way to choose: Odoo Online if you run standard Odoo with no custom modules; Odoo.sh the moment you need custom code but don’t want to manage servers; on-premise if you need full control of the infrastructure, your own cloud region, or specific data-residency and compliance arrangements. Odoo.sh is the middle path, and for most businesses running custom development it’s the pragmatic one.
What does Odoo.sh cost in 2026?
Odoo.sh pricing has two layers, and understanding both prevents budget surprises.
Layer one – the Enterprise subscription. Odoo.sh runs on Odoo Enterprise, so you pay the per-user Enterprise licence as well as the platform. This is the layer people forget when they see the hosting price alone.
Layer two – platform resources, metered:
- Workers – the compute units that process requests. Roughly $48–72 per worker per month, and one worker handles about 25 users or 5,000 daily website visitors as a rule of thumb.
- Storage – around $0.16 per GB per month.
- Staging branches – roughly $12–30 each per month, optional but strongly recommended for real development.
- Dedicated server – an optional premium (several hundred dollars a month) if you don’t want the shared environment.
In practice: a single-worker production instance starts around $60 a month and handles a small team, while a real 30-user deployment with a staging branch and a second worker lands closer to $150–200 a month in platform cost plus the Enterprise licences on top. As a worked example, a 25-user setup can run roughly $200 a month in hosting and around $1,400+ a month all-in once Enterprise licences are counted. Confirm current rates on <a href=”https://www.odoo.com/pricing” rel=”noopener” target=”_blank”>Odoo’s pricing page</a>, since both layers move.
Who is Odoo.sh for?
A strong fit if you run custom Odoo modules or third-party apps and want a proper development pipeline – staging, testing, controlled deployment without building and maintaining the infrastructure yourself. It suits businesses working with a development team or partner, teams that value the Git workflow, and anyone who wants Odoo to handle updates, backups and security patching.
Look elsewhere if:
- You run standard Odoo with no custom code. Odoo Online is included free and does the job; Odoo.sh would be paying for a pipeline you won’t use.
- You need full server control, a specific cloud provider or region, or strict data-residency arrangements. On-premise or your own cloud is the answer, since Odoo.sh runs in Odoo’s Google Cloud account with no root access.
- Cost per user is already tight and growing. Odoo.sh bundles the Enterprise licence, so the bill scales with headcount as well as infrastructure worth modelling before you commit.
One thing to be clear about: Odoo.sh is not “free Community”
A common misconception worth correcting, because it changes budgets. Odoo.sh is a paid, Enterprise-tier platform it requires an active Enterprise subscription. Odoo’s free Community edition is genuinely free only when you self-host it on your own infrastructure (a VPS, your own cloud, or on-premise). You can deploy custom and community modules on Odoo.sh, but you’re doing so on the paid platform, not running Odoo for free. If a zero-licence cost is the goal, self-hosted Community is the path and it comes with the trade-off of managing everything yourself. Our comparison of Odoo Community vs Enterprise covers that decision in full.
Where a partner fits
Odoo.sh removes the server administration, but it doesn’t write your modules, design your branch strategy, or manage your deployments. That’s where a development team earns its place building the custom modules you’re hosting, setting up the Git workflow and staging discipline, and running the deploy process safely. For businesses without in-house Odoo developers, dedicated Odoo developers are what turn Odoo.sh from a platform into a working, maintained system, and ongoing support and maintenance keeps it healthy after go-live.
Odoo.sh is the environment; the implementation and development are what make it deliver.
Frequently asked questions
What is Odoo.sh? Odoo.sh is Odoo’s official Platform-as-a-Service, built and run by Odoo on Google Cloud. It hosts Odoo deployments that use custom modules, with a Git-based workflow for development, staging and production, and Odoo handling updates, backups and infrastructure.
How much does Odoo.sh cost? Odoo.sh is priced in two layers: the per-user Odoo Enterprise subscription, plus metered platform resources – workers (about $48–72 each per month), storage (around $0.16/GB/month) and staging branches (about $12–30 each). A small production instance starts near $60/month in hosting, before Enterprise licences. Confirm current rates at odoo.com.
What is the difference between Odoo.sh and Odoo Online? Odoo Online is fully managed SaaS that can’t run custom modules and is included free with a subscription. Odoo.sh is a paid platform that hosts custom code, with a Git pipeline, staging environments and shell access. Choose Odoo Online for standard deployments and Odoo.sh once you need custom development.
Can I run Odoo Community on Odoo.sh? Odoo.sh requires a paid Enterprise-tier subscription, so it isn’t a way to run Community for free. Odoo’s free Community edition is free only when self-hosted on your own infrastructure. You can, however, deploy custom and community modules on the Odoo.sh platform.
Does Odoo.sh support Git and staging environments? Yes. Git integration with GitHub or GitLab is central to Odoo.sh. Development and staging branches each get their own database copied from production and sanitised, and merging to the production branch deploys automatically.
Who should use Odoo.sh? Businesses running custom Odoo modules that want a managed development pipeline without maintaining servers themselves. It’s less suited to standard deployments with no custom code (use Odoo Online) or teams needing full server control and their own cloud region (use on-premise).
Next step
If you’re deciding how to host Odoo or already on Odoo.sh and want it set up and managed properly – the useful step is a short conversation about your modules, your team and your deployment needs.
Talk to our Odoo team → | Hire dedicated Odoo developers → | See Odoo on live data →