← All articles

Blog

Odoo.sh vs On-Premise vs Odoo Online: Hosting Trade-Offs

Odoo Online, Odoo.sh or on-premise? A practical comparison of custom code, control, backups, upgrades and cost to help you choose the right hosting model.

6 min read
  • mid
  • odoo

If you only want the short answer: choose Odoo Online if you can live with standard apps and Studio, Odoo.sh if you need custom modules but not a sysadmin, and on-premise if you need full control over infrastructure and have people who can run it. Most small and mid-sized businesses that need real customization end up on Odoo.sh. Most that do not need it should stay on Odoo Online.

Hosting is one of the first decisions in an Odoo project, and one of the hardest to reverse cheaply. Here is what actually differs.

The three options in one table

Odoo OnlineOdoo.shOn-premise
Who runs the serversOdooOdoo (platform), you (code)You or your hosting partner
Custom modulesNot supportedSupported via GitFully supported
Studio customizationYes (Custom plan)Yes (Custom plan)Yes (Enterprise, Custom plan)
Third-party appsStandard apps onlyYesYes
Server and shell accessNoWeb shell, SSHFull
Staging and test environmentsTest on a database duplicateBuilt inYou build them
UpgradesHandled by OdooTooling provided, you validateYou plan and run them
Community EditionNoNoYes

The key dividing line is custom code. Odoo’s own hosting documentation states that Odoo Online is not compatible with non-standard apps. If your requirements include a custom Python module or a community add-on, Online is off the table.

Odoo Online: the lowest-effort path

Odoo Online is the SaaS option. Odoo hosts, patches and upgrades your database. You configure the standard apps and extend them with Studio, the no-code customization tool.

Good fit when:

  • Your processes map reasonably well to standard Odoo.
  • You want predictable operations with no infrastructure work.
  • Your team is small and nobody wants to own a deployment pipeline.

Watch out for:

  • No custom Python code. If a requirement truly needs it, you will hit a wall mid-project.
  • Studio customizations are convenient, but they still need to be re-checked when Odoo upgrades the underlying version. Heavy Studio use is a form of technical debt too.
  • Plan choice matters too. According to Odoo’s pricing page, Studio is part of the Custom plan, while Standard is hosted on Odoo Online without custom modules.

Odoo.sh: the middle path

Odoo describes Odoo.sh as the official cloud platform for hosting and managing Odoo applications. In practice it is a platform-as-a-service built around Git. You push code to a GitHub repository, and Odoo.sh builds and deploys it into production, staging or development branches.

What you get:

  • Custom modules and third-party apps, with your code in version control.
  • Separate production, staging and development stages, so changes can be tested against a copy of real data before they reach users. See the branches documentation.
  • Web shell and SSH access for debugging.
  • Managed backups. According to Odoo’s branch documentation, production keeps seven daily, four weekly and three monthly backups. Staging databases are not backed up automatically.

Trade-offs:

  • You do not get unrestricted server-level control. If you need custom system packages, unusual network setups or a particular database topology, this may not be enough.
  • You need a developer or partner who is comfortable with Git workflows. The platform does not remove the need for engineering discipline.
  • Cost is layered. Per Odoo’s pricing configurator, hosting is billed on top of the Custom plan, with line items for workers, staging environments and optional dedicated servers. Figures change, so price your own configuration rather than relying on a blog post.
  • You must be on the Custom plan, which is priced higher per user than Standard.

On-premise: maximum control, maximum responsibility

On-premise means you install and run Odoo yourself, on your own hardware or on a cloud provider such as AWS, Azure or a European host. It is the only option that supports Community Edition, and it gives you full control of the stack. Odoo’s on-premise documentation covers installation, bugfix updates, system configuration and more.

Good fit when:

  • You have data residency, sovereignty or air-gap requirements that rule out a shared platform. This is common in regulated EU sectors and in some public-sector and defense-adjacent work.
  • You must integrate tightly with internal systems that cannot be reached from the cloud.
  • You want to run Community Edition or a heavily modified fork.
  • You already have infrastructure staff.

What you take on:

  • Security patching of the OS, database and Odoo itself.
  • Backups, restore testing and disaster recovery. Nobody else tests your restores.
  • Monitoring, performance tuning and capacity planning.
  • Building your own staging environment and deployment pipeline.
  • Version upgrades. Odoo’s upgrade service and tooling help, but the planning and testing are yours.
  • Support boundaries. Odoo SA does not provide guarantees on the robustness, performance or scalability of infrastructure you run yourself.

A self-hosted setup is cheaper only if you count the licence line and ignore staff time. Once you include the hours spent on patching, monitoring and incident response, the gap to Odoo.sh is often smaller than expected.

Questions that decide it

Work through these in order:

  1. Do you need custom code or non-standard apps? If no, Odoo Online is the default. If yes, it is Odoo.sh or on-premise.
  2. Do you need Community Edition? Then on-premise.
  3. Are there hard compliance or data location constraints? If a shared platform is not acceptable, on-premise (or a managed private deployment by a partner).
  4. Do you have people to run infrastructure? If not, avoid on-premise unless a partner will operate it for you under a written SLA.
  5. How often will you change the system? Frequent releases favor Odoo.sh’s staging workflow. Rarely-changed, stable systems tolerate other models better.

Common mistakes

Starting on Online and customizing past its limits. Teams sometimes begin on Online, then discover a requirement that needs code. Moving to Odoo.sh or on-premise later is possible, but it is a migration project, not a toggle.

Choosing on-premise to save money. Without an owner for patching and backups, the cheap option becomes the risky one.

Treating Odoo.sh as no-ops. It reduces infrastructure work. It does not review your code, manage your Git branches or validate an upgrade for you.

Ignoring upgrades. Whatever you pick, plan for version upgrades. Custom modules and Studio changes must be tested against each new version. The more you customize, the more this costs.

A reasonable default

For a typical SMB with standard processes, start on Odoo Online. For a business with integrations, custom workflows or third-party apps, Odoo.sh is usually the best balance. For regulated, high-control or Community Edition scenarios, plan on-premise with named owners for operations.

If you are unsure which category you fall into, list your must-have requirements first and mark which ones need code. That list usually makes the decision for you.

Talk it through with us

If you are weighing these options and want a second opinion, Teknologia Solutions is happy to review your requirements and walk through the trade-offs in a no-charge conversation. No pitch, no obligation.


Sources: Odoo documentation, Hosting; Odoo.sh documentation; Odoo.sh branches and backups; Odoo on-premise documentation; Odoo pricing; Odoo pricing configurator; Odoo forum, which hosting type is right. Features, plans and prices change between Odoo versions. Verify against Odoo’s primary documentation and your own quote before deciding.