How to choose Odoo hosting, a neutral decision guide

The two questions that decide it

Most Odoo hosting decisions come down to two questions. Answer them honestly and the list of options shrinks from dozens to two or three.

1. Will you run custom Python modules? That includes your own code, OCA modules and App Store modules. If the answer is no and you are happy with Enterprise, the simplest option is on the table. If the answer is yes, it is not.
2. Who operates the servers? Nobody on your team, someone part-time, or an engineer who knows Linux and PostgreSQL. Operating Odoo means upgrades, backups you have test-restored, monitoring, security patches and someone answering when it is down at 7 in the morning.

Two more questions refine the choice: Community or Enterprise (Community is only possible where you control the hosting) and where the data must live (a country, a specific cloud account, or your own hardware).

This guide describes each category as of September 2026. It does not quote prices: pricing changes often, so each section describes how the category charges and you should check the provider's own pricing page.

The six categories at a glance

The lines between the last three are blurry. Some control panels sell a managed tier, some managed hosts give you panel access. Read each provider's terms rather than trusting the label.

Odoo Online: SaaS, no custom code

Odoo Online is Odoo's own hosted SaaS. You sign up, choose apps and use them. Odoo runs everything, including upgrades.

• Good for: small and mid-sized companies using standard apps, with changes made through configuration and Studio.
• Limits: no custom Python modules and no third-party modules from the App Store or OCA. You follow Odoo's upgrade schedule. External API access depends on your plan, so check it if you plan integrations.
• Pricing structure: a subscription per user per month, varying by plan. See odoo.com/pricing.

If you have no developers and no need for custom code, this is often the right answer and you do not need anything else in this guide.

Odoo.sh: the official platform for Enterprise with custom code

Odoo.sh is Odoo's platform-as-a-service. You connect a GitHub repository, and each branch can become a development, staging or production environment. It is the official choice for Enterprise customers who need custom modules without running servers.

• Good for: Enterprise teams on GitHub who want Odoo to run the infrastructure, and Odoo partners building for such clients.
• Limits: Enterprise only, GitHub only, hosted in Odoo's infrastructure and regions. You get shell access to the containers but not root on a server you control. Scaling happens through Odoo.sh's own options.
• Pricing structure: on top of the Enterprise user subscription, Odoo.sh bills for hosting resources such as workers, storage and extra staging environments. See odoo.sh/pricing.

For a detailed look at where it fits and where it does not, see our Odoo.sh comparison and Odoo.sh alternatives.

A raw VPS: do it yourself

Rent a Linux server from any provider, install PostgreSQL, Odoo and nginx, and operate it yourself. This is the lowest direct cost and the highest amount of your own time.

• Good for: teams with a Linux engineer who has time, a single database, and appetite for learning Odoo's operational details.
• Limits: everything is yours: TLS certificates, backups to off-site storage, restore testing, monitoring, OS patches, Odoo upgrades, staging environments and a deploy process. The cost is people's time, and it grows with each extra database.
• Pricing structure: your cloud provider's server bill, plus your storage and bandwidth.

If you go this way, start with how to self-host Odoo 18 in production or the Docker Compose production guide, and put backups in place on day one with Odoo backups to S3.

Control panels on your own servers

A control panel is software (usually a hosted web app) that connects to servers you rent and handles the Odoo-specific work: creating instances, deploying from Git, TLS certificates, backups and monitoring. You keep the servers in your own cloud account, and the panel does the repetitive parts.

• Good for: agencies and in-house teams running several databases, who want Community or Enterprise, their own cloud account and a proper deploy process, without writing it all themselves.
• Limits: you still own the servers, so capacity planning and the cloud bill are yours. Panels differ a lot in depth: how they handle Git, staging, backups, team permissions and support. Check whether leaving the panel leaves you with working servers and your data.
• Pricing structure: a platform fee to the panel provider (the unit differs: per account, per server, per instance or quoted), and your cloud provider bills the servers separately.

Examples in this category include Cloudpepper, OEC.sh, DeployMonkey, InstPloy and CICDoo. Each works differently, see the head-to-head pages: CICDoo vs Cloudpepper, CICDoo vs OEC.sh, CICDoo vs DeployMonkey and CICDoo vs InstPloy.

Fully managed Odoo hosts

A managed host runs Odoo on its own infrastructure and handles the operations for you. You get an Odoo instance and a support contact, not a server.

• Good for: companies that want someone else to own uptime, and do not need to choose the cloud provider or hold the servers themselves.
• Limits: what you can install and how you deploy custom code depends on the host. Your data lives in their infrastructure, so check backup access and export terms before you sign.
• Pricing structure: usually a single bundled fee covering hosting and operations, often by resource size or number of users. Check the provider's pricing page.

Examples include Skysize (managed offering) and EasyInstance. See CICDoo vs Skysize and CICDoo vs EasyInstance.

Managed service by engineers

This is people, not a platform: an Odoo partner, an agency or a DevOps provider operates your Odoo for you, often on servers in your own account. The difference from a managed host is that the arrangement is built around your setup and usually includes upgrade and incident work by named engineers.

• Good for: companies with business-critical Odoo, custom code and no in-house operations team.
• Limits: quality depends entirely on the team. Ask who is on call, what the response times are in writing, and how you get your data and access back if you leave.
• Pricing structure: a retainer or a quote per project, plus infrastructure.

Decision table by team type

What to check before you commit

Whatever you pick, get clear answers to these, in writing where it matters:

• Backups. How often, where they are stored, how long they are kept, and whether you can download a full backup (database and filestore) yourself. Test a restore before go-live.
• Staging. Can you get a copy of production to test changes and upgrades on, with outgoing email disabled?
• Deploys. How custom code gets from Git to production, and how you roll back a bad release.
• Upgrades. Who runs the next major Odoo upgrade and how it is tested. See upgrading Odoo 17 to 18 for what that involves.
• Access. Shell access, database access, logs. Can you debug a problem yourself at night?
• Security. Two-factor login, team permissions, audit logs, who at the provider can access your data.
• Exit. If you leave, what you walk away with: servers, data, backups, code. The best time to ask is before you move in.
• Edition. Community or Enterprise, and whether the option supports both. See Community vs Enterprise when self-hosting.

Where CICDoo fits

CICDoo is a control panel on your own servers, with an optional managed layer. You connect Linux servers you own, from any provider with SSH, and link a GitHub or GitLab repository. Each branch becomes an Odoo instance in a development, staging or production stage, in its own Docker container, with nginx and automatic SSL certificates. It covers backups to S3-compatible storage, uptime and resource monitoring with alerts, a browser console with live logs and a web IDE, per-user SSH access, team workspaces with per-resource permissions, and white-label workspaces for agencies. It supports Community and Enterprise, 11.0 to the latest release, plus master.

There are no per-user fees and no compute markup: you pay your cloud provider directly for the servers, and paid access to CICDoo is quoted per project. If you want CICDoo engineers to run it for you, see managed operations. The Odoo hosting overview and features have the details, or talk to us.