AI features require a self-hosted Enterprise license.
- Docker
- Kubernetes
Enable bundled Qwen/vLLM for AI
The Docker stack can optionally run Qwen through vLLM as an OpenAI-compatible/v1 endpoint. Baseline
installs do not start vLLM and can still use Google Vertex, Azure, AWS Bedrock, or another OpenAI-compatible
endpoint.The bundled Qwen/vLLM service requires a GPU-capable Docker host with the NVIDIA Container Toolkit installed.
Model files are stored in the qwen-model-cache Docker volume. Startup can take several minutes while vLLM
downloads and loads the model.To use the bundled Qwen runtime, add these values to .env:http://vllm:8000/v1 and is bound to
127.0.0.1:8000 by default for local checks.If you run your own Qwen/vLLM service, do not enable the qwen profile. Set AI_PROVIDER, AI_MODEL, and
AI_OPENAI_COMPATIBLE_BASE_URL to your external endpoint instead.Enable AI taxonomy beta
The standalone AI taxonomy service is included as an opt-in Docker Compose profile. Baseline installs do not start taxonomy and do not require taxonomy or LLM secrets.To enable taxonomy with the bundled Qwen runtime, add these values to.env::v0.1.0 with the current released ghcr.io/formbricks/taxonomy image tag for your Formbricks
version. Production installs should pin a release tag instead of relying on :latest.If you run your own OpenAI-compatible endpoint, use COMPOSE_PROFILES=taxonomy instead and point
TAXONOMY_LLM_BASE_URL at that /v1 endpoint. The selected model must reliably return strict JSON because
taxonomy generation validates an exact 5-level tree.To use Amazon Bedrock instead of an OpenAI-compatible endpoint, replace the taxonomy LLM values with:.env. Compose reads COMPOSE_PROFILES from .env, so the same command works
for taxonomy and qwen,taxonomy setups:127.0.0.1:8000 refers to the taxonomy service itself.
The preflight endpoint then checks Hub internal auth and LLM reachability from taxonomy.The taxonomy service remains internal to the compose network by default. TAXONOMY_MAX_RECORDS defaults to
10000; change it only after sizing CPU, memory, and LLM capacity.The taxonomy service is internal to the Docker network. Formbricks Web still calls Hub with
HUB_API_KEY; Hub calls taxonomy with TAXONOMY_SERVICE_TOKEN; taxonomy calls Hub
internal APIs with HUB_INTERNAL_API_TOKEN.The one-click installer does not prompt for AI taxonomy settings. One-click users can enable the beta later
by editing
./formbricks/.env, adding the taxonomy variables above, ensuring COMPOSE_PROFILES=taxonomy is
set, and restarting with docker compose up -d.If you use the one-click Traefik setup, FeedbackRecords are available on the Formbricks origin at
/api/v3/feedbackRecords and /v1/feedback-records. Custom Docker reverse proxies need equivalent wiring:
run gateway auth against the Formbricks app, rewrite /api/v3/feedbackRecords to Hub’s
/v1/feedback-records, and inject Authorization: Bearer <HUB_API_KEY> only on the Hub-bound hop.