When LimeSurvey or Formbricks fits your team
LimeSurvey fits a team running research studies that need depth in questionnaire design. Its GPL-2.0-or-later license, more than 30 question types and multilingual surveys in more than 80 languages suit academic and market research on a PHP stack you host yourself. Formbricks fits a product team that wants surveys inside its own website or app. Its AGPLv3 core includes SDKs and website, app, link and email-embedded surveys, while the enterprise code ships in the Docker images and stays locked until an Enterprise License Key is applied. The decision turns on three questions: whether you need SSO or role-based access, whether the Community Edition limits matter to you, and who will run the stack.
Identity and roles are where the two products diverge most sharply. In self-hosted Formbricks, OIDC and SAML SSO, teams and access roles, audit logs and whitelabel email follow-ups all sit behind the Enterprise license. A team that must sign in through its corporate identity provider or split access by role should include that license in the decision before the first install. The Community Edition is limited to one workspace, which may suit a single product team but not several business units sharing one instance. Privately kept forks must also be released under AGPLv3 unless an Enterprise license covers them, so ask legal counsel to review that term. For LimeSurvey, confirm its authentication and role options in its own documentation and in a test install before assuming any parity with Formbricks.
Running costs follow the stack. LimeSurvey Community Edition requires PHP 8.1.29 or later with mbstring and PDO drivers, plus MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. The older 6.17.19 release reached end of support on August 31, 2026, so new installs should start on the 7.6.0 stable release. Formbricks can be self-hosted with Docker without a subscription and also offers a Helm chart for cluster hosting. If your team already runs PHP and a managed relational database, LimeSurvey adds little new operational surface. If it runs containers on Kubernetes, Formbricks fits that pattern. In either case, name the person who will apply upgrades, back up the database and track security releases, because that work recurs for the life of the install.
Which team fits which scenario for LimeSurvey vs Formbricks
This table maps common team situations to the platform that fits each one better and the condition that decides it. Read each row as a starting point: where both platforms can do the job, the row says so and names what would tip the choice. The main takeaway is that LimeSurvey suits structured research questionnaires, while Formbricks suits feedback embedded in products and websites.
| Scenario | Better fit | Why and when the other platform also works |
|---|---|---|
| Academic or market research with complex branching and multilingual panels | LimeSurvey | LimeSurvey supports more than 30 question types and multilingual surveys in more than 80 languages, and it has export plugins such as ExportR and ExportSTATAxml. Formbricks also handles multi-language surveys and advanced logic, but confirm that its question types and export options cover your study design before committing. |
| In-app NPS or feedback widgets inside a product | Formbricks | Formbricks is built for in-product and app surveys, with SDKs and embedding for websites and apps. LimeSurvey is oriented toward standalone questionnaires, so an in-app widget would need custom work to reach the same result. |
| Customer feedback on a marketing website | Formbricks | Website and link surveys are core to Formbricks, and the Community Edition includes them. LimeSurvey can publish a public survey link, but it does not offer the same embedded website pattern as its primary use case. |
| Employee surveys that must use corporate SSO | Formbricks, with the Enterprise license | OIDC and SAML SSO require the Formbricks Enterprise license and a license key, so budget for that cost. If your identity provider requirement is strict, confirm the exact SSO setup with DeployOpen or the vendor before choosing Formbricks. |
| A team already running PHP and MySQL or PostgreSQL | LimeSurvey | LimeSurvey is a PHP application that needs PHP 8.1.29 or later with mbstring and PDO drivers, plus a supported database. Your existing PHP operations skills and database backups transfer directly. Formbricks is not a PHP stack, so it adds a new runtime to maintain. |
| A team already running Docker or Kubernetes | Formbricks | Formbricks can be self-hosted with Docker without a subscription, and the Community Edition includes a Helm chart for cluster hosting. LimeSurvey can also run in containers, but confirm the image and upgrade path with your platform team, since Formbricks is designed around this model. |
| A single product team needing one workspace | Formbricks | The Formbricks Community Edition is limited to one workspace, which fits a single product team. If you need multiple teams with separate roles, that falls under the Enterprise license. LimeSurvey covers a single team as well, but its strength lies in research questionnaires rather than product feedback loops. |
How LimeSurvey and Formbricks are built and deployed
LimeSurvey and Formbricks take different routes to a self-hosted install, and those routes shape who patches, backs up and answers the pager. The cards below cover the application stack, the licensing boundary inside Formbricks, where respondent data lives, and what each choice means for day-two operations.
LimeSurvey as a PHP application
LimeSurvey Community Edition is a PHP application that needs PHP 8.1.29 or later with the mbstring and PDO drivers. The supported database minimums are MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Check the PHP extensions and database versions against your current host image before you download the Community Edition package, because a server built for another application may lack them.
Formbricks core and Docker images
The Formbricks core application is AGPLv3 and self-hosts with Docker without a subscription. A Helm chart is included for cluster hosting, so the team choosing it should decide early whether it runs a single container host or Kubernetes. Confirm the image tag you deploy against the current release list before you pin it in production.
Enterprise code in the same images
The Enterprise module ships inside the same Docker images as the core application, under a separate Enterprise license. Features such as SSO, teams and access roles are unlocked with an Enterprise License Key, so the image you run is the same one whether or not a key is present. Ask your security team to confirm how the key is loaded and stored, and what happens to enterprise features if it lapses.
Where respondent data lives
In either self-hosted install, survey responses sit in the database you run in your own infrastructure. LimeSurvey stores data on the organization's server or its provider's server, so data residency depends entirely on where you deploy it. Confirm the region, backup location and any third-party sync for both products before collecting personal data from EU or UK respondents.
Patching and version lifecycles
LimeSurvey 6.17.19 reached end of support on August 31, 2026, so the team must plan a move to the current 7.x line on its own schedule. Formbricks 6.0.2 was published on October 1, 2026. Both products need a tested upgrade path, a staging environment and a named owner for each release, since neither maintains a long-term support branch that avoids upgrades.
Backups and on-call load
A LimeSurvey install adds PHP runtime patching, web server and database maintenance to the pager. A Formbricks install adds container orchestration, the Enterprise License Key and the database. Write a runbook covering database backups, restore tests and the first responder for each product, and ask whoever supports you to confirm which of these they handle under a retainer.
Capability comparison: LimeSurvey and Formbricks feature claims
This table sets the feature claims supplied for each platform against the same capability rows, so you can see where the products overlap and where they diverge. Where a row shows a confirm note, the figure or behavior was not established in our sources and should be checked with the vendor before you rely on it. The main takeaway is that LimeSurvey is the stronger fit for research-style questionnaires, while Formbricks centers on in-product and link feedback with SSO and roles gated behind an enterprise license.
| Capability | LimeSurvey | Formbricks |
|---|---|---|
| License | GPL v2.0, with the option to use any later GPL version | Core under AGPLv3; enterprise module under a separate Enterprise license |
| Question types and languages | More than 30 question types; multilingual surveys in more than 80 languages. Confirm current language coverage with the vendor. | Advanced logic and multi-language surveys included in Community Edition. Confirm the question type count and language list with Formbricks. |
| Plugins and export | Plugins include ExportR and ExportSTATAxml for analysis-ready exports | Webhooks included; integrations with Slack, Notion, Zapier and n8n. Confirm export formats with the vendor. |
| Survey delivery (link, website, app, email) | Survey links and embedded surveys; confirm app-based delivery options for your use case | Website, app, link and email-embedded surveys included in Community Edition |
| SDKs and API | Confirm API scope and SDK availability with the vendor | Full API access and all SDKs included in Community Edition |
| SSO | Confirm SSO options for your edition with the vendor | OIDC and SAML SSO require the Enterprise license |
| Roles and teams | Admin users are counted per plan on LimeSurvey Cloud (1 to 10 admins). Confirm role granularity for self-hosted installs. | Teams and access roles require the Enterprise license |
| Audit logs | Confirm audit logging with the vendor for your install | Audit logs require the Enterprise license |
| Community Edition limits | Free to download and self-host with no published response cap in the supplied sources | Unlimited surveys, responses and users, but limited to one workspace. Privately kept forks must be AGPLv3 unless covered by an Enterprise license. |
| Self-hosting method | Self-hosted on PHP with MySQL, PostgreSQL, MariaDB or MSSQL; PHP 8.1.29 or later required | Self-hosted with Docker, with a Helm chart for cluster hosting, and no subscription needed for Community Edition |
| Cloud hosting regions | Germany, Finland, the UK, the USA, Canada and Australia; Germany or Finland recommended for EU customers | Formbricks Cloud Hobby plan hosted in Frankfurt. Confirm other regions with the vendor. |
What each edition costs in licensing terms
LimeSurvey Community Edition is licensed under GPL v2.0, with the option to use any later GPL version, and it is free to download and self-host. Your organization pays no license fee for the software, but it pays for the server, the database, PHP upkeep and any outside help used to install and run the platform. Survey data stays on servers that you or your hosting provider control.
- License terms: GPL v2.0 with the option of any later GPL version. Obligations attach when you distribute modified code, so confirm with counsel how internal changes are treated.
- Paid items: no license fee. Recurring costs are hosting, database and PHP maintenance, staff time and any implementation services.
- Version currency: LimeSurvey Community Edition 7.6.0 is the latest stable release, and 6.17.19 reached end of support on August 31, 2026, so older installs need a planned upgrade.
- Requirements: PHP 8.1.29 or later with mbstring and PDO drivers, plus one of the supported database versions.
Check which level of support your team needs, and ask any implementation partner for a written quote based on your defined scope.
LimeSurvey Cloud is a hosted subscription with checkout in euros. The plans are capped by responses and admin users, and the subscription pays for hosting and the vendor's operation of the service. The plan limits decide whether a given study fits, so match them to your peak volume before you commit.
- Basic: 1,000 responses per month and 1 admin user.
- Expert: 10,000 responses per year and 3 admins.
- Business: 50,000 responses per year and 5 to 10 admins.
- Corporate: priced by quote for teams that need more than the listed plans.
- Regions and lapse: hosting regions include Germany, Finland, the UK, the USA, Canada and Australia, with Germany or Finland recommended for EU customers. When a subscription expires, the account falls back to the Free package and keeps access to collected responses.
Compare the response caps with your busiest month and year, and confirm the data processing terms for your region with LimeSurvey before you sign.
Formbricks Community Edition is the self-hosted core, licensed under AGPLv3. It runs with Docker without a subscription and includes unlimited surveys, responses and users, but it supports only one workspace. The license cost is zero, and the operating cost of hosting, upgrades and backups falls to your team.
- License: AGPLv3 for the core application. The AGPL includes a source obligation for modified versions that users interact with over a network, so confirm how it applies to your deployment with counsel.
- Included: full API access, all SDKs, website, app, link and email-embedded surveys, advanced logic, multi-language surveys and UI, file upload, webhooks and a Helm chart for cluster hosting.
- Limit: one workspace. Teams that need several separate workspaces will need a different setup or the Enterprise license.
- Private forks: privately kept forks must be released under AGPLv3 unless an Enterprise license covers them. Internal-only changes still need a legal review before any modified build reaches users.
Ask for a written review of the license terms, including how your changes are handled, before you build on a fork. The Formbricks license documentation sets out the current terms.
Formbricks Enterprise is a separate license for code in the enterprise module. That code ships in the Docker images and stays locked until you apply an Enterprise License Key. Teams buy it when identity, access and audit requirements call for features the Community Edition does not include, and the license is the only thing that unlocks them.
- Identity: OIDC and SAML SSO.
- Access: teams and access roles.
- Governance: audit logs, contact management and segments, and quota management.
- Brand and email: whitelabel email follow-ups and removal of the Powered by Formbricks badge.
- Terms: the license is priced by quote from Formbricks. Ask for the fee, the renewal terms and what happens to enterprise features if the key expires.
Before you buy, list the features your security and compliance reviews require and confirm in writing that each one sits inside the Enterprise license.
Formbricks Cloud is the hosted option with three plans. The pricing shown in October 2026 starts with a free Hobby plan, and the paid plans are priced per month and sized by responses. Cloud fees pay for hosting and operation, so they replace the infrastructure work of a self-hosted install rather than the license itself.
- Hobby: free, with 250 responses per month, hosted in Frankfurt.
- Pro: $74 per month, with 2,000 responses.
- Scale: $325 per month, with 5,000 responses.
- Feature scope: confirm whether SSO, roles and audit logs are included in each Cloud plan, since the self-hosted license terms do not settle this for hosted plans.
- Lapse: confirm in writing what happens to collected responses and to access when a paid Cloud subscription ends.
Match the response caps to your expected volume, and get the lapse and data retention terms in writing before you move live surveys to a hosted plan.
What drives running cost for each platform
The main running cost of self-hosted LimeSurvey is staff time, not the software. LimeSurvey Community Edition is free to download and self-host, so your team or a provider pays for the server, the PHP and database stack, and the people who keep them current. That means someone maintains the PHP runtime and the database (MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later, per the LimeSurvey repository), applies upgrades, and runs backups and restore tests. Self-hosted Formbricks has a similar shape, with Docker and database upkeep as the recurring work. Its cost differs at the point where you need the enterprise features. OIDC and SAML SSO, teams and access roles, audit logs and removing the Powered by Formbricks badge all require an Enterprise License Key, so a license fee is added to the staff cost. Ask both vendors and any partner which of these items your quote includes and which are your responsibility.
Installation and migration are mostly one-time costs. Recurring costs are upgrades, backups, monitoring, security patching and license renewals, and they continue for as long as the platform runs. Formbricks Cloud, as read in October 2026 from its pricing page, lists Hobby free with 250 responses per month hosted in Frankfurt, Pro at $74 per month with 2,000 responses and Scale at $325 per month with 5,000 responses. LimeSurvey Cloud, as read in October 2026 from its pricing page and checked out in euros, lists Basic with 1,000 responses per month and 1 admin user, Expert with 10,000 responses per year and 3 admins, and Business with 50,000 responses per year and 5 to 10 admins. Those plans show what hosted subscriptions scale with: response volume, admin seats and, for Formbricks, workspaces and identity-linked users. Confirm current prices on the vendor pages before you budget, because both vendors can change them.
Four drivers push running cost up or down on either side. Response volume drives server capacity and, on hosted plans, the tier you buy. Admin count and, for Formbricks, the number of workspaces affect seat or plan pricing, and the Community Edition is limited to one workspace. The number of identity-linked users determines whether SSO is needed at all, which in turn determines whether the Enterprise License Key is needed. Language count and data residency also matter: LimeSurvey Cloud offers regions including Germany, Finland, the UK, the USA, Canada and Australia, and EU customers are advised to choose Germany or Finland, while self-hosting lets you place data in your own facility. When requesting a written quote, ask for: the license fee and its renewal terms, what the partner covers for installation, upgrades and backups, the hours or retainer level for ongoing support, hosting and storage assumptions, and the cost to exit if you move between platforms.
How to move surveys from one platform to the other
This sequence moves survey definitions, responses and collection points from LimeSurvey to Formbricks, or the reverse, without losing data or interrupting respondents. Each step ends with a check that tells you whether it is safe to move on.
Inventory surveys, question types and logic
List every active and archived survey, its question types, skip logic, quotas, language versions and the places it is published, such as a web link, an email invitation or an embed in an app. LimeSurvey supports more than 30 question types, so record which ones your surveys actually use. Confirm with Formbricks which question types, advanced logic and multi-language setups it covers in your edition, since the Community Edition documentation lists advanced logic and multi-language surveys but you should test your specific constructs. The step is done when you have a spreadsheet that maps each survey to its target feature or to a workaround.
Export responses and survey metadata
Export response data and question metadata from LimeSurvey. The LimeSurvey GitHub repository lists plugins such as ExportR and ExportSTATAxml, which you can use to produce analysis-ready files alongside the standard export. Keep response timestamps, question codes and value labels, because these are what your analysts rely on. Confirm with your LimeSurvey administrator which export plugins are installed on your instance and whether they export every question type you use. The step is done when you have a complete archive, a checksum or row count for each survey, and a test reopen of the files.
Rebuild surveys and embeds on Formbricks
Recreate each survey in Formbricks, mapping LimeSurvey question types to the nearest Formbricks equivalent and flagging any gaps for redesign. Rebuild the collection points: link surveys, website or app embeds and email follow-ups. Formbricks does not import LimeSurvey structures automatically, so treat this as a manual rebuild that needs careful testing. Confirm with Formbricks which SDK and embed options match your application stack. The step is done when each rebuilt survey passes a test run against your mapping sheet and each embed loads in a staging environment.
Move identity, roles and workspace structure
Map LimeSurvey admin users and their permissions to Formbricks roles and teams. In Formbricks, SSO through OIDC or SAML and teams with access roles are part of the Enterprise license, while the Community Edition is limited to one workspace. Decide before rebuilding whether you need that license, and confirm the exact license terms with Formbricks before you depend on them. The step is done when every former admin has a documented role on the target, SSO sign-in has been tested with a non-admin account, and workspace layout matches your access model.
Run a parallel collection period
Keep both platforms collecting for an agreed overlap so you can compare response counts, completion rates and data formats before cutting over. Route new traffic to Formbricks only after the rebuilt surveys have matched LimeSurvey on a test set. Monitor webhooks, integrations with Slack, Notion, Zapier or n8n, and any downstream analytics pipelines. The length of the overlap is your decision, not a supplied figure, so agree it in writing with the people who own the data. The step is done when response counts reconcile for the same period and downstream consumers have confirmed they read the new data correctly.
Retire the source platform
Close LimeSurvey collection points, change or remove embeds and links in applications and emails, and archive the final export with its hash and access log. Keep the source instance or its data available for the retention period your research or compliance policy requires, and confirm that retention rule with your data protection lead before deleting anything. If you run LimeSurvey Cloud, confirm with LimeSurvey what happens to data at subscription end, since its pricing FAQ says an expired account falls back to the Free package and keeps access to collected responses. The step is done when no live collection points point at the old platform and the archive is verified.
Where LimeSurvey and Formbricks implementations run long
LimeSurvey delays usually start with the stack and the research data, not the survey build. Self-hosting the Community Edition means aligning the PHP runtime and database with the supported versions before anything else, and the LimeSurvey GitHub repository lists PHP 8.1.29 or later with mbstring and PDO drivers, plus MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Confirm these against your own hosts and your patching cadence, because a database version that is already in use elsewhere often forces a second build. Surveys with many languages add a separate workload: the platform supports multilingual surveys in more than 80 languages, but each translation still needs a named reviewer who signs off wording for research instruments. Ask the study owners who approves translations before the build starts. Data protection review is the third common stall. Survey data lives on your server or your provider's, so the data protection officer needs to sign off on the hosting location, retention and access to responses before any live collection. If you are weighing LimeSurvey Cloud, confirm the region with that officer first, since the pricing page lists several hosting regions.
Formbricks delays usually come from the product integration and the identity provider, not the survey editor. Embedding surveys in an application means installing the SDKs into the product codebase, so the product team must own that change, its release schedule and its testing. The identity side is the longer item. Self-hosted OIDC or SAML single sign-on requires the Enterprise license, so decide early whether SSO and team roles are mandatory. If they are, obtain administrative access to your identity provider, the redirect and metadata values, and a named owner for group mapping to Formbricks roles. Without that access, the work stalls at the first login test. Operations are the last item. Formbricks runs with Docker, and Helm is available for cluster hosting, so the platform team must decide which path it will operate, who handles upgrades and where backups of the database sit. Confirm the chosen image and version with the Formbricks GitHub releases page before the build is locked, and confirm with your own security team whether an Enterprise License Key will be issued for the target environment.
Questions buyers ask before choosing LimeSurvey or Formbricks
Does Formbricks Community Edition include SSO?
No. The self-hosted Community Edition does not include SSO. Per the Formbricks license documentation, OIDC and SAML SSO require the Enterprise license, which is unlocked with an Enterprise License Key on top of the Docker images. The same key covers teams and access roles, so if your identity provider must sign people in, plan for the Enterprise license from the start. Confirm the current feature list with Formbricks before you finalize scope, since the Enterprise module is versioned separately from the core application.
What drives the cost of the Formbricks Enterprise license, and who do I ask for a quote?
The Enterprise license is a separate commercial agreement from the AGPLv3 core, so its price is set by Formbricks, not by DeployOpen. Ask Formbricks directly for current Enterprise terms. The Formbricks pricing page lists Cloud plans, which are a different product and do not replace a self-hosted Enterprise license. Costs you should budget for beyond the license include hosting, database operations, upgrades and any integration work. DeployOpen can quote the implementation and support scope in writing, but it does not publish a price list and does not set license fees.
Can our team run LimeSurvey or Formbricks without outside help?
A team with Linux, PHP or Docker experience and a database administrator can run either platform, but the workload differs. LimeSurvey Community Edition is a PHP application that needs PHP 8.1.29 or later with mbstring and PDO drivers, plus a supported database, so you own PHP and database upgrades. Formbricks runs from Docker images or a Helm chart, so your team must own container hosting and upgrades. Whether you need outside help depends on your in-house skills, change process and how many people will maintain the system. DeployOpen can take on planning, hardening, backups, upgrades and documentation under a fixed-scope agreement or a retainer.
How long does an implementation take, and what drives the timeline?
No general duration is supplied for either platform, so treat any single number with caution. The main drivers are the number of surveys or in-product flows to migrate or build, whether you need SSO and role-based access, the hosting model you choose, integration with downstream tools such as Slack, Zapier or n8n, and your security review and compliance evidence needs. Ask for a written scope that lists deliverables and milestones before work starts, because most engagements are fixed-scope and timelines follow from that scope.
Can survey data stay inside the European Union?
Yes, when you self-host, because the data sits on servers you or your provider control, so you choose the region. LimeSurvey Community Edition stores survey data on your organization's or its provider's server. If you use LimeSurvey Cloud, its pricing FAQ lists hosting regions including Germany and Finland, with Germany or Finland recommended for EU customers. Formbricks Cloud's Hobby plan is hosted in Frankfurt according to its pricing page. Confirm the region for your chosen plan and any sub-processors in writing before you collect personal data.
What happens to LimeSurvey data if a Cloud plan lapses?
When a LimeSurvey Cloud subscription expires, the account falls back to the Free package and keeps access to collected responses, according to the LimeSurvey pricing page FAQ. That protects access to data but not your plan limits, so confirm with LimeSurvey what the Free package allows for new collection and export before relying on it. If you run Community Edition yourself, a lapsed subscription does not apply, but you must keep your own backups and export routine in place.
Does a fixed-scope engagement cover migrating existing surveys?
It can, if migration is written into the agreed scope. DeployOpen plans, implements, integrates and documents self-hosted platforms, and most engagements are fixed-scope with scope, deliverables and timelines agreed in writing before work starts. Migration of questionnaires, responses, users and integrations is a separate workstream that needs an inventory of what you hold, a decision on which data to move, and validation after cutover. Ask for the migration inventory, data mapping, test plan and rollback steps to be listed as deliverables.
How DeployOpen helps choose, implement or migrate
DeployOpen works on LimeSurvey vs Formbricks as a self-hosting partner, starting with the question of which platform fits the research, in-product or embedded survey work your team actually runs. We plan, implement, integrate, harden, document and support the chosen platform inside your own infrastructure, so the decision is tested against your real hosting, identity and data requirements.
How we scope
- We confirm which survey types, languages and response volumes your teams need before comparing editions.
- Written scope lists the hosting target, identity integration, roles and data location agreed before work starts.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before any work begins.
How we build
- We install the chosen platform in your cloud account, data center or air-gapped network, with the database and PHP or Docker stack you approve.
- Integrations such as SSO, embedding in your applications and webhooks are configured and tested against your environment.
- Security testing of the deployed application and its APIs is available as a separate scoped engagement.
How we hand over
- Deliverables include architecture, configuration and runbook documentation written for your own operations team.
- Backup and upgrade procedures are documented so your staff can run restores and version changes after handover.
- Compliance readiness material, such as controls and evidence for your assessor, is prepared; audit reports remain with independent auditors.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Retainers can cover platform version upgrades, which matter when a release support window closes.
- Ask for the support scope, response expectations and upgrade responsibilities in writing before you sign.
