Self-hosted Odoo, without the 2am pager
Run Odoo Community or Enterprise on servers you own, at any provider. CICDoo automates the parts that make self-hosting hard: deploys from Git, staging copies, backups, monitoring, SSL and upgrades.
Your servers, your data, your backups. No per-user fees.
development
feature/*
staging
staging
production
main
The short answer
What self-hosted Odoo actually means
Self-hosted Odoo means the Odoo server, its PostgreSQL database and its filestore run on infrastructure you control: a cloud VM at Hetzner, AWS, DigitalOcean, OVH or Azure, or hardware in your own rack. You choose where the data lives, who can reach it, which modules are installed and when upgrades happen.
Both editions can be self-hosted. Odoo Community is open source (LGPLv3) and free to run. Odoo Enterprise can also run on your own servers: you need an Enterprise subscription for the users, and access to the enterprise addons that come with it. The software is the same one Odoo runs on its own cloud.
The trade-off is operations. Odoo Online and Odoo.sh do the server work for you, in exchange for their limits on hosting, pricing and customisation. Self-hosting removes those limits and hands you the work: deployments, staging copies, backups you have actually restored, monitoring, certificates, security patches and version upgrades. That work is what CICDoo automates.
The checklist
Everything production Odoo needs, handled
Self-hosting Odoo well is the same eight jobs every time. Here is each one, and what CICDoo does about it.
Deploy from Git
Push to a branch and that branch builds and deploys to its own Odoo instance, with your custom and OCA modules on the addons path.
Staging and dev stages
Development, staging and production stages per project, so a module update is tested on real data before it reaches users.
Backups you can restore
Scheduled and on-demand backups of database and filestore to S3-compatible storage, downloadable and restorable in a click.
Monitoring and alerts
Uptime checks and server and container metrics, with alerts by email, Telegram and SMS when something goes wrong.
Domains and SSL
Point a domain at an instance and the certificate is issued and renewed automatically behind an nginx reverse proxy.
Isolated containers
Each instance runs in its own Docker container on your server, so one client or stage can never take down another.
Console and SSH
Live logs, a web IDE in the browser and per-user SSH access, without handing out the server root password.
Team permissions
Workspaces with per-project and per-action permissions, two-factor authentication and an audit trail.
Your options
Three ways to self-host Odoo
Doing it by hand, with a control panel, or with a platform and engineers behind it.
| By hand on a VPS | Hosting control panel | CICDoo | |
|---|---|---|---|
| Servers you own | Yes | Usually | Yes, any Linux server with SSH |
| Deploy from Git | Write your own scripts | Usually | Per branch, per stage |
| Staging with real data | Manual copy | Varies | Built in |
| Backups and restore | Cron plus scripts | Usually | S3-compatible, one-click restore |
| Monitoring and alerts | Set up separately | Varies | Email, Telegram, SMS |
| Community and Enterprise | Yes | Varies | 11.0 to latest, plus master |
| People to call | You | Support desk | Engineers, or fully managed |
Comparing specific products? See every Odoo hosting option compared.
How it works
From an empty server to production Odoo
-
1
Connect a server
Any Linux server with SSH, at any provider, or one you already run. CICDoo prepares Docker, PostgreSQL and nginx on it. Read the docs
-
2
Link your repository
GitHub, GitLab.com or self-hosted GitLab. Your branches become development, staging and production instances. Read the docs
-
3
Pick edition and version
Community or Enterprise, 11.0 to the latest release, plus master. Upload an existing backup or start fresh. Read the docs
-
4
Add a domain
Point DNS at the server; the SSL certificate is issued and renewed for you. Read the docs
-
5
Push and ship
Every push deploys that branch. Backups, monitoring and alerts run from day one. Read the docs
Guides
Go deeper
FAQ
Questions, answered
Can you self-host Odoo?
Yes. Both Odoo Community and Odoo Enterprise can run on your own servers. Community is open source under LGPLv3. Enterprise needs a valid Odoo Enterprise subscription for its users and the enterprise addons, but runs on the same Odoo server you would self-host for Community.
Is self-hosted Odoo free?
Odoo Community is free to download and run; you pay for the server, your time or someone else's to operate it, and any paid apps. Odoo Enterprise is licensed per user by Odoo, whether you self-host or not. CICDoo adds no per-user fee: you pay your cloud provider for servers directly, and CICDoo access is quoted per project.
What server do I need to self-host Odoo?
For a small company, a VM with 2 to 4 vCPUs, 4 to 8 GB of RAM and SSD storage runs Odoo and PostgreSQL comfortably. Size up with concurrent users, workers and the volume of scheduled jobs. Ubuntu LTS with Docker is the most common base today.
Is self-hosting Odoo secure?
It can be more secure than shared hosting, because you control the network, the database access and the patch schedule. It is only as secure as its operations: HTTPS, a locked-down database manager, restricted SSH, current patches, tested backups and monitoring. CICDoo automates most of that list.
Can I move from Odoo.sh or Odoo Online to self-hosted?
Yes. Export a backup (database and filestore) from Odoo.sh or request one for Odoo Online, restore it on your server with the same Odoo version, bring your custom modules from Git, then switch DNS. We help plan the move.
Do I still get support if I self-host?
With CICDoo, yes: tickets are answered by engineers who run Odoo, and fully managed operations are available if you would rather not run it yourself.
Self-hosted Odoo, minus the chores
Connect a server, link your repository and ship. Or talk your setup through with an engineer first.
No per-seat fees. Your servers stay yours.