What does a self-hosted survey tool cost compared with SaaS?
The software license is free for the community editions of LimeSurvey and Formbricks, so the real cost of self-hosting is the infrastructure, setup, support and staff time around it. Whether that total beats a SaaS subscription depends on response volume, the edition features you need (SSO, access roles, audit logs), the hosting region you must use and whether your team already runs PHP or Docker workloads well. As reference points only, LimeSurvey Cloud lists Basic at 1,000 responses per month, Expert at 10,000 responses per year and Business at 50,000 responses per year, with Corporate priced by quote. Formbricks Cloud lists Hobby as free at 250 responses per month in Frankfurt, Pro at $74 per month for 2,000 responses and Scale at $325 per month for 5,000 responses. These are published list prices as read in October 2026, so confirm them on the vendors' pricing pages before you build a comparison.
The cost lines that move most are the ones a SaaS subscription hides. Self-hosting adds a recurring line for servers or cloud accounts, database and backup storage, email delivery for invitations and reminders, and monitoring. It also adds one-time work for installation, hardening, SSO integration and migration of any existing surveys. Formbricks self-hosting needs the Enterprise license for OIDC and SAML SSO, teams and access roles, audit logs and removing the Powered by Formbricks badge, so an organization that needs those features should price that license into the self-hosted option. Ask any implementation partner for a quote that separates one-time setup, recurring hosting and support, and any license fees, and for the assumptions behind each line, including response volume and the number of administrators.
Cost components: in-house, partner and SaaS
This table compares who pays for each cost component under an in-house build, an implementation partner engagement and a SaaS subscription, and whether each cost is one-time or recurring. Read it as a checklist for building a quote or internal budget, since the amounts depend on scope and sizing. The main takeaway is that the Community Edition removes the software license line but not the operating costs that come with it.
| Cost component | In-house build | Implementation partner | SaaS subscription |
|---|---|---|---|
| Software license | No license fee for LimeSurvey Community Edition or the Formbricks Community Edition (one-time download, recurring only if you buy a license) | Same as in-house, plus any Enterprise License Key you choose to buy for Formbricks features | Recurring subscription fee to the vendor, tiered by responses and admin users |
| Enterprise edition licensing | Needed only if you require Formbricks SSO, teams, audit logs or quota features; confirm the price with the vendor | Same license cost, passed through or quoted in the written scope | Usually included in the plan tier you buy; confirm which features sit in higher tiers |
| Hosting and infrastructure | Your servers or cloud accounts, recurring; you size, patch and monitor them | Same infrastructure, recurring, usually in your own accounts so you keep ownership | Included in the subscription; check the hosting region options against your residency needs |
| Initial setup and configuration | Internal staff time, one-time, covering PHP or container setup, database, SSO and survey templates | Fixed-scope one-time fee agreed in writing before work starts | Mostly account setup and survey design, one-time and light |
| Integrations | Developer time for each connection (for example Slack, Zapier, n8n or your data warehouse), one-time plus maintenance | Scoped one-time build per integration, with its own maintenance terms | Often prebuilt connectors or webhooks; custom links may still need your engineers |
| Security testing and hardening | Internal effort or external testing bought separately, recurring when repeated | Testing and hardening scoped in the engagement, one-time or retainer | Vendor controls apply; your own assessment evidence still depends on your configuration |
| Backup, upgrades and patching | Internal staff time, recurring; upgrades must track each new release and end-of-support date | Retainer or per-upgrade scope, recurring; confirm response and rollback terms | Handled by the vendor; confirm data export and deletion terms in the contract |
| Ongoing support | Internal on-call and troubleshooting, recurring | Support retainer, recurring, with terms agreed in writing | Vendor support tier, recurring and bundled with the subscription |
| Internal staff time | Largest hidden line: product owner, administrator, security reviewer and data protection contact, recurring | Smaller, focused on requirements, approvals and acceptance testing | Lower for administration, but still needed for survey design, consent text and data governance |
What moves each cost line up or down
Survey tool costs follow a small set of drivers. Some lines rise with usage, some with features and staffing, and some with compliance scope, so the same tool can cost very different amounts for two organizations.
Response volume
SaaS plans are priced by responses per month or per year, so volume is the most visible cost line on a subscription. Self-hosting removes the per-response meter, but infrastructure, database storage and backups grow as response counts and attachments grow. Estimate peak campaign volume, not just average volume, and ask a partner how load testing and capacity planning are scoped in a quote.
Enterprise features and license
Formbricks keeps the core application under AGPLv3, but OIDC and SAML SSO, teams and access roles, audit logs, quota management and a few other features sit behind an Enterprise license. Adding them is a recurring license decision that changes the total, so confirm which features your rollout needs before comparing against a SaaS tier that includes them.
Identity and access requirements
Single sign-on, role separation and reviewed access are often the reason a team moves from a free tier to a paid tier or a fully supported build. Each identity provider you connect adds configuration, testing and support time. Confirm whether your identity provider uses OIDC or SAML, and who owns role mapping after go-live.
Data residency and region choice
Cloud editions offer hosting regions, and a region choice can decide whether a SaaS plan is viable under your data rules. Self-hosting moves that decision to your own cloud account or data center, which adds hosting cost and staff time for backups, patching and disaster recovery. Ask a quote to state the hosting location, backup location and support access path separately.
Number of integrations
Each connection to a CRM, analytics tool, automation service or data warehouse adds build, testing and maintenance work. Formbricks supports webhooks and integrations with tools such as Slack, Notion, Zapier and n8n, but a custom sink for survey results usually needs a partner or internal developer. Count the destinations and the data fields each one needs before requesting a quote.
Admin users and compliance evidence
Cloud plans limit admin users, and self-hosting has no such limit but needs named owners for every administrator account. Compliance evidence scope adds work for access reviews, change records, retention settings and audit log exports. Clarify who prepares this evidence, because DeployOpen prepares controls and records for assessments but auditors and certification bodies issue any reports.
When a SaaS subscription is cheaper than self-hosting
A SaaS subscription is often the cheaper option when response volume is low, no single sign-on or audit trail is required, and respondent data has no residency constraint. In those cases the cost of hosting, patching and backing up a survey server, plus the staff time to keep it running, can exceed a small monthly plan. The published tiers make the comparison concrete. LimeSurvey Cloud lists Basic at 1,000 responses per month with one admin user, and Formbricks Cloud lists a free Hobby tier at 250 responses per month hosted in Frankfurt. Compare those limits against your own forecast, including peak months for campaigns and feedback drives.
The balance shifts when the data is regulated, must stay in a specific jurisdiction, or arrives in high volume. Health, research, public sector and EU-resident respondent data may require hosting you control, and a subscription that does not meet those terms removes the option entirely. High response counts push SaaS prices up on each tier, while a self-hosted deployment has a fixed infrastructure base. Enterprise needs such as OIDC or SAML single sign-on for Formbricks, which the Community Edition does not include, add licence cost to the self-hosted side as well, so price both paths with the same feature list.
Before signing any SaaS contract, check what happens to your data when the subscription ends. LimeSurvey's pricing FAQ states that an expired Cloud account falls back to the Free package and keeps access to collected responses. Confirm in the written terms whether that access includes exports, whether attachments and metadata are included, how long data is retained after downgrade, and how deletion is requested. Those answers determine your exit cost, so record them in the cost model alongside the subscription price.
How to build your own survey tool cost estimate
This sequence turns a vague sense of survey tool cost into a three-year comparison of build, partner and SaaS options, built from your own response volume, feature needs, hosting choices and written partner scope.
Define response volume and edition needs
Start by estimating how many responses you expect per month and per year, how many survey administrators need access, and how many surveys will run in parallel. Your product owner and the research or feedback lead should agree on these numbers, using last year's survey history where it exists. The output is a one-page volume profile that states peak months and the number of concurrent users. You know this step is done when the volume profile is signed off and can be checked against the response limits published on each vendor's pricing page, which you should confirm directly with the vendor because limits change.
Map required features to the licensing boundary
List every feature you need, such as SSO, team roles, audit logs, quota management, whitelabel follow-up emails, and webhooks, then mark each one as included in the open-source Community Edition or reserved for a paid license. For Formbricks, the Community Edition covers unlimited surveys, responses and users with one workspace, while SSO, teams and access roles, audit logs and several other features need an Enterprise license. For LimeSurvey, confirm with the vendor which plugins and capabilities are free and which depend on the edition you choose. Your legal or procurement lead should review the license terms. The output is a feature matrix that marks each requirement as free, paid or unknown, and you are done when every unknown has a named owner for confirmation.
Choose hosting model and data region
Decide where the survey server will run: your own cloud account, a private data center, a provider you contract with, or a managed cloud edition. Record the region requirement that your data protection officer or legal team sets, and note which vendor-hosted regions exist if you consider a managed option. Compare the hosting choice against your existing platform team's skills and on-call coverage. The output is a short hosting decision record naming the location, the operator and the backup location. You are done when the data protection lead has accepted the record and the chosen region is written down for the quote request.
Price infrastructure for the chosen stack
Translate the chosen platform into infrastructure components. LimeSurvey needs a supported PHP version with the required extensions and a supported database such as MySQL, PostgreSQL, MariaDB or MSSQL, so price the application server, database service, storage, backups and monitoring for that stack. Formbricks is typically deployed with Docker or a Helm chart for clusters, so price the container hosting, database, object storage for file uploads and email delivery. Ask your cloud or infrastructure team for a quote based on the sizing from step one, and ask the vendor for the minimum supported versions. The output is a monthly infrastructure line with a separate line for backups and disaster recovery. You are done when each component has a cost source and a named owner.
Cost internal staff hours for operations
Estimate the internal time needed to set up the platform, apply upgrades, manage user accounts, monitor the service, respond to incidents and keep the survey instruments current. Use the upgrade policy of the chosen version to plan recurring upgrade work, and confirm the support window for the version you deploy, since LimeSurvey has ended support for older releases. Include the time of security reviewers and the data protection officer who must approve each survey that collects personal data. Your engineering manager should estimate hours in named roles, not a single headcount figure. The output is a role-by-task staff hours table for the first year and for each following year. You are done when each recurring task appears once and has a responsible role.
Request partner quotes against written fixed scope
Write a fixed-scope brief that lists the platform, edition, features, hosting region, data migration, integrations, testing, documentation and post-go-live support terms, then send the same brief to each candidate partner. Most DeployOpen engagements are fixed-scope and agreed in writing before work starts, and DeployOpen does not publish a price list, so expect a quote that follows from the written scope. Ask each partner to separate one-time implementation fees from recurring support, upgrades and retainer costs, and to state what is excluded. The output is a set of comparable quotes with identical scope definitions. You are done when every quote maps to the same brief and the exclusions are clear enough to compare.
Compare three-year totals across build, partner and SaaS
Build a three-year model with one column each for building in-house, engaging a partner for implementation and support, and using a subscription SaaS edition. Include one-time costs such as setup, migration and testing, and recurring costs such as infrastructure, staff hours, licenses and support. For SaaS, use the published subscription prices on the vendor's pricing page and confirm the response limits and overage terms in writing before you rely on them. Include an illustrative sensitivity row where response volume doubles, because it can move the subscription tier or infrastructure size. The output is a three-year comparison that shows the drivers behind each total. You are done when a second reviewer can trace every line to a named source or quote.
Survey tool cost questions buyers ask before hiring help
Does LimeSurvey or Formbricks cost money to run?
The core software is free to download and self-host. LimeSurvey Community Edition is free to download and self-host, and Formbricks can be self-hosted with Docker without a subscription. The money goes elsewhere: the servers or cloud accounts you run them on, database and backup storage, email delivery, the people who install and maintain the platform, and any paid licence you choose to add. Ask for a quote that separates one-time setup from recurring infrastructure and support, so you can compare it with a SaaS subscription on the same basis. Note that LimeSurvey Cloud and Formbricks Cloud are published subscriptions, and their list prices are the figures a SaaS comparison starts from.
How much effort does a self-hosted survey install take?
The effort depends on the platform, the hosting model and how many integrations and identity connections are in scope. LimeSurvey needs a supported PHP version with mbstring and PDO drivers, plus a supported database such as MySQL, PostgreSQL, MariaDB or MSSQL, so the web stack and database work are the first items to scope. Formbricks can run from Docker images or a Helm chart on a cluster, which shifts effort toward container and cluster operations. Ask the implementer to list the server build, database setup, TLS, backups, email sending and upgrade path as separate line items so you can see where the hours go.
Can an internal team run a survey tool without a partner?
Yes, many teams with a working web and database operations skill set can install and run LimeSurvey or Formbricks alone. The questions to answer honestly are whether someone owns patching, backups, restore testing, access reviews and upgrades on a fixed schedule, and whether that person is available when a survey goes live to a large audience. For example, if LimeSurvey Community Edition 6.17.19 is still in use, it reached end of support on August 31, 2026, so an internal team needs a process that tracks support dates and plans the move to a supported release. Bringing in a partner usually makes sense for the initial build, the hardening and the handover, not for running every day.
How long does setup take and what changes it?
Setup length is driven by scope rather than by the software alone. The main drivers are the number of surveys and form types to migrate, the volume of responses to import, the identity model (local accounts or SSO), the integrations to connect, the hosting region and the testing and sign-off required by your privacy or security team. Ask for a fixed-scope plan with a timeline that lists each deliverable and its acceptance test. DeployOpen agrees scope, deliverables and timelines in writing before work starts, so the quote should state exactly what is included and what is excluded.
What does ongoing support for a self-hosted survey tool require?
Ongoing support covers the work that keeps the platform secure and available after go-live: applying platform and dependency updates, monitoring, backups with tested restores, access reviews, log retention and incident response. These tasks recur for as long as the platform runs, so they belong in a separate line from the one-time build. DeployOpen offers ongoing support, upgrades and continuous testing as retainers. Ask any provider for the response expectations in writing, the upgrade cadence, who is on call, and what happens to the platform if a release reaches end of support.
When does the Formbricks Enterprise license apply?
The Enterprise license applies when you need features that the Community Edition does not include. According to Formbricks license documentation, self-hosted Formbricks needs the Enterprise license for OIDC and SAML SSO, teams and access roles, contact management and segments, quota management, audit logs, whitelabel email follow-ups and removing the Powered by Formbricks badge. The Community Edition is limited to one workspace, and private forks must be released under AGPLv3 unless covered by an Enterprise license. Enterprise code ships in the Docker images and is unlocked with an Enterprise License Key, so confirm the licence terms and renewal cost with Formbricks before you commit to a design that depends on those features.
When does a partner cost less than building alone?
A partner usually costs less when the work is front-loaded and specialized, such as the first hardening pass, the identity integration, the data migration and the evidence pack your privacy or security reviewers request. Building alone costs less when the team already runs similar platforms, the scope is small and the staff time is not otherwise committed. Compare the two on the same basis: internal hours for design, build, testing and documentation, plus the ongoing run cost, against a fixed-scope quote with a clear handover. A useful test is to ask whether the internal team could carry the platform through its first upgrade without outside help.
What to ask for in a partner quote
A partner quote is only comparable to another if both are built from the same written scope, so the first thing to request is a scope that names the platform and edition (LimeSurvey Community Edition, or Formbricks with or without the Enterprise license), the version to be deployed, and the hosting model and region. Ask for each of these to be stated explicitly. For Formbricks, the scope should say whether SSO, teams and access roles, and audit logs are in or out, because those features depend on the Enterprise license rather than on the Docker deployment itself. For LimeSurvey, it should confirm the PHP, database and web server versions the installation will run on, and who provisions them.
The second group of items covers identity, data and operations. The scope should describe the identity integration (which directory or SSO provider, which protocol, and who configures the trust relationship), the data migration of any existing surveys and responses (what is moved, in what format, how it is validated, and who signs off), and the split of backup and upgrade responsibilities between the partner and your team, including restore testing and how security patches are applied between major releases. Ask who owns the infrastructure account, the backup target and the upgrade calendar after handover. Each of these items is a place where unpriced work tends to appear later.
Finally, separate one-time from recurring costs in writing. One-time items usually include design, installation, configuration, integration and migration work, and are normally delivered under the fixed scope agreed before work starts. Recurring items include infrastructure, licenses where applicable, backups, monitoring and support. DeployOpen offers ongoing support, upgrades and continuous testing as retainers, so ask whether support terms after go-live are a separate retainer, what response expectations it sets, and what happens to scope when a new release is published. Confirm these with the partner and your own environment rather than assuming them.
How DeployOpen scopes and prices a survey tool implementation
DeployOpen plans, implements, hardens and documents self-hosted survey platforms inside the client's own cloud accounts, data centers or air-gapped networks. We start from a written scope that shows which costs the client carries directly and which are paid to a partner, so the build, partner or SaaS comparison rests on actual line items rather than list prices.
How we scope
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
- We confirm the platform and edition, expected response volumes, and whether SSO or paid features are needed.
- The written scope lists hosting, integrations, migration, testing and handover so the quote maps to each cost line.
How we build
- We install and configure the chosen survey platform on infrastructure the client controls, including database and backups.
- Integrations with identity, email and analytics tools are built and tested against the agreed data flows.
- Security testing and configuration review run before go-live, and the results are recorded in the handover file.
How we hand over
- We deliver runbooks, configuration records, access model documentation and the cost assumptions behind the scope.
- Staff receive operating guidance so the client can judge which future costs are internal and which need a partner.
- Compliance evidence such as hosting records and retention settings is prepared for the client's own auditors and data protection officers.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after go-live.
- Retainer scope is written separately, so recurring partner fees can be compared with internal staff time.
- Clients confirm with their own legal and privacy teams which obligations apply to their survey data and hosting location.
