Self-host Domoticz with Levelrail

A home automation system with a web UI that links sensors, switches and many device protocols.

  • Authordomoticz
  • LicenceGPL-3.0-only
  • Memory256 MiB
  • Services1

How to self-host Domoticz

  1. Pull the images

    One image is pulled on your server.

    Show images
    • domoticz/domoticz:2026.4@sha256:ece392300d055395cac0b4edea4451b31f765ff5339e5597ca77371be8d7e93a
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.

  3. Fill in the secrets

    1 setting is preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Open the address, then set a login under Setup and Settings and add your hardware.

Domoticz requirements

Memory
About 256 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8080
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0-only, copyleft license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Domoticz. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Domoticz docs page.

Deploy Domoticz your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Domoticz from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain domoticz=app.example.com.

levelrail-cli templates install domoticz --name my-domoticz

Deploy Domoticz with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/domoticz/install \
  -d '{
    "name": "my-domoticz"
  }'

Domoticz configuration

Domoticz services

ServiceImagePortsVolumes
domoticz domoticz/domoticz:2026.4@sha256:ece392300d055395cac0b4edea4451b31f765ff5339e5597ca77371be8d7e93a 8080 userdata -> /opt/domoticz/userdata

Domoticz environment variables

VariableServiceValue
TZ domoticz Preset by the template

Ports and volumes

Ports
8080
Volumes
1 named mount: userdata -> /opt/domoticz/userdata

Domoticz FAQ

How much memory does Domoticz need?

The catalog lists about 256 MiB of memory for Domoticz.

Does Domoticz run on arm64?

For Domoticz, arm64 support is not confirmed; amd64 is unknown.

What licence is Domoticz under?

Domoticz is licensed under GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.

Does Domoticz need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Domoticz use?

Domoticz listens on port 8080 inside the stack.

Where does Domoticz keep its data?

In a named volume: userdata mounted at /opt/domoticz/userdata.

Can I deploy Domoticz on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Domoticz, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image domoticz/domoticz:2026.4@sha256:ece392300d055395cac0b4edea4451b31f765ff5339e5597ca77371be8d7e93a is what you deploy there.

levelrail-cli templates install domoticz --name my-domoticz