A Linux Ubuntu Virtual Machine deployed with SSH access.
An A record set up to connect a custom domain to your instance. Formbricks will automatically create an SSL certificate for your domain using Let's Encrypt.

Single Command Setup

Copy and paste the following command into your terminal:

/bin/sh -c "$(curl -fsSL https://raw.githubusercontent.com/formbricks/formbricks/stable/docker/formbricks.sh)"

The script will prompt you for the following information:

Overwriting Docker GPG Keys: If Docker GPG keys already exist, the script will ask if you want to overwrite them.
Email Address: Provide your email address for SSL certificate registration with Let's Encrypt.
Domain Name: Enter the domain name that Traefik will use to create the SSL certificate and forward requests to Formbricks.

That's it! After running the command and providing the required information, visit the domain name you entered, and you should see the Formbricks home wizard!

Formbricks Hub and Cube

The stack includes the Formbricks Hub API (ghcr.io/formbricks/hub) and can also run a bundled Cube.js service for XM Suite v5 analytics. Hub and Cube share the same database as Formbricks by default, and Cube is enabled through the optional Docker Compose xm profile.

Migrations: A hub-migrate service runs Hub's database migrations (goose + river) before the Hub API starts. It runs on every docker compose up and is idempotent.
Production (docker/docker-compose.yml): Set HUB_API_KEY (required). HUB_API_URL defaults to http://hub:8080 so the Formbricks app can reach Hub inside the compose network. To enable XM Suite v5 analytics, set COMPOSE_PROFILES=xm and CUBEJS_API_SECRET; CUBEJS_API_URL defaults to http://cube:4000. Cube JWT issuer/audience default to formbricks-web and formbricks-cube, and the bundled Cube service exposes only meta,data API scopes. Override HUB_DATABASE_URL and CUBEJS_DB_* only if Hub or Cube should use a separate database. The Hub image tracks :latest by default so formbricks.sh update advances Hub in lockstep with the app. hub and hub-migrate always resolve to the same image. To pin to an immutable reference, set HUB_IMAGE_REF in docker/.env to either a tag (e.g. :0.2.0) or a digest (e.g. @sha256:14db7b3d...).
Development (docker-compose.dev.yml): Hub uses the same local Postgres database and HUB_API_KEY defaults to dev-api-key. Cube is behind the xm profile, CUBEJS_API_URL defaults to http://localhost:4000, and pnpm dev:setup generates CUBEJS_API_SECRET in the repo root .env. The Hub image is pinned to a semver tag (hub and hub-migrate share the same value); override HUB_IMAGE_TAG in the repo root .env to test a specific Hub release.

In development, Hub is exposed locally on port 8080. When the xm profile is enabled, Cube is exposed on 4000 (with the Cube playground on 4001). In production Docker Compose, Hub stays internal to the compose network at http://hub:8080; Cube also stays internal at http://cube:4000 when enabled.