Skip to content
Compare · Odoo hosting

calmo.cloud
or Odoo.sh?

Both run Odoo Enterprise in production, deploy from GitHub and give you staging. Odoo.sh does it on infrastructure Odoo operates. calmo.cloud does it on a server you rent yourself, with root access and plain Docker underneath.

calmo.cloud

A management layer for Odoo on your own Ubuntu server. It installs Docker, Traefik and PostgreSQL, deploys Odoo 18, 19 or 20 in containers, sends backups to storage you choose and gives every pull request a preview instance. The server stays yours.

Odoo.sh

Odoo's own platform as a service. It builds production, staging and development branches straight from GitHub, keeps daily backups and opens a shell on every branch. It needs an Odoo Enterprise subscription and runs only on Odoo's infrastructure.

At a glance.
Side by side.

The two platforms overlap more than most comparisons admit. The rows that matter are the ones about who holds the keys.

Where Odoo runs

calmo.cloud Your server

Any Ubuntu server you can reach over SSH: Hetzner, another cloud, or a machine in your own rack.

Odoo.sh Odoo's servers

Shared or dedicated hosting operated by Odoo. You pick workers and storage, not the machine or the provider.

Root access

calmo.cloud Yes

Full root over SSH. Read logs, inspect containers, install what you need.

Odoo.sh Shell only

SSH and a web shell into each branch container. System packages cannot be installed and the host is not yours.

Database access

calmo.cloud Direct

PostgreSQL on your server, one database per instance, reachable with any client.

Odoo.sh In the shell

psql inside the branch shell. The cluster itself is managed by Odoo.

Custom modules

calmo.cloud Yes

Deploy from a GitHub repository, or install modules from the dashboard without touching a terminal.

Odoo.sh Yes

Commit to a branch and Odoo.sh builds it. Python dependencies go in a requirements file.

Staging and previews

calmo.cloud Copies and PR previews

Copies of production on demand, plus a neutralized preview instance for every pull request that is removed when the PR closes.

Odoo.sh Branches

Staging branches with production data and development branches with demo data. Staging databases are deleted after a month unless rebuilt.

Backups

calmo.cloud Your storage

Scheduled to one or more S3-compatible buckets you own, each with its own frequency and retention. Restore into a copy before you touch production.

Odoo.sh Odoo's storage

Seven daily, four weekly and three monthly backups on Odoo's servers, downloadable from the Backups tab. Restoring a monthly backup goes through Odoo Support.

Edition and versions

calmo.cloud Enterprise, 18, 19 and 20

Odoo 18, 19 and 20 Enterprise today. Community edition is on the roadmap.

Odoo.sh Enterprise, 16 and up

Enterprise subscription required. Community edition does not run on Odoo.sh.

Monitoring

calmo.cloud Built in

Server, container, PostgreSQL and Traefik metrics every five minutes, uptime and certificate checks, security checks on every instance.

Odoo.sh Built in

Per-project graphs for CPU, response time and mail, plus build logs.

If you leave

calmo.cloud Everything keeps running

End the subscription and the containers, databases and backups stay where they are, on your server.

Odoo.sh Export

Download a dump from the production branch and import it on another host.

Underneath

calmo.cloud Docker Compose

Standard Compose files, Traefik and PostgreSQL. You can read and change every line.

Odoo.sh Odoo.sh runtime

Odoo's own build and hosting system. No access to the containers or the host.

Checked against odoo.sh and the Odoo documentation on 14 September 2026. Tell us if something changed.

Where they
part ways.

The server is yours.

calmo.cloud never owns your infrastructure. You rent the server, you hold root, and the platform connects over SSH to do its work. When something breaks at three in the morning, you can open a terminal instead of a ticket.

Backups land where you say.

Odoo.sh keeps your backups on Odoo's side and lets you download them by hand. calmo.cloud writes them to buckets you own, at several providers at once if you like, with a schedule and retention per destination.

Previews come from your real data.

Odoo.sh builds development branches with demo data. calmo.cloud clones your production instance, neutralizes it, deploys the pull request branch and posts the link to GitHub. Reviewers see the change on data they recognise.

In fairness

When Odoo.sh is the better fit

If you want one contract for licence, hosting and platform upgrades, Odoo.sh is the simpler arrangement, and Odoo runs the hardware so you never have to. It also hosts versions calmo.cloud does not yet support. Teams without anyone who wants to own a server are usually well served there.

What it costs.
Run your own numbers.

The Odoo licence is the same on both sides. Self-hosting Enterprise needs the Custom plan, and so does Odoo.sh. What differs is the hosting line: Odoo.sh meters workers, staging and storage, calmo.cloud is a flat plan from €29 a month that covers two servers, plus the server itself.

Odoo.sh prices read from Odoo's own calculator with the currency set to EUR: €48 per worker, €12 per staging environment and €0.16 per GB a month on annual billing; €60, €15 and €0.20 monthly. Dedicated hosting adds €400 a month (€500 monthly) and starts at four workers.

Moving over.
Four steps.

A move from Odoo.sh is mostly a database move. The addons already live in your Git repository.

  1. 01

    Rent a server

    Any Ubuntu machine you can reach over SSH. Connect it to calmo.cloud and it installs Docker, Traefik and PostgreSQL.

  2. 02

    Connect the repository

    Point calmo.cloud at the GitHub repository you already deploy from Odoo.sh. Addons are discovered per branch.

  3. 03

    Download and import the dump

    Take a backup from the production branch on Odoo.sh, upload it to calmo.cloud and restore it into a fresh instance. Test there first.

  4. 04

    Switch the domain

    Add your hostname, let the certificate issue, and move the DNS record. The Odoo.sh project can stay alive until you are sure.

Good questions

Asked before
switching.

Can I keep my Odoo.sh Git workflow?

Yes. Branches deploy the same way: connect the repository, choose a branch per instance and calmo.cloud deploys the addons in it. Pull requests get their own preview instance.

Do I need a new Odoo licence?

No. Your Enterprise Custom plan covers self-hosting. Move the subscription code to the new instance and it activates there.

Which Odoo versions can I move?

calmo.cloud runs Odoo 18, 19 and 20. If your Odoo.sh project is on 16 or 17, plan the version upgrade first or keep it on Odoo.sh until you upgrade.

What about Community edition?

Neither platform runs it today. Odoo.sh requires Enterprise by design. calmo.cloud is built on Enterprise images and Community support is planned.

Who looks after security updates on my server?

calmo.cloud keeps the Odoo images, Traefik and PostgreSQL containers current and runs security checks on every instance. The operating system is your server, so its updates are yours, and root access means you can automate them however you like.

Sources, checked 14 September 2026

Competitor details come from their public pages on the date above. Prices change; the links are there so you can check the current figures yourself.

A calmer cloud is coming

Your next chapter.
A little more sky.

Join the waitlist for early access and launch updates. Bring your Odoo. Keep your independence.

Join the waitlist Let's talk