Odoo hosting is where your Odoo runs and who keeps it running well. That means the server, the database, backups, updates, speed and security. Odoo can do it for you, a hosting company can do it, or you can rent a server and do it yourself. Some companies run it in their own building.
Getting Odoo to start is the easy part. Keeping it fast, safe and backed up a year later is the real job. So when you pick a hosting option, you’re really picking who does that job.
Here are the six options, what each one is good for, and what work stays with you.
The six options at a glance
Option | Who it fits | What you run yourself | What it costs to run |
|---|---|---|---|
Odoo Online | Teams happy with the standard Odoo apps, no custom code | Nothing | A fee per user, paid to Odoo |
Odoo.sh | Odoo Enterprise users with their own code | Your code. You pick the server size | Your Enterprise plan, plus the hosting you choose |
Managed Odoo hosting | Teams that want Odoo run for them, on Community or Enterprise | Your code, if you have any | A monthly plan from the host |
A VPS you run yourself | People who have run Odoo in production before | Everything: server, Odoo, backups, updates, security | The server bill, plus your time every month |
Your own server, run by a host | Teams with their own cloud account, or in a country no host covers | You keep the server up. The host runs Odoo on it | Your server bill, plus a fee for running Odoo |
On-premise | Banks, insurers, health and public bodies. Data can’t leave the network | Your team runs Odoo, with software that does the hard parts | A software licence, plus your own servers and staff |
Option 1: Odoo Online (Odoo SaaS)
Best for: teams that use the standard Odoo apps as they are.
Odoo Online is Odoo’s own cloud. You sign up on odoo.com, pick your apps and start. There’s no server to think about at all.
The limit is code. You can’t add your own modules or modules from the Odoo Community Association (OCA). If you need a custom feature or a link to another system, you will outgrow it.
If the standard apps do what you need, this is the simplest choice. You probably don’t need anyone else.
Option 2: Odoo.sh
Best for: Odoo Enterprise users with their own code who want to deploy from Git.
Odoo.sh is Odoo’s hosting for custom code. You connect a Git repository. Each branch can be production, staging or development. You push code and it deploys. Build logs and a shell are built in.
The main thing to know: Odoo.sh only runs Odoo Enterprise. A lot of teams are choosing Community right now. If you’re one of them, Odoo.sh isn’t an option.
If you want the same way of working on Community, or with GitHub, GitLab or Bitbucket, look at an Odoo.sh alternative.
Option 3: Managed Odoo hosting
Best for: teams that want Odoo run properly without it becoming their job.
A managed host runs the server and Odoo for you. You get deploys from Git, staging copies, backups, updates and support. You use Odoo, and they look after what’s underneath.
Not every host does the same amount of work. Before you sign up, ask:
- Which editions? Community, Enterprise or both.
- Is there an SLA? A written promise on uptime and on how fast support answers.
- Who checks their security? Look for an outside audit, like ISO 27001.
- Which Git services? GitHub, GitLab, Bitbucket.
- Staging? Can you test on a copy of production before you go live?
- Backups? Are they kept off the server, and are restores tested?
- Can you leave? Can you download your database and files at any time?
That last one matters most. If you can download a full backup whenever you like, you’re never stuck.
See how managed Odoo hosting works on Skysize.
Option 4: A VPS you run yourself
Best for: people who have already run Odoo in production.
You rent a server from a cloud company. You install Postgres, Odoo and a web server. You set up the SSL certificate, backups and updates. From then on, it’s yours to look after.
Starting this way makes sense. It’s cheap, and Odoo can be up in an afternoon, often with a little help from AI. The trouble comes later, and it comes quietly:
- Odoo gets slow at busy times because the workers were never sized for your users.
- Live updates and chat stop working because one setting is missing.
- Logs fill the disk, a little more every week.
- Backups run every night, but nobody has ever tried to restore one.
- Updates wait, because nobody wants to be the one who breaks production.
None of this shows on day one. It shows up as hours, every month. In our experience a self-run Odoo takes 20 hours a month to keep in good shape, and more in a bad month. Those hours come out of your real work.
Then, maybe once, the bad day comes: a restore that doesn’t work, on the day you need it.
If you have run Odoo in production before, a VPS is a fair choice. If you haven’t, compare the real cost first: self-hosting vs managed
Option 5: Your own server, run by a host
Best for: teams with their own cloud account, or in a country where no host has a data centre.
You keep your server, in your account, in the country you choose. A host connects to it and runs Odoo on it: deploys, staging, backups, updates and help from Odoo experts.
The work is split, so be clear about who does what. You keep the server up and big enough. The host takes care of everything Odoo needs.
On Skysize this is called bring your own server. Our software connects out from your server. You don’t open any port to us.
Option 6: On-premise
Best for: banks, insurers, health care and public bodies, where data can’t leave your own network.
Odoo runs on your own servers, inside your own network. It can even run with no internet link at all. Your IT team operates it. Software does the hard parts for them: deploys, staging, backups, updates and checks.
The difference from the options above: no one outside your company touches your Odoo. Your team stays in charge, and the software brings the know-how they’d need years to build.
See how Odoo on-premise works.
Community or Enterprise? Ask this first
Your edition decides half the list.
- On Community: Odoo Online and Odoo.sh are both out. You choose between a managed host that supports Community, your own server, or on-premise.
- On Enterprise: all six are open to you. Compare who does the work, the support you get, and how easy it is to leave.
How to choose in one minute
If this is you | Look at |
|---|---|
Standard apps, no custom code | Odoo Online |
Enterprise, custom code, you like Git | Odoo.sh or managed hosting |
Community, with or without custom code | Managed hosting |
You’ve run Odoo in production before and enjoy it | A VPS |
You have your own cloud account, or no host covers your country | Your own server, run by a host |
Your data must stay inside your network | On-premise |
You’re an agency hosting Odoo for clients | Managed hosting or your own server |
Can you change your mind later?
Yes. Your Odoo is a database and a folder of files. With any good host you can download both at any time and take them somewhere else. On Skysize you can start on our cloud and move to your own server later, or the other way round.