Forms-Engine vs Formbricks
Formbricks and Forms-Engine are both open-source and both self-hostable, but they answer different questions. Formbricks describes itself as an open-source Qualtrics alternative — experience management. Forms-Engine is an embeddable questionnaire engine — data collection inside your product or site.
What Formbricks is
Section titled “What Formbricks is”A full survey platform: link surveys, website surveys, and in-app micro-surveys with user targeting, plus built-in analytics and response management. The core is AGPLv3 and self-hostable via Docker (with some enterprise-licensed functionality in the repo), and a hosted cloud is offered for teams who don’t want to operate it.
Where Formbricks is stronger
Section titled “Where Formbricks is stronger”- Surveys as a discipline. Targeting who sees what and when, in-product micro-surveys, churn/NPS-style workflows — purpose-built capabilities Forms-Engine doesn’t have.
- Built-in analytics. Summaries and insights in the product; Forms-Engine offers raw browsing and CSV export, with analytics on the roadmap.
- A hosted option when running infrastructure isn’t on the table.
- Community and pace — an established open-source project with an active contributor base.
Where Forms-Engine differs
Section titled “Where Forms-Engine differs”- Embeddable-first. The unit of deployment is a web component in your page — the product demonstrating structured questionnaires as part of your own flow (an intake form, an application, an assessment), not a survey delivered about your product.
- Structured, versioned questionnaires. Multi-step/tab/section hierarchy, a rules engine with pinned semantics, version-pinned responses, content-verified file uploads — form-of-record features more than survey features.
- MIT vs AGPL. MIT imposes no copyleft obligations if you modify or embed the code. (For pure self-hosted use, AGPL is no obstacle — this matters mainly if you’re building on top.)
- Radically smaller operational footprint — two containers plus Mongo/MinIO, no auth system to configure because there isn’t one (which cuts both ways; see the security posture).
Honest bottom line
Section titled “Honest bottom line”If your need reads like “measure user sentiment, target segments, watch dashboards” — Formbricks is built for exactly that and Forms-Engine isn’t. If it reads like “our app needs real multi-step forms with conditional logic, files, and versioned responses in our own database” — that’s Forms-Engine’s home ground.