The Odoo.sh workflow, on independent hosting

If you have used Odoo.sh, you already know how Knova Cloud works: branches pushed from GitHub, staging on a neutralized copy of production, a shell and daily backups. What changes is who runs it, that Community projects are welcome too, and that it can run on a server you own.

  • Same branch-per-environment workflow
  • Community and Enterprise
  • Import your Odoo.sh backup

Same workflow. Independent infrastructure.

A factual comparison, based on Odoo's public documentation at the time of writing.

CapabilityOdoo.shSelf-managed serverKnova Cloud
Every branch is an environment, pushed from GitHubYesNoYes
A preview for every pull request, forks includedYesNoYes
Development, staging and production stagesYesNoYes
Staging on a neutralized copy of productionYesNoYes
Web shell, SSH, online editor, logsYesSSH onlyYes
Community (OCA) modules added in a few clicksYesDo it yourselfYes
Daily backups, custom domains with HTTPS, mail catcherYesDo it yourselfYes
Odoo EnterpriseYesYesYes
Odoo CommunityEnterprise onlyYesYes
Runs on a server you ownNoYesYes
Operated byOdoo S.A.YouKnova 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.

The prices, side by side

Our hosted plans use the same units as Odoo.sh: workers, storage and staging environments. Here they are next to Odoo.sh's published prices.

Per monthOdoo.shKnova CloudDifference
Worker$72$72Same
Storage, per GB$0.25$0.25Same
Staging environment$18$18Same
Odoo Enterprise subscriptionRequiredOnly for Enterprise
Odoo CommunityNot availableIncluded

Per unit, our hosted prices are the same as Odoo.sh's published prices: $72 per worker, $0.25 per GB of storage and $18 per staging environment a month (Odoo.sh prices from odoo.sh/pricing, checked 5 October 2026).

Odoo.sh prices as published on https://www.odoo.sh/pricing, checked 5 October 2026, before taxes. Odoo.sh is a trademark of Odoo S.A.

Price your own plan with the Odoo.sh pricing calculator

Your habits carry over

The stages, the tools and the commands your team uses every day work the same way.

  • Three stages

    Development builds with demo data and tests, staging on a copy of production, and production that keeps its database.

  • The same shell

    odoo-update, odoosh-restart, the repository at ~/src/user, and SSH into a build with your GitHub keys.

  • Online editor

    Edit, commit and push from the browser, with Odoo's sources read-only alongside your code.

  • Logs per phase

    Build, install, update, pip and server logs for every build, streamed live.

  • Mail catcher

    Emails from development and staging are caught and shown in the Mails tab, never sent.

  • Upgrades on staging first

    Test a major version upgrade on a copy of production before production is touched.

A few things we do differently

Choices made for teams who want more control over their hosting.

  • Community projects welcome

    Host Odoo Community or Enterprise on any version from 14 to 20, at the same hosting price.

  • Your own server, if you prefer

    Keep Odoo on a server you own and get the monitoring, backups and security audit anyway.

  • Restore-tested backups

    Every week the newest production backup is restored into a temporary database and checked.

  • Encrypted offsite copies

    Backups are encrypted on the server before they are copied to a second location.

Moving from Odoo.sh in four steps

Your code stays in GitHub, and an Odoo backup restores on any Odoo of the same version.

  1. Create the project

    Link the same GitHub repository, on the same Odoo version, with Enterprise ticked if you use it.

  2. Download a backup

    From your production branch's Backups tab on Odoo.sh, with the filestore.

  3. Rehearse, then import

    Import it into a staging branch to test, then into production. Large uploads resume if interrupted.

  4. Switch the domain

    Point your DNS record at the project, and register your Enterprise code inside Odoo.

Questions from Odoo.sh users

How does Knova Cloud compare to Odoo.sh?

Knova Cloud follows the Odoo.sh workflow: branches pushed from GitHub become environments, releases move from development to staging (a neutralized copy of production) to production, and you get a web shell, SSH, an online editor and daily backups. The differences are that Knova Cloud is operated independently of Odoo S.A., hosts Odoo Community projects too, and can also run and manage Odoo on a server you own. Knova Cloud is not affiliated with or endorsed by Odoo S.A.

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.

Odoo.sh or self-hosting: which should I choose?

Odoo.sh is simplest if you use Odoo Enterprise and are happy on Odoo S.A.'s infrastructure; a plain self-hosted server costs less but leaves installation, backups, security updates and monitoring to you. Knova Cloud sits in between: your Odoo on our cloud or on your own server, with the installing, daily tested backups, monitoring and security audit done for you.

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.

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.

Will my Odoo.sh commands and paths work?

The shell has the commands Odoo.sh users rely on, such as odoo-update and odoosh-restart, and your repository is at ~/src/user. Scripts that hard-code other Odoo.sh paths are worth checking before you move.

Does my repository need a special layout?

No. Put your modules at the root of the repository or in folders; submodules are supported, including private ones with a deploy key. Python requirements in requirements.txt are installed on each build.

Does Odoo.sh host Odoo Community?

No. Odoo.sh only runs Odoo Enterprise databases. Knova Cloud runs the same GitHub branch workflow (development, staging on a neutralized copy of production, and production) for both Community and Enterprise, on versions 14 to 20, on our cloud or on your own server.

How much does Odoo.sh cost compared with Knova Cloud?

Odoo.sh charges $72 per worker, $0.25 per GB and $18 per staging environment a month, and requires an Odoo Enterprise subscription on top. Per unit, our hosted prices are the same as Odoo.sh's published prices: $72 per worker, $0.25 per GB of storage and $18 per staging environment a month (Odoo.sh prices from odoo.sh/pricing, checked 5 October 2026). Knova Cloud also hosts Community with no licence, and manages your own server for $5 a month.

How do I move from Odoo.sh without downtime surprises?

Download a backup from Odoo.sh, connect the same GitHub repository, import the backup into a staging branch first to rehearse, then into production, and move the domain last. The Enterprise subscription code is entered inside Odoo; it is never shared with the host.

Guides for the move

Everything you need to plan the switch.

  • How to migrate from Odoo.sh to Knova Cloud

    · 8 min read · Odoo.sh, Migration, Enterprise

    A step-by-step move from Odoo.sh: download a backup, connect the same GitHub repository, rehearse the import on staging, import production, move your custom domain and register the Enterprise code.

  • Odoo.sh pricing explained: workers, storage, staging and the licence

    · 5 min read · Odoo.sh, Pricing, Odoo hosting

    How Odoo.sh pricing works in 2026: the price per worker, per GB and per staging environment, yearly billing, the Enterprise licence on top, and an example.

  • Odoo.sh alternatives: hosting Odoo with the same GitHub workflow

    · 7 min read · Odoo.sh, Odoo hosting, Comparison

    The realistic ways to host Odoo when you want branches, staging copies of production and push-to-deploy, how they compare with Odoo.sh, and the questions to ask before you choose.

Bring your repository, keep your workflow

Tell us your Odoo version, the size of your database and your number of users, and we'll help you plan the move.

Plan a move · See pricing