Why open source
Your Postgres. Your API. Your call.
Bring your architect. We'll go through deployment, security and sizing.
13k+ GitHub starsAGPLv3ISO 27001 certified
Experience data is customer data. Treat it like the rest of it.
Every survey answer, review and support comment carries names, emails, order numbers and whatever customers type into a free-text box. Most companies leave it in a vendor's cloud and rent it back as dashboards. Self-hosted, it sits next to the rest of your customer data, under your controls, ready for your data platform.
What runs where
Everything Formbricks runs sits in your environment.
Formbricks app
- What it is
- The Formbricks application, shipped as container images.
- Who runs it
- You, us or a partner.
- Third party access
- None, not even us.
PostgreSQL
- What it is
- Your relational database.
- Who runs it
- You.
- What data it holds
- Responses, contacts, survey definitions, settings.
S3-compatible storage
- What it is
- Object storage in your environment.
- Who runs it
- You.
- What data it holds
- Files respondents upload.
Identity provider
- What it is
- Your SSO provider.
- Who runs it
- You.
- What data it holds
- Who your team members are.
Your AI model
- What it is
- Azure OpenAI, another approved provider, or an open model you host.
- Who runs it
- You or your provider.
- What data it holds
- Text sent for enrichment, under your terms with that provider.
Your data platform
- What it is
- Your warehouse or data lake.
- Who runs it
- You.
- What data it holds
- Whatever you send it through the API and webhooks.
Your agents
- What it is
- Your own AI agents and tools.
- Who runs it
- You.
- What data it holds
- What they query through MCP.
Formbricks license server
- What it is
- Our server that validates your license key and receives anonymous usage telemetry.
- Who runs it
- Formbricks.
- What data it holds
- Your license key, its status and anonymous usage telemetry. No responses or customer data.
Formbricks app
Runs as containers on your infrastructure.
Your database
Responses, contacts and settings live in your PostgreSQL.
Your storage
File uploads go to your S3-compatible storage.
Your identity provider
People sign in through it, with SAML or OIDC.
Your AI model
AI enrichment calls the model endpoint you configure.
Your data platform
Feedback leaves only the way you send it: the REST API, webhooks or the MCP server, into your warehouse, your data lake or your own agents.
Calls home for two things
The license check and anonymous usage telemetry. Neither includes responses or customer data. Everything else goes only where you point it: your AI model, your mail server, your webhooks.
A license key, not a migration
Review the open source code. Then add a key.
The Experience Suite is the open source code you can already run, plus a license key. Install the Community Edition and run your architecture and security reviews against it. When you add the key, single sign-on, roles, audit logs and the rest switch on in the same instance. Nothing to migrate. Nothing to review again.
A global manufacturer ran every architecture, security and compliance review on the open source version. Switching to the Enterprise Edition took the license key and a server restart.
What it takes
Is this another thing we have to run?
Fair question. Here's the honest answer.
| Who does what | You run the servers and the database. We ship the software, security fixes and support. |
|---|---|
| Over your volume | The software keeps running. We settle it at renewal. |
| Help | The Premium deployment success plan adds help with environment setup, cluster hosting and AI hosting. Partners can run it for you. |
AI on your terms
Use the model you already approved.
Point Formbricks at Azure OpenAI, another provider your security team has cleared, or an open source model you host. There's no new provider to review, no markup on inference, and we don't train models on your customers' words. Your own agents can query feedback through the API or the MCP server.
The manufacturer runs AI enrichment on Azure OpenAI models its compliance team had already cleared. If cost becomes a concern, it can switch to an open source model.
Things your security team can check
Don't take our word for it.
Every line is on GitHub
The code that runs on your servers is public. Read the code on GitHubISO 27001 certified
For how we build, ship and support Formbricks.SOC 2 Type II
The report is available on request. Request security documentsEnterprise controls
SAML and OIDC single sign-on, roles, audit logs and data retention policies.Public terms
Our DPA and license agreement are public.Accessibility report
An accessibility conformance report (VPAT) is available.
Our ISO 27001 and SOC 2 cover how we build, ship and support Formbricks. On a self-hosted instance, your controls cover your servers and network. More detail: IT & security
Build on it
Send your CX lead their page
Your CX team will ask what changes for them. The Customer Experience page answers that in their words.
Bring your architect.
We'll go through deployment, sizing, security review and AI setup on your stack. You'll pick a time right in the form.