Skip to main content
Version: 2.17.0

Deploying ToolJet using Docker Compose

Follow the steps below to deploy ToolJet on a server using Docker Compose. ToolJet requires a PostgreSQL database to store applications definitions, (encrypted) credentials for datasources and user authentication data.


If you rather want to try out ToolJet on your local machine with Docker, you can follow the steps here.

If you have any questions feel free to join our Slack Community or send us an email at [email protected].

Installing Docker and Docker Compose

Install docker and docker-compose on the server.

Deployment options

There are two options to deploy ToolJet using Docker Compose:

  1. With in-built PostgreSQL database (recommended). This setup uses the official Docker image of PostgreSQL.
  2. With external PostgreSQL database. This setup is recommended if you want to use a managed PostgreSQL service such as AWS RDS or Google Cloud SQL.

Confused about which setup to select? Feel free to ask the community via Slack:

  1. Download our production docker-compose file into the server.

    curl -LO
    mv docker-compose-db.yaml docker-compose.yaml
    mkdir postgres_data
  2. Create .env file in the current directory (where the docker-compose.yaml file is downloaded as in step 1):

    curl -LO
    curl -LO && chmod +x
    mv .env.internal.example .env && ./
  3. To start the docker container, use the following command:

    docker-compose up -d
  4. (Optional) TOOLJET_HOST environment variable can either be the public ipv4 address of your server or a custom domain that you want to use. Which can be modified in the .env file.

    Also, for setting up additional environment variables in the .env file, please check our documentation on environment variable


    If you've set a custom domain for TOOLJET_HOST, add a A record entry in your DNS settings to point to the IP address of the server.


    i. Please make sure that TOOLJET_HOST starts with either http:// or https://

    ii. Setup docker to run without root privileges by following the instructions written here

    iii. If you're running on a linux server, docker might need sudo permissions. In that case you can either run: sudo docker-compose up -d