Odoo hosting options: which cloud or on-premise set-up fits your business?

Searching for Odoo cloud usually means one question: where will our system run, and who will be responsible for it? The answer is not a single option. Odoo can be hosted in three ways, and each one changes what you can customise, who handles upgrades, who owns the backups and how much effort your team carries.

For a UK business, the choice also touches data protection, your accountant's access and the way the system connects to HMRC services. This page explains the options as Odoo itself documents them, so you can brief an integrator with the right questions.

The three ways to host Odoo

According to Odoo's documentation, Odoo Enterprise can be hosted on three platforms:

• Odoo Online, the software-as-a-service (SaaS) offer, run entirely by Odoo.
• Odoo.sh, a platform-as-a-service (PaaS) and dedicated cloud for custom code.
• On-premise, on your own infrastructure.

People often say "Odoo SaaS" when they mean Odoo Online, and "Odoo cloud" when they mean either of the first two. A partner may also offer managed hosting of its own, in which case you should ask exactly what is included in the service and which Odoo platform sits underneath it. The ground rules below apply whichever label is used.

Odoo Online (SaaS): the simplest route

With Odoo Online, the hosting and the migration from one version to the next are managed by Odoo. There is no server to buy or patch, and a database can be live quickly once the scope is agreed.

The trade-off is flexibility. Odoo states that Odoo Online is not compatible with non-standard applications: only Odoo's own applications can be installed, with no third-party modules and no changes to the code.

In practice, Odoo Online suits a business whose processes fit the standard applications, which is often the case for a services firm, a small distributor or a company replacing spreadsheets and a basic accounting package. If you want to see how far the standard catalogue goes before deciding, read the overview of Odoo modules.

Some things to confirm with your integrator before choosing this route:

• Whether every integration you need works without custom code, for example your bank feeds, payment provider or courier. The page on Odoo integrations is a good starting point.
• Whether a standard-only approach is acceptable to your finance team, particularly for VAT reporting under Making Tax Digital.
• Whether the plan you buy covers the features you need. Studio, multi-company and external API access belong to the Custom plan, not Standard.

Odoo.sh: cloud hosting for custom code

Odoo.sh is described by Odoo as the official cloud platform for hosting customised code. Its documented features include:

• GitHub integration;
• development, staging and production branches;
• continuous integration;
• SSH access, a web shell and an online editor;
• automatic backups.

For a growing company with specific workflows, this is the route that combines cloud hosting with real development discipline. Developers work on a branch, test on a staging copy of production data, and promote to production when the result is accepted. That is much safer than editing a live system.

Odoo.sh is only available on the Custom plan, and Odoo notes that Odoo.sh costs are not included in the Custom plan price. When you compare quotes, always ask for the platform cost to be shown separately so that you are comparing like with like. The page on Odoo pricing sets out how plans and extras fit together.

It also changes who is accountable. Because custom code lives in your repository, someone has to maintain it each time you move to a new version. That is a good reason to agree a maintenance arrangement from the start; see Odoo support and maintenance.

On-premise: full control, full responsibility

With an on-premise installation, you run Odoo on infrastructure you control. That might be your own server room, a UK data centre or a virtual machine at a hosting provider you select. Odoo describes the trade-off clearly: the company keeps full control and full responsibility. Customisation and third-party modules are possible, and both the Enterprise and Community editions can be used. Maintenance, backups and data security are your job.

On-premise only makes sense if you have a clear reason, such as:

• a security policy or customer contract that dictates where the system must sit;
• heavy customisation or unusual integrations with systems on your own network;
• an in-house IT team, or an integrator under contract, able to run the platform properly;
• a manufacturing or warehouse site where a local connection matters.

Without those, the operational burden often outweighs the benefit. Patching, monitoring, restore testing and capacity planning do not disappear; they simply move to you.

Side-by-side comparison

Community or Enterprise: how licensing affects hosting

Hosting is linked to the edition you use. Odoo offers Community, which is open source, and Enterprise, which is sold under licence. The official editions page states that Community is the base on which Enterprise is built, and that you can move from one to the other at any time.

For Odoo 19, Community is released under the LGPL version 3. Enterprise is covered by the Odoo Enterprise Edition Licence v1.0, which requires a valid Enterprise subscription for the right number of users. This matters for hosting because a free self-hosted Community installation is a different undertaking from a subscription-based Enterprise one. For a closer look at editions, see Odoo versions and editions.

Enterprise also brings features that some businesses consider decisive. Odoo's editions page mentions AI-assisted invoice automation, advanced manufacturing features such as Shopfloor and scheduling, Studio, and Field Service. If your plan relies on these, a pure Community installation is unlikely to be enough.

Customisation, upgrades and total cost

The three routes differ most in what happens after go-live.

Customisation. Odoo Online stays close to standard. Odoo.sh and on-premise allow bespoke development. If you expect bespoke development, read Odoo customisation first, because every line of custom code is a line you must keep working.

Upgrades. On Odoo Online, Odoo manages the migration to a new version. Where you have custom code, an upgrade is a project: modules are adapted, tested on staging and then released. The page on Odoo migration describes what that involves.

Cost. Odoo publishes plan prices per user and per month, with hosting included for Odoo Online. Odoo's pricing counts as paying users those with backend access; portal users such as customers and suppliers are not counted as paying. For on-premise, you add the cost of servers or virtual machines, backup storage, monitoring and the time of whoever administers the platform. Cloud hosting does not make the work vanish; it changes which line of the budget it appears in.

Data location, UK GDPR and backups

Where the data sits is a legitimate question for any UK business, particularly one handling employee records through payroll or customer data in a CRM. Under UK GDPR you remain responsible as the data controller, whichever hosting you pick.

Odoo's pricing page states that its plans include daily backups on two continents and round-the-clock monitoring. That tells you something about resilience, but it does not by itself answer the question of the precise location of your database. Before signing, ask:

1. In which country or region will the production database and its backups be stored?
2. What contractual terms cover personal data processing, and who are the sub-processors?
3. How are restores handled, and can a test restore be demonstrated?
4. What happens to the data at the end of the contract, and how can you export it?

For on-premise or a partner-managed server, add your own questions on encryption, access control and disaster recovery. If you will run payroll in Odoo, the page on Odoo payroll and HR explains the scope, and the guide to payroll software and RTI covers what UK payroll reporting requires of any system. For wider context, see our guide to cloud versus on-premise ERP.

How to choose: a practical decision path

You do not need to settle the question in the abstract. Work through these steps with your integrator.

1. List your must-have processes. If all of them are covered by standard applications, Odoo Online is the natural starting point.
2. Flag any bespoke requirement. Any need for third-party modules or code changes rules out Odoo Online and points to Odoo.sh or on-premise.
3. Decide who will own technical operations. If you have no IT team, avoid on-premise unless the integrator takes it on under contract.
4. Check data and compliance requirements. Involve your accountant and whoever handles data protection, especially if you must evidence where the data is held.
5. Compare total cost, not the subscription alone. Include the platform, development, upgrades, backups and support.
6. Plan the exit. Know how you would export data or change hosting later.

A short, scoped Odoo implementation plan should state the hosting decision explicitly, together with the reason for it. If you already run Odoo and are unsure whether the current set-up still fits, an Odoo audit is a sensible way to review hosting, custom code and upgrade readiness.

Which type of business tends to choose what

These are tendencies, not rules.

• An accountancy-led services firm with standard needs, timesheets, invoicing and a modest IT function often chooses Odoo Online. The Odoo accounting and finance pages help check that the standard scope is enough.
• A manufacturer or distributor with specific workflows frequently lands on Odoo.sh so that bespoke logic can be developed, tested and released in a controlled manner.
• A company with strict network or contractual constraints might take the on-premise route, accepting the extra operational load.

Whatever the profile, hosting should be judged alongside the rest of the project, not after it. A partner who understands UK requirements, from VAT and Making Tax Digital to payroll submissions, will shape the hosting choice around them. If you are comparing partners, choosing an Odoo partner lists what to ask, and our Odoo in the UK page puts the product in a local context.

Next step

ERP Integrator is a free matching service. We are not affiliated with Odoo and we do not carry out the project ourselves: we introduce you to an integrator suited to your scope, and that integrator advises on hosting, plan and licensing. Tell us about your business, the processes you need and any constraints on data location, and we will help you find a suitable match. You can see how it works on the how it works page.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.