Skip to content

Documentation / Running Odoo

Creating a Service

Deploy a new Odoo instance step by step.

Creating a new Odoo service in calmo.cloud deploys a fully configured Odoo instance on your server, ready to use.

Prerequisites #

Before creating a service, make sure you have:

  • At least one server added with Docker installed
  • The server's database (Postgres) and proxy (Traefik) enabled on its configuration page — only servers that are ready for Odoo appear in the server list

Creating a new service #

1. Navigate to Odoos #

In the sidebar, open Projects → Odoos and click the New Odoo button.

2. Fill in the details #

Configure your new service:

  • Name — A descriptive name (e.g., "Acme Corp ERP", "Staging Environment")
  • Version — Select 18.0, 19.0 or 20.0
  • Python version — The Python version Odoo runs on. New Odoos use 3.12; the other versions on offer are the ones your Odoo version is built on and has images for, and you can change it later. See Choosing the Python version
  • Server — Choose which server to host this service on
  • Type — Select the appropriate type:
    • Test — For development and testing
    • Live — For production use
    • Demo — For demonstrations
  • Admin Password — Set the master admin password for the Odoo instance

Once your team has early access to it, the Coding agent section of a test or demo Odoo lets a coding agent set the new Odoo up as soon as it is deployed: install apps, configure settings and enter data such as your company details or users. See Coding agents.

3. Create the service #

Click Create. calmo.cloud will:

  1. Create a dedicated database for this service
  2. Generate the Docker container configuration
  3. Build and start the Odoo container
  4. Set up reverse proxy routing

You can watch the progress in the Actions tab.

4. Access your service #

Once the status shows Running (green), your Odoo instance is ready. It is immediately accessible via its platform domain (e.g., erp.production.acme.calmo.cloud). Use this URL and your admin credentials to log in.

After creating a service #

Once your service is running, you'll typically want to: