How to Self-Host Formbricks 2026

What Is Formbricks?

Formbricks is an open source experience management platform — part survey tool, part in-app feedback system, part user research platform. It lets you:

• Build multi-step forms and surveys (like Typeform)
• Trigger in-app micro-surveys based on user actions
• Create NPS surveys, CSAT forms, and feature interviews
• Run link surveys (shareable URLs)
• Analyze responses with built-in analytics

Typeform costs $50-$83/month for teams that need logic jumps, file uploads, and integrations. Formbricks is free when self-hosted — just server costs (~$10/month on Hetzner CX32).

Key differentiator: Formbricks has a "No-Code SDK" approach — you instrument your app once, then non-engineers can create and target surveys without deployments.

---

Prerequisites

• VPS with 2 vCPU, 2GB RAM minimum
• Docker + Docker Compose v2
• Domain name pointing to your server
• SMTP credentials (for invite emails)

---

Docker Compose Deployment

1. Create Project Directory

mkdir formbricks && cd formbricks

2. Create docker-compose.yaml

version: "3.3"

networks:
  formbricks:

volumes:
  uploads:
  database:

services:
  postgres:
    image: postgres:15-alpine
    volumes:
      - database:/var/lib/postgresql/data
    restart: always
    networks:
      - formbricks
    environment:
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRES_USER: formbricks
      POSTGRES_DB: formbricks

  formbricks:
    image: ghcr.io/formbricks/formbricks:latest
    depends_on:
      - postgres
    ports:
      - "3000:3000"
    volumes:
      - uploads:/home/nextjs/apps/web/uploads
    restart: always
    networks:
      - formbricks
    environment:
      # App URL
      WEBAPP_URL: ${WEBAPP_URL}
      # Security
      NEXTAUTH_SECRET: ${NEXTAUTH_SECRET}
      ENCRYPTION_KEY: ${ENCRYPTION_KEY}
      # Database
      DATABASE_URL: postgresql://formbricks:${POSTGRES_PASSWORD}@postgres:5432/formbricks
      # Email
      MAIL_FROM: ${MAIL_FROM}
      SMTP_HOST: ${SMTP_HOST}
      SMTP_PORT: ${SMTP_PORT}
      SMTP_USER: ${SMTP_USER}
      SMTP_PASSWORD: ${SMTP_PASSWORD}
      SMTP_SECURE_ENABLED: ${SMTP_SECURE_ENABLED}
      # Instance settings
      PRIVACY_URL: ${PRIVACY_URL:-}
      TERMS_URL: ${TERMS_URL:-}
      IMPRINT_URL: ${IMPRINT_URL:-}
      # Optional: disable new signups
      # DISABLE_REGISTRATION: "1"

3. Create .env

# .env

# App URL (no trailing slash)
WEBAPP_URL=https://forms.yourdomain.com

# Security keys — generate strong random values
NEXTAUTH_SECRET=$(openssl rand -hex 32)
ENCRYPTION_KEY=$(openssl rand -hex 32)

# Database
POSTGRES_PASSWORD=your-secure-db-password

# Email (SMTP)
MAIL_FROM=noreply@yourdomain.com
SMTP_HOST=smtp.yourdomain.com
SMTP_PORT=587
SMTP_USER=your-smtp-username
SMTP_PASSWORD=your-smtp-password
SMTP_SECURE_ENABLED=1

4. Start Formbricks

docker compose up -d

# Check startup
docker compose logs -f formbricks
# Look for: "Ready - started server on 0.0.0.0:3000"

---

Configure Caddy Reverse Proxy

# /etc/caddy/Caddyfile

forms.yourdomain.com {
    reverse_proxy localhost:3000

    # Allow large file uploads in forms
    request_body {
        max_size 50MB
    }
}

systemctl reload caddy

---

First Login and Setup

Visit https://forms.yourdomain.com:

1. Click "Create account"
2. Enter name, email, and password
3. Complete the onboarding (create your first environment)
4. You're now the admin of your instance

Formbricks Concepts

Organization (your company/team)
└── Products (your apps/websites)
    └── Environments (Production / Development)
        └── Surveys
            ├── Link Surveys (standalone URL)
            ├── In-App Surveys (triggered by user actions)
            └── Web Surveys (embedded in site)

---

Building Your First Survey

Link Survey (Like Typeform)

1. Go to Surveys → New Survey
2. Select "Link Survey"
3. Add questions:
   - Rating (NPS 0-10)
   - Open Text
   - Single Select
   - Multi Select
   - Matrix
   - File Upload
4. Configure logic: "If rating < 7, show follow-up"
5. Set thank you card
6. Publish → Copy link

In-App Survey (No Extra Deploy Needed)

Formbricks shines with in-app micro-surveys. Install the SDK once, then trigger surveys via the dashboard:

npm install @formbricks/js

// app/providers.tsx (Next.js)
"use client";

import { useEffect } from "react";
import formbricks from "@formbricks/js";

export function FormbricksProvider({ children, user }) {
  useEffect(() => {
    formbricks.setup({
      environmentId: "your-env-id",  // from Formbricks dashboard
      apiHost: "https://forms.yourdomain.com",
    });

    // Identify the user (for targeted surveys)
    if (user) {
      formbricks.setUserId(user.id);
      formbricks.setEmail(user.email);
      // Custom attributes for targeting
      formbricks.setAttribute("plan", user.plan);
      formbricks.setAttribute("createdAt", user.createdAt);
    }

    // Track actions to trigger surveys
    formbricks.track("Dashboard Visited");
  }, [user]);

  return children;
}

Then in the Formbricks dashboard, create a survey with trigger: "When user visits Dashboard 3 times" — no code change needed.

---

Integrations

Webhooks (Send to Any Service)

Survey Settings → Webhooks → Add Webhook

URL: https://hooks.yourdomain.com/formbricks
Events: Response Created, Response Finished

Payload format:
{
  "event": "responseCreated",
  "data": {
    "surveyId": "abc123",
    "response": {
      "finished": true,
      "data": {
        "question-1": "Very satisfied",
        "question-2": "The UI is intuitive"
      }
    }
  }
}

Slack Integration

Survey Settings → Integrations → Slack
→ Connect Slack workspace
→ Choose channel for response notifications

Google Sheets

Survey Settings → Integrations → Google Sheets
→ Authenticate with Google
→ Map survey fields to columns
→ New responses auto-append rows

---

Segment Your Audience for Targeted Surveys

Formbricks lets you target surveys based on user attributes:

Show survey to users where:
- plan = "free"
- AND account age >= 7 days
- AND has_used_feature_X = false

Display: when user opens "Upgrade" modal

This is what replaces tools like Sprig, Qualtrics, or Typeform's conditional logic — but at the SDK level, not form logic level.

---

Email Follow-Up After Survey

Survey Settings → Actions → Send Email on Completion

When: Survey finished
Send to: {respondent_email}  (if you collected email)
Subject: Thanks for your feedback, {first_name}!
Body: (rich text with dynamic variables)

---

Disable Public Registration

After setting up your team:

# docker-compose.yaml — formbricks service environment
DISABLE_REGISTRATION: "1"

docker compose up -d

New users can only be invited by existing members.

---

Backup and Restore

#!/bin/bash
# backup-formbricks.sh
DATE=$(date +%Y%m%d_%H%M%S)
BACKUP_DIR="/backups/formbricks"

mkdir -p $BACKUP_DIR

# Database
docker compose exec -T postgres pg_dump \
  -U formbricks formbricks | gzip > $BACKUP_DIR/db_$DATE.sql.gz

# Uploaded files (if using local storage)
UPLOADS_PATH=$(docker volume inspect formbricks_uploads --format '{{.Mountpoint}}')
tar -czf $BACKUP_DIR/uploads_$DATE.tar.gz "$UPLOADS_PATH"

# Retain 30 days
find $BACKUP_DIR -mtime +30 -delete

---

Formbricks vs Typeform vs SurveyMonkey

Feature	Formbricks (self-hosted)	Typeform	SurveyMonkey
Price	~$10/mo server	$50-83/mo	$39-99/mo
Self-hosted	✅	❌	❌
In-app surveys	✅	❌	❌
Conditional logic	✅	✅	✅
File upload	✅	✅	✅
NPS tracking	✅	✅	✅
Webhooks	✅	✅	✅
Data ownership	✅ Full	❌	❌
GDPR compliant	✅ (by design)	⚠️ EU transfer	⚠️
White-label	✅	💰 Paid	💰 Paid
API	✅	✅	✅
Response analytics	✅	✅	✅

---

Troubleshooting

Formbricks won't start:

docker compose logs formbricks
# "DATABASE_URL" connection error: ensure postgres is healthy
docker compose ps  # check postgres status

Emails not sending:

docker compose logs formbricks | grep -i "smtp\|email\|mail"
# Test SMTP: docker compose exec formbricks curl smtp://your-host:587

SDK not triggering surveys:

# In browser console:
formbricks.getState()
# Should show environmentId and person attributes

---

Formbricks is a top Typeform alternative on OSSAlt — see all open source form and survey builders.

Why Self-Host Formbricks?

The case for self-hosting Formbricks comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Formbricks means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Formbricks, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Formbricks headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Formbricks data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Formbricks without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Formbricks's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Formbricks backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Formbricks's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Formbricks's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Formbricks's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Formbricks's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f formbricks

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Formbricks's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats formbricks. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Formbricks Updated

Formbricks follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Formbricks is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.