Choose the right deployment topology

Decide where Odoo, Runtime and SocketD live before assigning hostnames.

Odoo 19.0 & 18.0 supported

The three connections

Odoo ──HTTPS──> Runtime API
Runtime/SocketD ──HTTPS──> Odoo /socketd/*
Desktop client ──TLS──> SocketD

These addresses are not interchangeable:

Setting	Who uses it	Example
Runtime API URL	Odoo and desktop HTTP API	`https://print.example.com/runtime`
SocketD to Odoo URL	SocketD callbacks	`https://odoo.example.com`
SocketD Public URL	Desktop persistent connection	`tls://print.example.com:9019`

Supported choices

Public production

Run the protected Linux x86-64 container beside a package-installed or Docker Compose Odoo server. Publish Runtime and SocketD through trusted TLS.

Trusted LAN / test

Windows, macOS and x86-64 Deepin may run the same container as a Docker sidecar while Odoo remains installed natively.

Odoo.sh

Runtime + SocketD must run on a separate customer-managed host. Never start them inside an Odoo.sh shell.

Read the Odoo.sh guide

Port choice

The standard public profile uses HTTPS on TCP 443 for Runtime and native TLS on TCP 9019 for SocketD. Confirm that every desktop network permits 9019. The trusted-LAN profile uses plaintext HTTP 8020 and TCP 9019 and must never be exposed to the Internet.

Topology selected?Next: install the Odoo module →