You've chosen Odoo. Great, but then the next question follows immediately: where are you going to run it? There are three flavours: Odoo Online, Odoo.sh and your own server (or own cloud). All three are perfectly good options, but for different situations. And unlike a phone contract, you're not tied to it forever: you can still switch later. Here is the decision guide.
Odoo Online: getting started without hassle
Odoo Online is the SaaS variant: Odoo hosts everything, you log in and work. Updates, backups and security are taken care of, and hosting is included in your Enterprise subscription. There is one important limitation: you cannot install your own custom modules. You can configure to your heart's content, and with Studio you can adapt fields and views, but real custom code is not possible. For many SMEs that stay close to the standard, that is more a blessing than a loss: it forces simplicity and keeps upgrades painless.
Odoo.sh: the best of both worlds
Odoo.sh is Odoo's managed platform for businesses that do need custom development. You work git-based: every change goes through a repository, and you get staging branches on which you test changes with a copy of your production data before they go live. Odoo handles the servers, monitoring and backups; you (or your partner) manage the code. The costs depend on the number of workers, storage and staging environments: for an average SME environment, count on roughly €100 to €400 per month, on top of your Enterprise licences. For most businesses with custom development, this is the logical choice.
Your own server or own cloud: full control
On-premise or in your own cloud environment (for example a VPS or a Dutch hosting provider) you have full control: over the data, the infrastructure, the version and the pace of updates. That freedom comes at a price in responsibility. Updates, security patches, backups, monitoring and recovery after outages: it is all yours. The server costs themselves are modest (from a few tens of euros per month for a decent VPS), but you structurally need someone who takes the maintenance seriously. Choose this if you have specific requirements around data location or integrations, or if you run Community, because that only runs on your own hosting.
How to choose
- Choose Odoo Online if you stay close to standard Odoo, don't want technical maintenance and want to start quickly.
- Choose Odoo.sh if you have custom modules or integrations and want a professional test and deployment pipeline without your own servers.
- Choose your own hosting if you use Community, demand full control over your data and infrastructure, and have the maintenance covered.
Good to know: the migration paths are passable. Switching from Odoo Online to Odoo.sh is possible if you come to need custom development; your database moves with you. The other way round is also possible, although custom development then has to be phased out first. And from your own server to Odoo.sh (or back) is essentially a database migration. So your first choice is important, but not final.
Praktische tip
Choose your hosting based on your need for custom development two years from now, not today's. Do you expect integrations with a webshop, EDI or industry software? Then start on Odoo.sh straight away and save yourself an interim move. Sticking with standard? Then Odoo Online is the cheapest and calmest route.
Not sure which variant suits your situation? Contact DAADit Group, then we'll set out the options for you with real figures.