Odoo hosting, on our cloud or your server
The Odoo.sh workflow, independent: every GitHub branch runs as its own Odoo, staging tests on a copy of production, and releases go live with a drag and drop. Already have a server? We install Odoo on it, then monitor, back up and secure it for you.
- Odoo 14 to 20, Community and Enterprise
- Daily backups, restore-tested weekly
- Any server: AWS, Hetzner, DigitalOcean, your own
- 14 → 20 Odoo versions (Community and Enterprise)
- 1 command to link a server (then install Odoo in a few clicks)
- 7 · 4 · 3 daily, weekly, monthly backups (restore-tested every week)
- Every PR gets its own preview (with a GitHub check and a comment)
You pick where Odoo runs. We run the rest.
Start on our cloud, keep your own server, or use both. The same dashboard, team accounts, backups and alerts either way.
On our cloud
Fully hosted
The Odoo.sh workflow on servers we operate. Every branch is an environment, and servers, backups and updates are our job.
- Development, staging and production from GitHub
- Staging on a neutralized copy of production
- A preview for every pull request
- Web shell, SSH, editor and the kv CLI
- OCA Apps catalog, AI help with failed builds
- Odoo 14 to 20, Community and Enterprise
From $72 per worker per month. Configure a plan
On your own server
Bring your own server
Keep Odoo on a VPS or machine you own. We install it, watch it, back it up and keep it secure, without moving anything.
- Link any server with one command
- Install Odoo 17 to 20 in a few clicks
- Monitoring, live logs and push alerts
- Daily backups, offsite copies, restore tests
- Security audit with guided fixes
- Recorded web terminal, for the owner only
Server Pro from $2 per server per month. Install on your server
From git push to production in three steps
The workflow Odoo teams already know: branches are environments, and releases move up through the stages.
Connect GitHub
Sign in with GitHub and pick a repository. We install the webhook and report build status on your commits.
Push a branch
Every branch builds into its own Odoo with a URL, logs and a shell. Tests run on development builds.
Promote to production
Drag the branch to staging to test it on a copy of production, then merge it into production.
Install Odoo on your server in four steps
No guide to follow and nothing to type on the server after the first command. The installer checks the machine, fixes what it can by itself and shows every step live.
Link the server
Run one command as root. The server appears with its CPU, memory, disks and any Odoo already on it.
Choose your Odoo
Version 17, 18, 19 or 20, Community or Enterprise, your domain, apps, language and country.
Review the plan
See what's fine as it is and what we'll do for you: swap, Docker, free ports, disk clean-up.
Go live
Follow the install live, in about 8 to 15 minutes. HTTPS is added as soon as your domain points to the server.
The whole Odoo platform, not just a server
What a serious Odoo project needs every day, from the first push to the fifth year in production, on our cloud or your own server. No add-ons to buy.
GitHub push-to-deploy
Connect a repository and every branch becomes a running Odoo with its own URL. Each push builds it again.
Development, staging, production
Three stages, like you know them. Drag a branch from one stage to the next, or merge it, right from the Branches page.
Staging copies of production
Staging builds start from a neutralized copy of production: emails are caught and scheduled actions are off.
Pull request previews
Every pull request gets its own development environment on a fresh database, with a GitHub check and a comment linking to it.
Odoo 14 to 20
Community or Enterprise, on every version from 14.0 to 20.0, built from the official Odoo images.
Apps catalog of OCA modules
Search thousands of the Odoo Community Association's modules for your Odoo version and add them to a development branch without touching git.
Custom domains, automatic HTTPS
Point your domain at any branch and a certificate is issued for it automatically. The dashboard shows each step.
Import an existing database
Moving in? Bring a backup from Odoo.sh, Odoo Online or any host: upload it, paste a download link, or fetch it from a running Odoo's database manager.
Link any server in one command
Run one command as root on your server, at AWS, Hetzner, DigitalOcean, Linode or in your own rack, and it shows up in the dashboard with the Odoo instances it runs.
Install Odoo on your server
Odoo 17, 18, 19 or 20, Community or Enterprise, in a few clicks. The installer prepares the server by itself and adds your domain with HTTPS as soon as its DNS points there.
Server monitoring and alerts
Every 5 minutes: load, memory, disks, each Odoo instance and each domain with its certificate. You're alerted when something goes down or fills up.
Backups of your server's Odoo
Daily backups of each database in Odoo's own zip format, checked, copied offsite encrypted, and restored as a test every week.
Security audit and guided fixes
A daily, read-only audit of the server and each Odoo: open database manager, exposed ports, SSH settings, pending updates, HTTPS. Graded from A to F.
Recorded web terminal
A root shell on your server, in the browser, for its owner only: a fresh sign-in, plus your two-factor code when two-factor is on.
Web shell and SSH
A terminal inside the build, with Odoo shell, Python and SQL consoles. Or SSH in with the keys from your GitHub account.
Online editor
Edit, commit and push from a code editor in the browser, with terminals and git next to your files.
Jupyter notebooks
Open JupyterLab on any build with env ready to use, like odoo shell. Nothing runs until you open one.
Logs for every phase
Install, update, pip and server logs per build, plus slow SQL queries, streamed live to the dashboard.
Explain this failure, with AI
A failed build, restore, backup or Odoo install gets a plain-English explanation from Claude: what failed, the likely cause and the steps to fix it.
Monitoring
CPU, memory, requests, response times, storage and emails graphed per branch, with releases marked on the timeline.
Performance advisor
A daily score with prioritized recommendations for production: slow requests and SQL, missing indexes, scheduled actions, workers and memory.
Mail catcher
Emails from development and staging never reach a real person. Read them in the Mails tab instead.
Auto-sleep of idle environments
Development and staging builds nobody visits go to sleep, and wake up on the next visit. Production never sleeps.
Daily backups, tested
Production is backed up every day and kept for about three months. Each week the newest backup is restored as a test.
Encrypted offsite copies
When offsite storage is set up, backups are encrypted on the server, then copied to storage in another location. The provider only sees ciphertext.
A private network per environment
Production, staging, each development branch and each pull request preview run on separate private networks, each stage with its own database role.
Uptime and status page
Every server is checked once a minute. The project's Status page shows uptime over the past day, week and month.
Downtime alerts
When production stops answering, you get a notification and an email, and another one when it's back.
Upgrade assistant
A readiness report of every installed module, a test upgrade on a copy of production with smoke checks, then production when you're ready.
Maintenance windows
Choose when production may restart. Pushes can wait for the window, and platform rebuilds and restarts always do, then run in order.
Two-factor sign-in
Authenticator-app codes with one-time recovery codes for password accounts, and a platform switch that makes two-factor mandatory.
Public status page
Platform health per region, with 90 days of uptime, incident history, email updates and an Atom feed.
Team accounts for companies
Create an organization, invite your people as owners, admins, billing or members, and pay for projects and servers as the company.
Collaborators and roles
Invite your team as admins, testers or developers, with access to each stage that matches the role.
Client portal and support plans
Clients whose Odoo we manage get their own view: status, uptime, backups and monthly reports, with support requests answered within their plan's response time.
Partner and reseller program
Odoo partners bring their clients with a discount or a commission, and a partner portal to buy hosting and create projects for them.
Monthly reports
On the 1st of each month, project admins get last month's report: uptime and incidents, deploys, backups and restore tests, storage growth and a health score.
kv, the command-line tool
Status, rebuilds, live logs, backups and database dumps from your terminal or CI. Sign in through your browser and kv gets a scoped token of its own.
API and access tokens
Script the platform and trigger rebuilds from CI with personal access tokens, scoped to reading, builds, backups or admin, and documented in the API reference.
An app with push notifications
Install the dashboard on your phone's home screen or your computer, and get failed builds and backups, a linked server going down and support replies as push notifications.
Chat notifications
Builds, deploys, backup failures and downtime posted to Slack, Discord, Microsoft Teams or a signed webhook.
Help chat, then a human
The help chat answers from our documentation and cites its sources. Not enough? Talk to a human and the team gets the whole conversation.
Your data, portable
Download any backup as a standard Odoo backup, and export your account or a project's data whenever you want.
Same workflow. Independent infrastructure.
If you have used Odoo.sh, you already know how Knova Cloud works. The difference is who runs it, that Community projects are welcome too, and that it can be your own server.
| Capability | Odoo.sh | Self-managed server | Knova Cloud |
|---|---|---|---|
| Every branch is an environment, pushed from GitHub | Yes | No | Yes |
| A preview for every pull request, forks included | Yes | No | Yes |
| Development, staging and production stages | Yes | No | Yes |
| Staging on a neutralized copy of production | Yes | No | Yes |
| Web shell, SSH, online editor, logs | Yes | SSH only | Yes |
| Community (OCA) modules added in a few clicks | Yes | Do it yourself | Yes |
| Daily backups, custom domains with HTTPS, mail catcher | Yes | Do it yourself | Yes |
| Odoo Enterprise | Yes | Yes | Yes |
| Odoo Community | Enterprise only | Yes | Yes |
| Runs on a server you own | No | Yes | Yes |
| Operated by | Odoo S.A. | You | Knova Cloud |
Odoo.sh column based on Odoo's public documentation at the time of writing. Self-managed means a server you install and look after yourself. Odoo and Odoo.sh are trademarks of Odoo S.A. Knova Cloud is an independent service, not affiliated with or endorsed by Odoo S.A.
Built so that a bad day stays a small one
Production is backed up before every change and rolled back when an update fails. Every environment is walled off from the others, and every server you link is audited.
- A private network per environment: Production, staging, each branch and each pull request preview on networks of their own; a database role, files and key per stage.
- Locked-down containers: Linux capabilities dropped, no privilege escalation, process limits on every build.
- Encrypted offsite backups: Encrypted before they leave the server, tested by a real restore every week.
- Your server, audited daily: A read-only audit grades each server and Odoo from A to F, and our agent only installs updates we signed.
- Two-factor and scoped tokens: Authenticator codes at sign-in, and API tokens limited to the scopes and projects you pick.
- Audit logs and recorded shells: Deploys, restores, settings changes and shell commands, with who and when; server terminal sessions are recorded.
Clear prices, no feature tiers
Every feature is included. On our cloud you choose the capacity; on your own server you pay per server.
On our cloud
$72 per worker per month. Plus storage and staging environments as you need them. Up to 20% less billed yearly. Configure your plan
On your own server
$5 per server per month. Server Pro, or $2 a month billed yearly. Installing a new Odoo is $150 once. See server pricing
Good to know before you start
What is Knova Cloud?
Knova Cloud is managed Odoo hosting in two ways: fully hosted on our cloud, where every branch of your GitHub repository runs as its own Odoo with development, staging and production, or on your own server, which we monitor, back up, secure and can install Odoo on. Daily tested backups, monitoring and custom domains with HTTPS come with both.
What is a good alternative to Odoo.sh?
If you want the Odoo.sh workflow without depending on Odoo S.A.'s own hosting, Knova Cloud gives you the same GitHub branch-per-environment model (development, staging on a copy of production, production) for Odoo Community and Enterprise 14 to 20. You can run it on our cloud or on a server you own, with daily restore-tested backups, monitoring and a web shell either way.
Can I keep Odoo on my own VPS and still get managed backups?
Yes. Link the server with one command: Server Pro ($5 a month, or $24 a year) adds monitoring and alerts, daily backups with offsite copies and weekly restore tests, a security audit with guided fixes, live logs and a recorded web terminal. Your Odoo keeps running on your machine: nothing is migrated.
Is the Odoo Enterprise licence included?
No. Odoo Community is free and needs no licence; for Enterprise, you subscribe with Odoo S.A. and enter your subscription code inside Odoo once production is live. The Enterprise apps themselves are provided by Knova Cloud, and you never share your subscription code with us.
Can I move from Odoo.sh or another host?
Yes. Connect the same GitHub repository, then import your database into a staging or production branch: a backup zip from Odoo.sh or Odoo's database manager, or a PostgreSQL dump. Large uploads are sent in resumable chunks, and the database has to be on the same Odoo version as the project.
How is my data backed up?
Production is backed up every day, and 7 daily, 4 weekly and 3 monthly backups are kept: about three months of history. The newest backup is restored as a test every week, and when offsite storage is configured, every backup is encrypted and copied to a second location. You can download any backup as a standard Odoo backup.
Run Odoo the way you want
Configure a hosted plan in a minute, link the server you already have, or tell us about your project and we'll suggest where to start.