Deploy and Host Formbricks on Railway

Formbricks is an open-source survey and experience management platform, often self-hosted as an alternative to Typeform or Qualtrics. You build link surveys, website and in-app surveys, and NPS, CSAT or CES questionnaires in a visual editor, then review the responses, with all of the data kept in your own database.

About Hosting Formbricks

Formbricks 6 runs as several services. This template deploys Formbricks 6.1.4 with everything its official Docker Compose setup expects: PostgreSQL with pgvector, Redis for sessions and caching, Formbricks Hub and its worker, Cube for analytics, SpiceDB for permissions, and a Railway Bucket for file uploads. The services talk over Railway's private network, and only Formbricks gets a public domain. Secrets are generated at deploy time, and every image is pinned to a fixed version. The first deploy takes a few minutes while the databases are created and migrated. When Formbricks is up, open its public URL and create the administrator account.

Common Use Cases

Customer feedback surveys (NPS, CSAT, CES) shared as links or embedded on your website
In-app product surveys and user research in web and mobile apps, using the Formbricks SDK
Employee and internal surveys, such as eNPS, onboarding or event feedback, where responses must stay on your own infrastructure

Dependencies for Formbricks Hosting

PostgreSQL with pgvector (Railway Postgres): Formbricks data, plus separate hub and spicedb databases on the same server
Redis (Railway Redis): sessions, caching and rate limiting
Formbricks Hub and Hub Worker: the feedback record API and its background jobs
Cube: the analytics query layer
SpiceDB: permissions
Railway Bucket: S3-compatible storage for uploaded files

Deployment Dependencies

Implementation Details

First login. The first person to open the URL creates the administrator account. After that, public sign-up is closed, and other people join through invitations.

Email (SMTP) is not configured. Without it, Formbricks can't send invitations (copy the invite link from the organization settings instead), email verification and password reset are turned off, and no email notifications are sent. To turn email on, add these variables to the Formbricks service: MAIL_FROM, MAIL_FROM_NAME, SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, and SMTP_SECURE_ENABLED=1 if your server uses port 465. Then set EMAIL_VERIFICATION_DISABLED and PASSWORD_RESET_DISABLED to 0 if you want those features.

File uploads. Survey images, file-upload questions and logos are stored in the Railway Bucket. The bucket stays private, and Formbricks signs every upload and download. When it starts, the Cube service adds a CORS rule to the bucket, but only if the bucket has none, so that browsers can upload directly.

Enterprise features. Formbricks 6 won't start without Hub and Cube, but the screens that use them (Feedback Data and Analysis dashboards) need a Formbricks Enterprise licence (ENTERPRISE_LICENSE_KEY). Surveys and responses work without one.

Resources. About 1.2 GB of RAM when idle across all services, most of it Formbricks itself.

Versions. Formbricks 6.1.4, Hub 0.14.2, Cube 1.7.50 and SpiceDB 1.52.0, as in upstream's compose for 6.1.4. The Cube image and its setup script are in aalfath/formbricks-railway-template.

Why Deploy Formbricks on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Formbricks on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.