Odoo.sh is Odoo’s managed development and hosting platform for projects with custom code. Odoo Online suits businesses whose workflows fit the hosted applications and supported configuration tools. Self-hosted Odoo gives your team or hosting partner responsibility for the server as well as more control over it.
The right choice depends on your modules, integrations, release process and operating responsibilities. Company size alone does not decide it. This 2026 guide compares the options, explains Odoo.sh pricing and shows where an ERPixel hosting plan can fit.
If you are still deciding between Community and Enterprise, start with our Odoo edition and system selection guide. Then choose the hosting model that supports your required applications.
Hosting offer and Odoo.sh EUR inputs reviewed: November 9, 2026. Technical references use Odoo 19 documentation; check compatibility with the version and modules you actually run. Licence prices have a separate dated snapshot on the pricing page.
Odoo hosting comparison at a glance
Separate the delivery model from the commercial terms. Cloud ERP is remotely hosted; Software as a Service (SaaS) places application operation with the provider, while on-premise ERP gives the organization responsibility for its environment. The software license separately defines permitted use and distribution.
| Decision | Odoo Online | Odoo.sh | Self-hosted / on-premise |
|---|---|---|---|
| Who runs the infrastructure? | Odoo | Odoo runs the platform; your team maintains project code | Your team or a hosting provider such as ERPixel |
| Custom server modules | Not supported | Supported within the platform’s environment | Supported; you manage dependencies and compatibility |
| Development workflow | Hosted configuration tools | GitHub, builds, development and staging branches | Tools and release process arranged by your team or provider |
| Server control | No server administration | Build shell/SSH access; managed infrastructure | Control over the stack, subject to the hosting agreement |
| Cost structure | Odoo plan with Online hosting included | Odoo subscription plus separate platform hosting | Infrastructure, operations and any Enterprise licence |
| Backups and recovery | Managed by Odoo | Automatic production backups; staging/dev differ | Specify backup scope, retention and restore responsibilities |
“On-premise” does not have to mean a server in your office. The same deployment model can run on a rented cloud server or infrastructure managed by a partner. Managed hosting and self-administration are different service arrangements within that model.
Odoo.sh pricing in 2026: what to budget for
Odoo.sh hosting is charged separately from the Enterprise licence. Its official hosting calculator uses workers, storage, staging environments and shared or dedicated hosting. A worker is an application processing resource, not a named user licence.
The official Odoo.sh calculator uses monthly EUR inputs of €60 per worker, €0.20 per GB and €15 per staging environment, verified on November 9, 2026. One worker, 40 GB and one staging environment total €83/month with monthly payment, or €796.80/year (€66.40/month equivalent) with annual payment. This is a reference configuration, not a capacity recommendation. Compare your country, user tier and included services in our Odoo hosting cost comparison.
For Online, “free” refers to the One App Free offer with its included dependencies and unlimited users, not an unrestricted multi-app ERP subscription. Paid Standard and Custom subscriptions are separate choices; consult Odoo’s current plan terms.
Compare each proposal using the same scope:
- Recurring costs: licences, hosting resources, backup storage, additional environments and agreed operational support.
- Initial costs: installation, migration, domain/email setup and configuration.
- Ongoing project work: custom module maintenance, upgrades and changes to integrations.
A lower server rental price alone does not establish a lower total cost. Equally, you may not need every platform feature for your particular deployment.
Odoo Online: when standard workflows are enough
Odoo Online removes the need to operate an Odoo server. It supports configuration without custom server code, but you cannot install custom modules or modules from the Odoo Apps Store. See the Odoo Online documentation.
For paid plans, Standard provides the apps on Online; Custom adds Studio, multi-company and external API access. Selecting Custom while staying on Online does not unlock custom server modules. The official plan comparison separates these choices.
Online can work for a larger organization if its processes fit. Before rejecting it, distinguish between a connector that must be installed inside Odoo and an external service that communicates through its API. External API access is available on the Custom plan; it is not included in One App Free or Standard. See Odoo’s external API documentation.
Choose it when: supported applications and configuration cover your needs, and your team wants Odoo to handle the hosting. Reconsider it when an essential workflow needs a server-side module.
Odoo.sh: custom code with a managed platform
Odoo.sh connects project code in GitHub with builds and deployment environments. It provides a development workflow for custom modules without requiring your team to assemble the entire hosting toolchain. Build shell and SSH access help developers inspect and troubleshoot their application; they are not equivalent to owning the underlying server.
A staging branch uses a neutralized copy of production data to test changes. Odoo disables outgoing email and scheduled actions in that copy by default. Check your own connectors too: a custom integration must not send test orders or stock updates to a live external system.
Production receives automatic backups, with seven daily, four weekly and three monthly copies documented. Staging and development databases do not receive the same automatic backups. Review the branch and backup documentation when planning recovery and test environments.
Choose it when: you need custom modules and value an integrated release workflow. Your developer or implementation partner still needs to review code, test changes and maintain module compatibility. A managed platform does not remove those responsibilities.
Self-hosted Odoo: control with operational responsibility
Self-hosting lets you choose the operating environment and deployment process. It can accommodate Community or Enterprise, subject to the applicable licences. This is useful when a project needs infrastructure choices or dependencies that do not fit a managed platform.
That control needs an operating plan: who patches the system, monitors incidents, backs up the database and filestore, tests restoration, and handles releases? If a provider runs the server, agree which work belongs to hosting and which belongs to application support.
A dedicated server is not automatically faster or more secure. Performance depends on the workload, resources and application code; security depends on configuration and ongoing operations. For capacity planning, use our Odoo server requirements guide and validate the proposed setup with representative activity.
Choose it when: the additional control solves a concrete requirement and you have a team or provider to operate it. Include that work when comparing costs.
When to consider ERPixel hosting
When is ERPixel.sh an alternative to Odoo.sh?
Consider ERPixel.sh when you want an isolated server, predictable recurring costs and a hosting team you can call. Compare the services you actually need: 40 GB disk, test and staging are included, while server resources are agreed for your workload. Odoo.sh remains useful when its integrated GitHub builds and branch workflow are central to your project.
Use the licence and hosting cost comparison to compare the same payment period. An Odoo.sh shared-hosting example and an ERPixel isolated server do not provide identical resources. ERPixel includes daily backups plus a weekly copy, test, staging, SSL, an ERPixel subdomain and Odoo email connection. Check recovery responsibilities and application support when comparing the complete service.
If you prefer a provider to run a separately hosted Odoo environment, Compare ERPixel.sh Odoo hosting plans: both Enterprise and Community use an isolated server in Europe or the United States, with 40 GB disk, test and staging included. Small Community projects can receive an individually agreed discount. ERPixel monitors server availability 24/7, receives incident alerts and uses automated recovery procedures. A real team is available by phone when you need to discuss a problem.
Use the estimate below to choose your options and compare recurring and one-time costs. Hosting setup, backups, test, staging, domain access, SSL and Odoo email connection are included. Enterprise licences and VAT are excluded. Migration and application support should be scoped separately.
Use the calculator below to compare an ERPixel configuration with your Odoo.sh budget. Its Odoo.sh reference rates are a November 9, 2026 snapshot in EUR with monthly payment, not a live price feed or a like-for-like total. Check the official calculator for the currency, billing term and market applicable to your purchase. You can see the result without entering contact details; requesting a formal quote is optional.