ToolJet with Docker Compose

What ToolJet needs

Only figures ToolJet's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.

On top of this, Caddy (the reverse proxy in the file) is a single small container. ToolJet itself runs as 2 containers: tooljet, tooljet-postgres.

Which hardware ToolJet has images for

Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.

• x86-64 PC or NAS (linux/amd64): every image has a build.
• Raspberry Pi 4/5, 64-bit OS (linux/arm64): no image for tooljet. No image for this hardware; the builder leaves the app out.
• Raspberry Pi 3 or Zero 2 W, 32-bit OS (linux/arm/v7): no image for tooljet. No image for this hardware; the builder leaves the app out.

A manifest says an image exists for a CPU, not how well ToolJet runs on it: a build for arm64 or arm/v7 can still be too slow or need more memory than the board has. The RAM and disk ToolJet publishes are in the table above and, for a whole set of apps against a Raspberry Pi, on Will it run on my machine?. A tag like latest can move to a new digest after the date checked.

docker-compose.yml

This is exactly what the builder writes for ToolJet alone on example.org: the official definition with its published ports removed and Caddy added in front. Every ${VARIABLE} is defined in the .env below.

# docker-compose.yml built at dankhost.com for: ToolJet
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- ToolJet (tooljet.example.org) ----
  # Source: https://docs.tooljet.ai/docs/setup/docker/ (checked 2026-10-01)
  # Source: https://tooljet-deployments.s3.us-west-1.amazonaws.com/docker/docker-compose-db.yaml (checked 2026-10-01)
  # Source: https://tooljet-deployments.s3.us-west-1.amazonaws.com/docker/.env.internal.example (checked 2026-10-01)
  # Source: https://tooljet-deployments.s3.us-west-1.amazonaws.com/docker/internal.sh (checked 2026-10-01)
  # Source: https://docs.tooljet.ai/docs/setup/system-requirements/ (checked 2026-10-01)
  # Changed: Removed the documented '80:80' port; Caddy reaches tooljet:80 on the proxy network. The two container_name lines and the unused certs, logs and fallbackcerts volumes are dropped (the builder names every container).
  #          env_file: .env is replaced by the non-empty lines of the docs' .env.internal.example, written under environment. TOOLJET_HOST is https://tooljet.example.org: the docs say it can be "a custom domain that you want to use" and must start with http:// or https:// (here it is https).
  #          LOCKBOX_MASTER_KEY, SECRET_KEY_BASE and PGRST_JWT_SECRET are generated in .env at the lengths internal.sh makes them (openssl rand -hex 32, -hex 64 and -hex 32). One generated database password serves PG_PASS, TOOLJET_DB_PASS and PGRST_DB_URI, as internal.sh does.
  #          PG_HOST, TOOLJET_DB_HOST and the host in PGRST_DB_URI are postgres, the database service's name. The documented file names the database container ${PG_HOST} (postgresql in the example .env); the builder gives every container its own prefixed name instead.
  #          The database data stays in the folder ./postgres_data next to this file, as with the documented named volume (driver_opts o: bind, device ${PWD}/postgres_data), written here as a plain bind. The postgres service gets its two variables instead of the whole .env.
  tooljet:
    tty: true
    stdin_open: true
    image: "tooljet/tooljet:ee-lts-latest"
    container_name: "tooljet"
    platform: "linux/amd64"
    restart: "always"
    depends_on:
      - "tooljet-postgres"
    environment:
      SERVE_CLIENT: "true"
      PORT: "80"
      TOOLJET_HOST: "https://tooljet.example.org"
      LOCKBOX_MASTER_KEY: "${TOOLJET_LOCKBOX_MASTER_KEY}"
      SECRET_KEY_BASE: "${TOOLJET_SECRET_KEY_BASE}"
      ORM_LOGGING: "all"
      PG_DB: "tooljet_production"
      PG_USER: "postgres"
      PG_HOST: "postgres"
      PG_PASS: "${TOOLJET_PG_PASS}"
      TOOLJET_DB: "tooljet_db"
      TOOLJET_DB_USER: "postgres"
      TOOLJET_DB_HOST: "postgres"
      TOOLJET_DB_PASS: "${TOOLJET_PG_PASS}"
      PGRST_DB_URI: "postgres://postgres:${TOOLJET_PG_PASS}@postgres/tooljet_db"
      PGRST_HOST: "localhost:3002"
      PGRST_JWT_SECRET: "${TOOLJET_PGRST_JWT_SECRET}"
      PGRST_SERVER_PORT: "3002"
      PGRST_DB_PRE_CONFIG: "postgrest.pre_config"
      CHECK_FOR_UPDATES: "true"
      DEFAULT_FROM_EMAIL: "hello@tooljet.io"
      ENABLE_MULTIPLAYER_EDITING: "true"
      ENABLE_MARKETPLACE_FEATURE: "true"
      USER_SESSION_EXPIRY: "2880"
      DEPLOYMENT_PLATFORM: "docker"
    command: "npm run start:prod"
    networks:
      proxy: {}
      tooljet-backend: {}
  tooljet-postgres:
    image: "postgres:16"
    container_name: "tooljet-postgres"
    restart: "always"
    volumes:
      - "./tooljet/postgres_data:/var/lib/postgresql/data"
    environment:
      POSTGRES_USER: "postgres"
      POSTGRES_PASSWORD: "${TOOLJET_PG_PASS}"
    networks:
      tooljet-backend:
        aliases:
          - "postgres"

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"
  tooljet-backend:
    internal: true

volumes:
  caddy-data:
  caddy-config:

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for tooljet.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.

# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.

# ToolJet
tooljet.example.org {
	reverse_proxy tooljet:80
}

Already running nginx, Nginx Proxy Manager, Caddy or Traefik? The reverse-proxy settings ToolJet needs, for all four, each cited to ToolJet's own docs.

.env

The secrets are left blank here on purpose: a password printed on a public page is the same for everyone who copies it. The builder fills them with random letters and digits made in your browser.

# .env for ToolJet, from dankhost.com/app/tooljet/. Fill the blank secrets before starting.
# Keep this file private (chmod 600).

# ToolJet
# 64 random letters and digits: the builder fills this in your browser
TOOLJET_LOCKBOX_MASTER_KEY=
# 128 random letters and digits: the builder fills this in your browser
TOOLJET_SECRET_KEY_BASE=
# 64 random letters and digits: the builder fills this in your browser
TOOLJET_PGRST_JWT_SECRET=
# 32 random letters and digits: the builder fills this in your browser
TOOLJET_PG_PASS=

Changes from the official file

Besides prefixing every service, container, volume, folder and variable with tooljet (so any set of apps can share one file), these are all the differences from what the project documents:

• Removed the documented '80:80' port; Caddy reaches tooljet:80 on the proxy network. The two container_name lines and the unused certs, logs and fallbackcerts volumes are dropped (the builder names every container).
• env_file: .env is replaced by the non-empty lines of the docs' .env.internal.example, written under environment. TOOLJET_HOST is https://tooljet.example.org: the docs say it can be "a custom domain that you want to use" and must start with http:// or https:// (here it is https).
• LOCKBOX_MASTER_KEY, SECRET_KEY_BASE and PGRST_JWT_SECRET are generated in .env at the lengths internal.sh makes them (openssl rand -hex 32, -hex 64 and -hex 32). One generated database password serves PG_PASS, TOOLJET_DB_PASS and PGRST_DB_URI, as internal.sh does.
• PG_HOST, TOOLJET_DB_HOST and the host in PGRST_DB_URI are postgres, the database service's name. The documented file names the database container ${PG_HOST} (postgresql in the example .env); the builder gives every container its own prefixed name instead.
• The database data stays in the folder ./postgres_data next to this file, as with the documented named volume (driver_opts o: bind, device ${PWD}/postgres_data), written here as a plain bind. The postgres service gets its two variables instead of the whole .env.

Notes for ToolJet behind the proxy

• Open https://tooljet.example.org and set up the first account on the page that appears on the first visit.
• The image is amd64 only: the documented file sets platform: linux/amd64, and the system requirements say "arm64 is not supported". Plan 4 GB of RAM for ToolJet alone.
• tooljet/tooljet:ee-lts-latest is the tag the docs name as the official image. The upgrade guide asks for an exact LTS tag (v3.x.x-lts) from Docker Hub instead; with ee-lts-latest a pull moves to the newest LTS release.
• Telemetry is on by default, the example .env says; add DISABLE_TOOLJET_TELEMETRY: "true" under tooljet's environment to turn it off. CHECK_FOR_UPDATES makes it look for a new version every 24 hours.
• To use ToolJet's AI features, the Docker page says to allow outgoing traffic to api-gateway.tooljet.ai and python-server.tooljet.ai.

Back it up

ToolJet publishes backup-restore.sh for the in-built PostgreSQL: pg_dumpall of the whole database server into one .sql file, and psql to load it back. That covers both databases the upgrade guide asks you to back up, PG_DB (apps, users, configuration) and TOOLJET_DB (ToolJet Database tables).

Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, the dump command the project documents, rewritten for this file's service names, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.

# BACKUP.md built at dankhost.com for: ToolJet

What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.

The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.

Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.

## Before you start

    BACKUP=/mnt/backup/selfhost   # change this: a disk or machine other than this server's system disk
    mkdir -p "$BACKUP"

## Every time: the three stack files

    tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy

.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.

## Caddy (the reverse proxy)

Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.

- caddy-data (named volume, /data in caddy)
  BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
  SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
  IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.

Copy (Caddy keeps serving while you copy):

    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data

Restore check:

    tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"

Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)

## ToolJet

ToolJet publishes backup-restore.sh for the in-built PostgreSQL: pg_dumpall of the whole database server into one .sql file, and psql to load it back. That covers both databases the upgrade guide asks you to back up, PG_DB (apps, users, configuration) and TOOLJET_DB (ToolJet Database tables).

What this compose mounts:
- ./tooljet/postgres_data (/var/lib/postgresql/data in tooljet-postgres)
  COVERED BY THE COMMAND BELOW: PostgreSQL data files of both databases; copy them only with the database stopped.

1. Database dump for tooljet-postgres:

    docker compose exec -T --user postgres tooljet-postgres pg_dumpall -c -U postgres > "$BACKUP/tooljet.sql"

   The script's docker exec -t --user postgres "$PG_HOST" pg_dumpall -c -U postgres, with docker compose, -T instead of -t (no terminal on a redirect) and this file's service name.

2. Nothing else to copy: the command above holds all of ToolJet's data. pg_dumpall is consistent per database while ToolJet runs: each database is dumped as a snapshot of the moment its dump started (PostgreSQL docs).

Restore check:

    grep -c 'PostgreSQL database cluster dump complete' "$BACKUP/tooljet.sql"   # 1 means pg_dumpall finished

The script pipes the file into psql; -c in the dump drops each database before it is recreated.

    docker compose up -d tooljet-postgres
    docker compose exec -T --user postgres tooljet-postgres psql -U postgres < "$BACKUP/tooljet.sql"
    docker compose up -d

Sources:
- ToolJet docs: Deploying ToolJet using Docker Compose (in-built PostgreSQL, .env, backup, upgrading to the latest LTS): https://docs.tooljet.ai/docs/setup/docker/ (checked 2026-10-01)
- ToolJet: backup-restore.sh (pg_dumpall and psql): https://tooljet-deployments.s3.us-west-1.amazonaws.com/docker/backup-restore.sh (checked 2026-10-01)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-10-01)

Update it

What docker compose pull does depends only on how each image line in the compose file above is tagged. For ToolJet as this page writes it:

What ToolJet's docs say about updating

ToolJet's upgrade guide: back up PostgreSQL with both databases, run docker compose down, set the tooljet image to the latest LTS tag from Docker Hub, and run docker compose up -d.

• The tag here is ee-lts-latest, so a pull already moves to the newest LTS release; the guide pins an exact tag instead.
• The guide: installations older than v2.23.0-ee2.10.2 must first upgrade to that version.

Source: ToolJet docs: Deploying ToolJet using Docker Compose (in-built PostgreSQL, .env, backup, upgrading to the latest LTS) checked 2026-10-01

The steps

1. Back up first, as in Back it up above. An update can migrate ToolJet's data on its first start and its database with it; the copy is the way back.
2. Download the new images. Running containers are not touched yet:

   docker compose pull

3. Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:

   docker compose up -d

4. Watch ToolJet start (Ctrl+C stops following the log, not the app):

   docker compose logs -f tooljet

5. Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:

   docker image prune

Docker's reference for these commands: Docker docs: docker compose pull checked 2026-09-30; Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30; Docker docs: docker image prune checked 2026-09-30

Sources

Every page below was fetched on the date shown.

• ToolJet on GitHub (repository description) checked 2026-10-01 (what it does)
• ToolJet docs: System Requirements (x86 only, 4 GB RAM, 1 vCPU, 8 GiB storage) checked 2026-10-01 (hardware requirements, compose definition and proxy settings)
• ToolJet docs: Deploying ToolJet using Docker Compose (in-built PostgreSQL, .env, backup, upgrading to the latest LTS) checked 2026-10-01 (compose definition and proxy settings, backup plan, update notes)
• ToolJet: the production docker-compose-db.yaml the Docker page downloads checked 2026-10-01 (compose definition and proxy settings)
• ToolJet: .env.internal.example, the .env the Docker page downloads for in-built PostgreSQL checked 2026-10-01 (compose definition and proxy settings)
• ToolJet: internal.sh, which fills in the keys and the database password checked 2026-10-01 (compose definition and proxy settings)
• Caddy docs: Keep Caddy running (Docker Compose section) checked 2026-09-23 (Caddy)
• Vaultwarden wiki: Caddy with HTTP challenge (uses the caddy:2 image) checked 2026-09-23 (Caddy)
• ToolJet: backup-restore.sh (pg_dumpall and psql) checked 2026-10-01 (backup plan)
• Docker docs: Volumes, Back up, restore, or migrate data volumes checked 2026-10-01 (backup plan)
• Caddy docs: Conventions, Data directory checked 2026-09-24 (backup plan)
• PostgreSQL docs: Upgrading a PostgreSQL Cluster checked 2026-09-30 (database upgrade)
• Docker docs: docker compose pull checked 2026-09-30 (update steps)
• Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30 (update steps)
• Docker docs: docker image prune checked 2026-09-30 (update steps)

Add ToolJet to the builder All seventy apps