Formbricks vs Heyform vs Typebot 2026

The Case for Self-Hosted Forms

Typeform charges $25-83/month. Google Forms sends your data to Google. SurveyMonkey starts at $39/month for team features. Tally has a limited free tier with paid plans starting at $29/month.

Beyond cost, forms collect sensitive data — customer feedback, employee satisfaction, lead information, support requests. Sending this data through third-party servers means a vendor can see your customers' responses.

Self-hosted form builders let you collect this data on your own infrastructure, with no per-submission fees and no vendor data access.

TL;DR

• Formbricks (12K+ stars): Best for surveys, product feedback, and multi-touchpoint experience management. Replaces Typeform + Qualtrics functionality.
• Heyform (8.5K+ stars): Best for simple, conversational forms with excellent no-code experience. Easy to set up, clean UX for respondents.
• Typebot (7K+ stars): Best for chatbot-style interactive forms with conditional logic. Replaces Intercom chat forms and complex form flows.

Quick Comparison

Feature	Formbricks	Heyform	Typebot
GitHub Stars	12K+	8.5K+	7K+
Form style	Traditional + conversational	Conversational	Chatbot/conversational
Conditional logic	Yes	Yes	Yes (advanced)
Analytics	Excellent	Basic	Good
Partial submissions	Yes	No	Yes
Survey targeting	Yes	No	No
Webhooks/integrations	Yes	Yes	Yes
Self-hosting	Easy	Easy	Easy
License	AGPL-3.0	AGPL-3.0	AGPL-3.0

Formbricks — Best for Surveys and Feedback

Formbricks positions itself as an open source Experience Management suite — not just form building, but targeted surveys that appear to the right users at the right time across your product, website, and email.

What Makes It Stand Out

Multi-touchpoint surveys: Trigger surveys based on user behavior in your product. "Show this survey to users who have been active for 30 days." "Show this to users who just completed their first purchase." This is the Qualtrics-like targeting that distinguishes Formbricks from basic form tools.

Survey templates: Pre-built templates for common research scenarios:

• Net Promoter Score (NPS)
• Product-Market Fit
• Customer Satisfaction (CSAT)
• Churn Survey
• Feature Prioritization

In-app surveys: Embed surveys directly in your web application using the Formbricks SDK. Surveys appear as modals, sliders, or inline components — not separate pages.

Email surveys: Send surveys via email link. Track open rates, completion rates, and responses.

Analytics: Per-question analytics showing response distributions, completion rates, and drop-off points.

Insights: AI-powered analysis of open-text responses — summarize themes, sentiment, and key points from free-text answers.

Self-Hosting

git clone https://github.com/formbricks/formbricks
cd formbricks
cp .env.example .env
docker compose up -d

Formbricks runs as approximately 4 Docker containers (app, PostgreSQL, Redis, and optional email worker). The docker-compose setup is well-documented.

Best for: SaaS companies collecting product feedback, customer researchers, and teams needing targeted in-app surveys beyond what Google Forms or basic form builders offer.

Heyform — Best for Conversational Forms

Heyform provides a clean, conversational form experience similar to Typeform — one question at a time, with smooth transitions and a polished interface that increases completion rates.

What Makes It Stand Out

Conversational design: Questions appear one at a time with smooth animations. This reduces form abandonment compared to traditional multi-field forms.

No-code builder: The visual form builder is the most intuitive of the three tools. Drag, drop, configure — no technical knowledge needed.

Question types: Text, multiple choice, checkboxes, rating scales, NPS, opinion scale, date picker, file upload, payment (Stripe), and more.

Conditional logic: Show/hide questions based on previous answers. Create branching paths through a form.

Workspace management: Organize forms into workspaces for different teams or projects.

Response notifications: Email notifications when new responses arrive. Export responses to CSV.

Self-Hosting

git clone https://github.com/heyform/heyform
cd heyform
cp packages/server/.env.example packages/server/.env
docker compose up -d

Heyform runs as 3-4 containers (app, MongoDB, Redis). Straightforward deployment with good documentation.

Limitations

• Analytics are less comprehensive than Formbricks
• No in-app targeting capabilities
• MongoDB dependency (some teams prefer PostgreSQL)
• Less active development pace compared to Formbricks

Best for: Teams replacing Typeform who want a clean, conversational form experience without needing behavioral targeting or complex analytics.

Typebot — Best for Chatbot-Style Interactive Forms

Typebot turns form collection into a chatbot conversation. Instead of filling out fields, respondents interact with a chat interface — messages appear sequentially, they respond to each message, and the conversation flows based on their answers.

What Makes It Stand Out

Chat interface: The respondent experience feels like messaging, not form filling. Research shows conversational interfaces achieve higher engagement and completion rates for long or complex forms.

Visual flow builder: Build form flows on a canvas — blocks connected by arrows representing conditional paths. Similar to Flowise or LangFlow but for form logic.

Advanced conditional logic: Complex branching based on any previous answer. Create highly personalized paths through your form.

Integration blocks: Connect to external services within the form flow — send emails, create CRM records, trigger webhooks, query APIs. Typebot can perform actions mid-conversation.

Embedding options: Embed as a full page, a popup, a side panel, or a chat bubble on your website.

WhatsApp and SMS: Send Typebot forms via WhatsApp Business or SMS — conversations happen where your users already are.

Self-Hosting

git clone https://github.com/baptisteArno/typebot.io
cd typebot.io
cp .env.example .env
docker compose up -d

Typebot runs as 2 main services (builder and viewer) plus PostgreSQL and Redis. Clean separation between the form builder UI and the form delivery interface.

Limitations

• Complex forms require more setup than traditional form builders
• The chat interface isn't appropriate for all use cases (quick surveys, simple forms)
• More complex than Heyform for basic needs

Best for: Customer onboarding flows, lead qualification, support deflection, and any scenario where a conversational interface improves completion rates.

Real-World Use Cases

Customer Onboarding Survey

Best tool: Formbricks (in-app targeting) or Typebot (conversational)

Lead Generation Form

Best tool: Typebot (conversational = higher conversion) or Heyform (polished form experience)

Employee Satisfaction Survey

Best tool: Formbricks (templates, analytics, multi-touchpoint)

Contact / Support Form

Best tool: Heyform (simple, clean) or Typebot (with automatic routing)

Product Feature Research

Best tool: Formbricks (behavioral targeting, feature prioritization templates)

Event Registration

Best tool: Heyform (polished experience, easy to set up)

Cost Comparison

Typeform Annual Costs

Plan	Monthly	Annual
Basic	$25	$300
Plus	$50	$600
Business	$83	$996

Self-Hosted

Tool	Server	Annual
Formbricks (Hetzner CPX21)	$6.50/mo	$78
Heyform (Hetzner CPX21)	$6.50/mo	$78
Typebot (Hetzner CPX21)	$6.50/mo	$78

Any of these tools saves $222-918/year vs Typeform, with no per-response limits.

Combining Multiple Tools

Many organizations use more than one tool:

• Heyform for external-facing forms (contact, lead gen, registration)
• Formbricks for in-app product feedback and NPS
• Typebot for complex conversational flows (onboarding, qualification)

All three can run on the same VPS (with adequate resources), keeping total infrastructure cost low.

In-App vs Landing Page vs Chatbot Forms

The three tools serve distinct form delivery contexts, and using the wrong tool for the wrong context reduces completion rates and data quality.

In-app forms (Formbricks) are embedded within your product's user interface. They appear as slide-out panels, popups, or inline sections while the user is actively using your application. The critical advantage is context: a survey that appears immediately after a user uses a specific feature captures feedback about that exact experience, while the user's memory is fresh. NPS surveys sent via email three days later suffer from recall bias — users generalize rather than remembering the specific interaction. In-app forms can target specific user segments (paid users only, users who completed onboarding, users on a specific plan) without requiring email list segmentation. The behavioral trigger system means the survey appears at the right moment without any manual campaign management.

Landing page forms (Heyform) serve acquisition and external-facing use cases. A contact form on your website, a conference registration form, a job application, a customer onboarding intake form — these are standalone pages or embedded forms that external visitors complete without being logged into your product. Heyform's strength is the traditional form builder experience: drag-and-drop fields, theme customization, and straightforward embedding on any webpage. There's no SDK to install in your product, no behavioral trigger configuration — just a form URL or embed code you add to your site.

Chatbot forms (Typebot) work best for qualification and lead capture flows where conversation increases engagement. Research consistently shows conversational form formats achieve 30–40% higher completion rates than equivalent traditional forms for lead capture — the progressive disclosure (one question at a time) feels less overwhelming than seeing twenty fields simultaneously. Typebot is not a good fit for every use case: a simple contact form (name, email, message) is slower and more awkward in chatbot format than a traditional form. The conversational format adds value specifically when qualification logic is complex and engagement matters more than speed of completion.

For a direct comparison between Formbricks and Typebot specifically, see Formbricks vs Typebot 2026. For detailed deployment guidance, see How to Self-Host Formbricks 2026. For the broader form builder landscape including LimeSurvey, see Best Open Source Form Builders 2026.

GDPR Compliance for Self-Hosted Form Tools

Form data collection is a primary GDPR compliance concern. Every survey response, lead capture form, and feedback submission that contains a name or email address involves personal data processing under GDPR. Understanding how self-hosted form tools handle this differently from SaaS tools matters for compliance.

When you use a SaaS form tool (Typeform, SurveyMonkey), you are a data controller and the SaaS vendor is a data processor. You're required to have a Data Processing Agreement (DPA) with the vendor, and the vendor's privacy policy determines what happens to the data. Respondents' data may be stored in data centers outside the EU, which creates cross-border transfer issues. The SaaS vendor may use aggregated data for product improvement or share with third parties as described in their privacy policy. These are legitimate uses under GDPR but require disclosure to your respondents and diligent vendor management.

Self-hosting eliminates the data processor relationship with the form tool vendor. Your organization becomes both the data controller and the data processor. Response data stays on your servers, in your chosen geography, subject only to your internal data governance policies. There's no DPA to manage, no cross-border transfer risk, and no concern about how the vendor uses aggregated form data. The practical GDPR compliance work shifts entirely to your own policies: you need a privacy notice explaining what data you collect via forms, how long you retain it, and respondents' rights to access or delete their data.

Retention policy enforcement is your responsibility with self-hosted tools. All three tools expose API endpoints for deleting responses — you can build automated deletion workflows (delete responses older than 12 months) via cron jobs or integration with n8n for scheduled data hygiene. SaaS tools often have retention settings in their admin panel that handle this automatically; self-hosted deployments require implementing equivalent automation yourself.

---

Find Your Form Builder

Browse all form builder and survey tools on OSSAlt — compare Formbricks, Heyform, Typebot, and every other open source form builder with deployment guides and use case comparisons.

See open source alternatives to Formbricks on OSSAlt.