Administer

Self-hosting

Run Triggerflow on your own server with Docker and PostgreSQL.

Triggerflow runs on your own server with Docker and PostgreSQL, so your data never leaves your infrastructure.

Quick start with Docker Compose

1. Copy the example settings: cp .env.example .env
2. Set at least POSTGRES_PASSWORD, CREDENTIALS_KEYS (the encryption key for credentials) and PUBLIC_URL (the address people use, starting with https://).
3. Start it: docker compose up -d --build
4. Open your address and create the first account; it becomes the owner and platform admin.

Compose runs the API, a background worker and PostgreSQL. Data is kept in Docker volumes.

Before customers use it

Open Admin → Launch checklist. It checks your settings against the server and tells you what to fix: HTTPS and secure cookies, email (SMTP) for invitations and password resets, off-site and encrypted backups, two-factor for admins, monitoring and more. The same problems are logged when the server starts.

Backups

Triggerflow makes its own backups on a schedule, optionally encrypted and copied to S3-compatible storage. Try restoring one into a scratch database once.

Upgrading

Pull the new version and run docker compose up -d --build. Database changes are applied automatically when the server starts.

More

The repository's docs/deployment.md covers every setting, scaling to several processes, server logs, data regions and search engines.