Setup ToolJet

Check out the different methods you can use to deploy ToolJet on your machine

📄️ Try ToolJet

On local with Docker

📄️ DigitalOcean

Now you can quickly deploy ToolJet using the Deploy to DigitalOcean button.

📄️ Docker

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.

📄️ Heroku

Follow the steps below to deploy ToolJet on Heroku:

📄️ AWS EC2

You should setup a PostgreSQL database manually to be used by the ToolJet server.

📄️ AWS ECS

You should setup a PostgreSQL database manually to be used by ToolJet.

📄️ Kubernetes

You should setup a PostgreSQL database manually to be used by ToolJet.

📄️ Kubernetes (GKE)

You should setup a PostgreSQL database manually to be used by ToolJet. We recommend using Cloud SQL since this guide is for deploying using GKE.

📄️ Kubernetes (AKS)

You should setup a PostgreSQL database manually to be used by ToolJet. We recommend using Azure Database for PostgreSQL since this guide is for deploying using AKS.

📄️ Google Cloud Run

You should setup a PostgreSQL database manually to be used by ToolJet.

📄️ Deploying ToolJet client

ToolJet client is a standalone application and can be deployed on static website hosting services such as Netlify, Firebase, S3/Cloudfront, etc.

📄️ Environment variables

Both the ToolJet server and client requires some environment variables to start running.

📄️ Connecting via HTTP proxy

Connecting via HTTP proxy

📄️ Deploying ToolJet on a subpath

ToolJet can now be deployed at a subpath rather than the root (/) of a public domain. Example subpath installation URL//www.yourcompany.com/apps/tooljet

If you have any questions feel free to join our Slack community or send us an email at hello@tooljet.com.