Which form builder fits your situation: Jotform or self-hosted Formbricks
Choose Jotform if your forms take payments, produce PDFs, or feed a custom app you want to build quickly from templates. Choose self-hosted Formbricks if your forms are mainly surveys and feedback, you need unlimited responses without a plan cap, and you want responses and uploaded files kept on servers your organization controls. Most renewal and cap decisions turn on which of these two groups of work dominates, so start there rather than with the price page. Jotform fits teams that rely on its built-in payment collection, PDF output, app building and template library. Those features are part of the product's core workflow, so replacing them means choosing and integrating other tools. Jotform's plan limits on active forms, monthly submissions, form views and storage also matter here, because a team with many small forms or heavy file uploads may hit them sooner than expected. Confirm the current limits and the HIPAA tier on Jotform's own pricing page before you build a comparison, since those figures change. Self-hosted Formbricks fits survey, feedback and in-product research work. The Community Edition includes unlimited surveys, responses and users, full API access, webhooks, multi-language surveys and file upload, and it runs in your own infrastructure with Docker. Two questions decide the fit: who will run and patch the server, and which features you need from the Enterprise license, such as SSO, teams and access roles, or audit logs. Ask an internal platform team or a partner to confirm who owns uptime, backups and upgrades before you commit.
Which option fits which scenario
This table maps common Jotform use cases to the option that usually fits better, Formbricks or another tool, and gives the reason tied to Community Edition limits and missing features. Read each row against your own form inventory, since a single organization often needs both tools.
| Scenario | Better fit | Reason |
|---|---|---|
| Customer feedback surveys on a website or in an app | Formbricks | Community Edition includes website, app and link surveys, advanced logic and multi-language surveys with no response cap, so volume does not change the license cost. |
| Intake forms with file uploads | Formbricks, after a test | File upload is included in the Community Edition. Confirm file size limits, storage location and retention in your own instance before rebuilding intake forms. |
| Forms that take payments | Jotform, or a separate payment tool | Formbricks does not cover payment collection. Keep payment steps in a payment provider and send only non-card context to Formbricks. |
| Forms that generate PDFs | Jotform, or a document tool fed by webhooks | Formbricks does not produce PDF output on its own. Route submissions through webhooks to a document generation service you run. |
| Website embeds in several languages | Formbricks | Multi-language surveys and UI are part of the Community Edition. Check each translated survey during rebuild, since translation is still a manual review step. |
| Forms that feed an internal system through the API | Formbricks | Full API access and webhooks are included in the Community Edition, with no form or submission caps. Confirm the payload fields and retry behavior with your integration team. |
| Single team with one shared workspace | Formbricks | One workspace is included in the Community Edition. Multiple business units that need separate workspaces will need the Enterprise license, so confirm scope first. |
| Forms needing app-building or workflow features | Jotform, or a workflow platform | Jotform's app-building features are outside Formbricks' scope. Keep those forms where they are and use Formbricks for survey and feedback work. |
Where responses and uploaded files live
Forms become a data question as soon as respondents enter personal details or upload files. The four areas below decide where those responses sit, who operates the system, how staff sign in, and what evidence an auditor will ask for.
Data location of responses
Jotform stores responses and uploaded files on its own hosted infrastructure, so your data residency depends on the Jotform account terms you accept. With self-hosted Formbricks, responses and uploads are written to the database and file storage you provision in your own cloud account or data center. Ask Jotform directly which regions and data centers apply to your plan, and document where each form's submissions and attachments are stored before you migrate.
Hosting model and operations
A self-hosted Formbricks instance runs as containers that your team or implementation partner deploys, patches and backs up. Formbricks can be self-hosted with Docker without a subscription, and the Community Edition is the core of that deployment. You take on uptime, upgrades, TLS certificates, database backups and restore tests, which Jotform currently carries for you. Price these operating tasks as part of the total cost, not only the license line.
Identity and single sign-on
Formbricks Community Edition does not include OIDC or SAML single sign-on. Those, along with teams and access roles, require the Enterprise license. If your staff must sign in to form builders through your identity provider, plan for that license key before go-live. Confirm how Jotform handles SSO and role separation on the plan you use, and list which staff roles can edit forms, export responses and view uploaded files.
Licensing and enterprise module
The Formbricks core is licensed under AGPLv3, while code in its enterprise module carries a separate Enterprise license. The enterprise code ships in the Docker images and is unlocked with an Enterprise License Key. If you modify and host Formbricks privately, the AGPLv3 terms on your changes apply unless an Enterprise license covers them. Have counsel review the license terms against your planned customizations before you build on the platform.
Compliance evidence and HIPAA terms
Self-hosting moves control evidence into your hands. DeployOpen can prepare configurations, access records, backup procedures and logging for your assessment, but independent auditors and certification bodies issue any audit report or attestation. Jotform's HIPAA capability and data residency terms vary by plan, so confirm them in writing with Jotform before comparing. Ask Jotform for its current documentation and sign any business associate terms they offer, then compare that record with what your own instance would produce.
How Formbricks licensing affects what you can run
The first licensing question for a Jotform replacement is which code you are running. The Formbricks core application is licensed under AGPLv3, so you can self-host it, modify it and use it inside your organization without a subscription. Code in the enterprise module sits under a separate Enterprise license and is unlocked with an Enterprise License Key. That enterprise code ships in the same Docker images as the core, so the image you pull is not the same as the features you are entitled to use. Confirm which features your key unlocks before you plan the rollout, rather than assuming the image contains everything you need to run.
The Community Edition is generous on volume: the facts supplied for this page list unlimited surveys, responses and users, full API access and webhooks. Its hard boundary is the single workspace. If your forms need to be split across several business units with separate administration, that is a licensing decision, not a configuration one. Check the license documentation for the current feature list before you commit, and ask whether a separate Formbricks instance per unit would meet your separation needs without adding administration you did not plan for.
Before you build a customized fork, read the copyleft rule. A privately kept fork must be released under AGPLv3 unless an Enterprise license covers it. If your team plans to change the form engine, add a proprietary integration or patch the interface for internal users only, decide early whether that code can stay private. Then match your feature list against the license documentation: OIDC or SAML SSO, teams and access roles, audit logs and removing the Powered by Formbricks badge all sit behind the Enterprise license. Ask the vendor to confirm the current terms in writing, and have your legal or procurement team review them against your intended use.
What each option costs to run
Jotform is a hosted subscription, so the organization pays a recurring fee that scales with how the account is used. The main meters are the number of active forms, monthly submissions, form views and storage for uploaded files and submission data. Costs can also rise through add-ons, such as features that sit in higher tiers or extra capacity you buy when a meter is exceeded. Because the meters interact, a form that is cheap at pilot volume can change tier once it is embedded on a busy website or once attachments accumulate.
- Recurring fee: The plan is billed on a schedule, so the cost repeats for as long as the account is open.
- Active forms: Every form kept live counts toward the plan limit, so form sprawl across departments adds cost.
- Submissions and views: Traffic growth from a public embed can push the account into a higher tier even when the number of forms stays flat.
- Storage and add-ons: Uploaded files and extra capacity or features are often priced separately from the base plan.
- Quote question: Ask which tier each of your current meters falls into today and what the next tier costs at your projected volume.
Check the current plan limits and add-on pricing on the vendor's own pricing page at the time of your decision, since those terms change.
Self-hosted Formbricks has no per-form or per-submission subscription. The recurring costs are the compute, storage and network capacity in your own cloud account or data center, plus the database and backups that hold responses and uploaded files. These costs scale with the size of the deployment and the retention period you choose, not with a vendor meter. The Community Edition supports unlimited surveys, responses and users, so the main planning question is how much capacity your traffic and file uploads require.
- Compute and storage: Application servers, a database host and disk for uploads are billed by your cloud provider or charged against existing hardware.
- Database and backup: Responses and metadata need a database with its own backup schedule, replication and tested restores.
- Network and TLS: Public access, certificates and load balancing add modest but recurring charges depending on hosting model.
- Cluster option: A Helm chart supports cluster hosting, which raises platform costs and skills requirements but adds resilience.
- Quote question: Ask the implementation partner to size the server, database and backup tiers from your expected submission volume and file sizes, and to state which items are one-time setup and which recur monthly.
Ask your cloud or infrastructure team to confirm current instance and storage rates in your own account.
The Enterprise license is optional. The Community Edition runs without a subscription, but some features sit behind an Enterprise License Key, including OIDC and SAML SSO, teams and access roles, contact management and segments, quota management, audit logs, whitelabel email follow-ups and removal of the Powered by Formbricks badge. If your identity, audit or branding requirements depend on those features, the license becomes a recurring line item that must be priced separately from infrastructure. Organizations that only need the core survey and form functions may not need it at all.
- Feature-driven need: The license is required only for the gated features your governance demands, such as SSO or audit logs.
- Recurring or fixed terms: Confirm whether the license is billed annually, per instance or per seat, and whether renewal is required to keep upgrades.
- Workspace limit: The Community Edition is limited to one workspace, so multi-department separation may require the license.
- Fork rule: Privately kept forks must be released under AGPLv3 unless covered by an Enterprise license.
- Quote question: Ask the vendor to list which gated features are included, the license term, and what happens to the instance if the license lapses.
Check the current Enterprise terms in the Formbricks license documentation before budgeting.
Most of the one-time effort goes into rebuilding forms, conditional logic, hidden fields, file upload handling and integrations such as webhooks and the tools Formbricks connects to. Ongoing effort covers operating the instance: applying upgrades, monitoring, patching the host, testing restores and handling access requests. A hosted subscription absorbs much of this work, so the trade-off is internal or contracted labor against a recurring vendor fee. The size of that effort depends mostly on the number of forms to rebuild and how many systems consume the responses.
- One-time rebuild: Each active form, its logic and its embeds need to be recreated and tested before the Jotform account is closed.
- Upgrades: Formbricks publishes releases such as 6.0.2, published on October 1, 2026, and each upgrade needs staging tests and a rollback plan.
- Operations: Monitoring, patching, certificate renewal and backup verification recur for the life of the instance.
- Integrations: Webhook consumers and downstream systems need owners who can respond when payloads change.
- Quote question: Ask for the effort split between one-time migration and recurring operations, the named roles doing each part, and whether ongoing support is a fixed-scope retainer.
Confirm internal staffing capacity before comparing these costs with the subscription.
What moving from Jotform to Formbricks involves
The sequence turns a Jotform estate into a self-hosted Formbricks instance with the forms rebuilt, past responses and files preserved, and website embeds switched over. Each step ends with a check you can confirm before the next one starts.
Inventory active forms and integrations
List every Jotform form that still receives submissions, along with its embeds on websites and apps, the integrations that receive its data, and the owner of each form. Mark which forms are surveys with rating or matrix questions, which collect payments, and which generate PDFs, because those need different handling. The output is a register that shows which forms move, which retire and which need a replacement tool. Confirm the register with each form owner before you rebuild anything.
Rebuild conditional logic and hidden fields
For each retained form, recreate the question flow, conditional branching, validation rules and hidden fields in Formbricks, and test each branch with sample responses. Hidden fields usually carry campaign, referral or record identifiers, so confirm where each value comes from and how it arrives in the new survey. Some Jotform layouts will not map one to one, so note any question that needs a different structure. The check is a test log that shows every path reaches the expected end state.
Export past submissions and uploaded files
Export historical submissions from Jotform in a format you can store and query, and download uploaded files with their links to the matching submissions. Decide how past data will be used, whether it moves into Formbricks as a reference archive or stays in a read-only store on your own servers. Keep the mapping between submission IDs and files so an auditor or record owner can trace any response. The output is a verified archive with a count of exported records that matches the Jotform export.
Replace payment and PDF steps with other tools
Formbricks does not cover payment collection or PDF document generation, so identify the tool that will take over each of those jobs before cutover. Payment flows need a processor that your finance team has approved, and PDF output needs a document generator or a template in your existing systems. Confirm data handling for any payment or personal data routed through these tools. The check is a signed-off replacement for every form that depended on a Jotform payment or PDF step.
Set up the self-hosted Formbricks instance
Deploy Formbricks in your own infrastructure with Docker or the Helm chart, and connect it to your database, storage, email and identity settings. Decide early whether you need the Enterprise license for SSO, team roles, audit logs or whitelabel email, because those features are not in the Community Edition. Configure backups and access controls before any real data arrives. The output is a running instance with documented settings, tested backups and a list of admin accounts that matches your access policy.
Test forms, webhooks and downstream integrations
Run each rebuilt form through a test pass that covers devices, languages, file uploads and error handling. Send test submissions through each webhook, automation tool or connector that Jotform fed, and confirm the receiving systems parse the new payload. Check that response data lands where your reporting expects it. The check is a sign-off from each form owner and each system owner that their test cases pass.
Swap website embeds and cut over
Replace each Jotform embed on websites and apps with the matching Formbricks survey or link, and update any links in emails, documents and QR codes. Plan the switch for a window when submission volume is low, and keep the Jotform form open in read-only mode until the new flow has run without errors. Record the date of each swap so responses can be traced to the right system. The output is a cutover log, a list of retired Jotform forms and a confirmed record that new responses arrive in Formbricks.
Questions buyers ask before switching from Jotform
What does switching from Jotform to self-hosted Formbricks cost?
The software itself has no license fee in the Community Edition, so the cost is made of components: server and storage, the staff time to rebuild forms, the migration of past submissions and uploaded files, and ongoing administration. Hosting costs recur every month and depend on your cloud or data center prices, traffic and how much file storage you keep. Rebuilding forms is mostly one-time work, but it grows with the number of active forms and the logic in each. Ask any implementation partner for a quote built from a written scope, and ask them to separate one-time migration work from recurring operations. DeployOpen does not publish a price list, and a quote follows from the agreed scope.
How long does a Jotform to Formbricks migration take?
The duration depends on the number of forms you keep, how complex their conditional logic and hidden fields are, how much past submission data and how many uploaded files must move, and how many embeds sit on live websites. Forms with payment steps or PDF generation add work because those features are not part of Formbricks and need replacement tools. Your own review of the forms inventory is the most useful input for an estimate. Ask the partner to state the timeline in the written scope, along with the milestones at which you approve each batch of forms before the old ones are retired.
What must our team provide before a migration starts?
Three inputs matter most. First, a named business owner for each form who can approve the rebuilt version and confirm its questions and consent wording. Second, a complete inventory of active forms, including which ones are embedded on websites, which send notifications, and which hold personal data. Third, access to the server or cloud account where Formbricks will run, along with a database and storage plan that your infrastructure team approves. Without these inputs, scope tends to grow during the work. Confirm the exact access model, approval steps and data handling rules with your team before the scope is signed.
Can our own team switch from Jotform without an outside partner?
Yes, a team with container and database skills can install Formbricks with Docker and rebuild forms in its interface. The harder parts are the ones that need careful planning: translating logic and hidden fields accurately, moving file uploads and past submissions without loss, running backups, applying security hardening, and handling embeds on live sites. Teams that do this alone often keep Jotform running in parallel until every form is verified. An outside partner can take on any of these parts under a fixed-scope agreement, while your staff keep ownership of the forms and data.
Does Formbricks replace Jotform payments and PDF generation?
No. Formbricks is a survey and form product, and its supplied feature set covers surveys, logic, file upload, multi-language forms, webhooks and the API. It does not cover the payment collection or PDF generation features that Jotform offers in its form builder. For those workflows, plan a separate tool for payments, a document generation step, and a webhook or workflow that connects Formbricks responses to them. Confirm each of these requirements in writing during scoping, because a missed payment or PDF step is one of the most common causes of delays in a switch.
What does the Formbricks Community Edition limit mean for our workspaces?
The Community Edition is limited to one workspace. It has no limit on surveys, responses or users, and it includes full API access and webhooks. If your organization needs separate workspaces for different business units, you need to decide whether one workspace with clear naming and access practices is enough, or whether the Enterprise license is needed for the setup. Formbricks documents that the Enterprise license covers OIDC and SAML SSO, teams and access roles, audit logs and whitelabel follow-ups. Confirm the license terms with Formbricks and your legal team before you design the structure.
Which parts of Formbricks need the Enterprise license?
The Enterprise license is needed for OIDC and SAML single sign-on, teams and access roles, contact management and segments, quota management, audit logs, whitelabel email follow-ups and removing the Powered by Formbricks badge. The enterprise code ships in the Docker images and is unlocked with an Enterprise License Key, while the core application is under AGPLv3. Ask your compliance and legal teams whether single sign-on and audit logs are required for your forms before you decide on the license. The Formbricks license documentation sets out the current terms.
Who keeps responsibility for backups and uptime after the switch?
After the switch, your organization or its chosen operator owns the server, database, file storage, backups, patching and monitoring of Formbricks. Forms that collect personal or regulated data also need access reviews and an agreed retention policy for responses and uploaded files. Jotform handled this infrastructure for you, so this responsibility is new. Ask the partner to describe backup scope, restore testing, upgrade windows and support hours in the written scope, and agree who receives alerts when a form or the server fails.
What stays the same and what changes for your team
Form owners will edit in a different builder, and the embed code on your website changes. Forms are rebuilt in Formbricks surveys rather than moved across, so each owner needs time in the editor to recreate logic, hidden fields and multi-language versions. Every Jotform embed, iframe or link on a web page or in an internal tool has to be swapped for the Formbricks equivalent, and the old Jotform links should stay live until traffic has moved. Respondents still fill in a link or an embedded survey, but the look, the notification routes and the place where responses land all change. Confirm with the Formbricks documentation which survey types your team actually uses (link, website, app or email) before you plan the cutover.
IT operators take on hosting, access control and backups, which Jotform previously handled. Once Formbricks runs in your infrastructure, your team owns the container deployment, database, file storage for uploads, TLS certificates, upgrades and the backup schedule for responses and attachments. Decide who can see submissions by mapping Jotform's sharing settings to Formbricks roles, and note that teams and access roles sit behind the Enterprise license, so the Community Edition's single workspace shapes who can separate data between departments. Compliance leads should ask for written evidence of who can export responses, how file uploads are encrypted at rest, and where backup copies are kept, then check those answers against your own environment rather than assumptions.
Staff training and form rebuilding are the main effort, and payment, PDF and app-building workflows need other tools. Budget time for form owners to learn the new editor, for reviewers to learn where notifications arrive, and for someone to test every workflow end to end. Jotform's payment collection, PDF generation and app-building features have no direct equivalent in Formbricks, so any form that feeds a payment, a generated document or a mobile app needs a separate service, and that integration is a scoped piece of work with its own owner. Ask your implementation partner to list these dependencies in the written scope before anyone rebuilds a form.
How DeployOpen helps you evaluate and move to Formbricks
DeployOpen starts by mapping your active Jotform forms, their logic, hidden fields, file uploads and integrations against what self-hosted Formbricks covers. We then build, test and hand over the Formbricks instance inside your own infrastructure, with the gaps you agreed to handled in writing.
How we scope
- We inventory which Jotform forms are active, which carry conditional logic, and which collect file uploads.
- The written scope lists which forms move to Formbricks, which stay on Jotform, and which need another tool.
- Payment, PDF and app-building needs are recorded as separate items with named replacement options to confirm.
How we build
- We deploy Formbricks with Docker in your cloud account, data center or air-gapped network, as agreed in scope.
- We rebuild logic, hidden fields and multi-language forms, then test each form against its Jotform original.
- We configure webhooks and API access for the systems that receive submissions, and test file upload storage paths.
How we hand over
- We document the deployment, form inventory, field mapping and the decisions taken for each unmigrated feature.
- We plan the swap of embeds on your website and the export of past Jotform submissions and uploaded files.
- Your team receives the runbooks, backup procedures and access records needed to operate the instance after handover.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after the fixed-scope engagement ends.
- We can review the Formbricks Enterprise license need against your SSO, access role and audit log requirements.
- Quotes follow from the written scope, so ask for line items covering build, data migration, testing and handover.
