A form hosting service does two jobs: it serves the page people fill in, and it stores what they submit. You can rent both from a hosted product, rent only the second half and build the form yourself, or run an open source form builder on your own server and do both. Teams usually start looking at self hosting when a hosted plan caps them at a few hundred submissions a month, or when their data has to stay on infrastructure they control. Self hosting does remove the submission caps and the per-month bill for the software. It replaces them with a server, an upgrade schedule, email delivery, backups and spam handling that someone on the team now owns. This article sets out the three routes, the free plan limits and licenses as published on October 8, 2026, and the costs that usually get left out of the comparison.
Three ways to host a form
Most searches for a form hosting service land on pages that mix these up, so it helps to separate them.
A hosted form builder gives you an editor, a public URL for each form, storage for responses and email notifications. Jotform, Zoho Forms and Formstack are in this group. You do not touch a server. You pay per month, and the plan sets limits on forms, submissions and file storage.
A form backend stores submissions from a form you build yourself. You write the HTML on your own site and point the form's action at the service's endpoint. Formspree is the best known example. This suits developers who want full control of the markup without running a database.
A self hosted open source builder is software you install on your own server or cloud account. You get the editor and the storage, with no vendor limit on submissions, but the server, the updates and the email sending are your responsibility. OpnForm, Formbricks, HeyForm, LimeSurvey and Form.io are the names that come up most.
The right route depends less on features than on who will be on call when the form stops sending notification emails at 9 p.m. before a deadline.
What the free hosted plans actually allow
The usual trigger for looking at open source is a free plan limit. These are the numbers the vendors publish on their own pricing pages as of October 8, 2026.
| Service | Type | Free plan forms | Free plan submissions | Notes |
|---|---|---|---|---|
| Jotform | Hosted builder | 5 active forms | 100 per month | 500 submissions stored in total, 100 MB of uploads |
| Formspree | Form backend | Unlimited | 50 per month | Paid plans add more submissions per month |
The Jotform free plan is generous for one or two forms with light traffic. A recruitment form that receives 150 applications in the week a job is posted will hit the monthly limit, and the total storage cap of 500 submissions means old responses have to be deleted or exported to keep collecting.
Formspree's free plan allows unlimited forms but 50 submissions a month, which fits a contact form on a small site. Its paid tiers raise the monthly submission count in steps: Formspree's plan page lists 200, 2,000 and 20,000 submissions a month on its Personal, Professional and Business plans.
The pattern is the same across hosted tools: pricing follows submissions or forms. That is the part self hosting removes. It is worth being clear that this is also the part the vendor uses to pay for servers, spam filtering and email delivery, so the cost does not vanish. It moves to you.
The open source options and their licenses
"Open source" covers very different licenses here, and the license decides what you may do with the code, especially if you plan to offer forms to clients or embed the builder inside your own product. These are the licenses shown in each project's repository on October 8, 2026.
| Project | Best known for | License of the core code | Stack noted in the README |
|---|---|---|---|
| OpnForm | Classic forms, Typeform style editor | AGPLv3, with a separate license for an Enterprise folder | Docker, PostgreSQL or MySQL |
| Formbricks | In-product and link surveys | AGPLv3, with a separate license for enterprise modules and MIT for its SDKs | Docker, PostgreSQL |
| HeyForm | Conversational forms | AGPLv3 | See project docs |
| LimeSurvey | Research-grade surveys | GPL version 2 or later | PHP with MySQL or PostgreSQL |
| Typebot | Chat style forms and bots | Functional Source License 1.1, Apache 2.0 future license | See project docs |
| Form.io | Developer platform, JSON forms | Open Software License 3.0 for the core server | See project docs |
Why the license matters for a form tool
AGPLv3 requires that if you modify the software and let people use it over a network, you make your modified source available to those users. For a team that installs OpnForm or Formbricks unchanged for internal use, this rarely matters. For an agency that adapts the code and hosts forms for clients, it does.
Several projects split their code: the core is AGPL, while features such as single sign-on, team roles or white labeling sit in a folder under a commercial license. Read which folder the feature you need lives in before you plan around it. A self hosted install that turns out to need a paid license key for the one feature you wanted is a common surprise.
Typebot's Functional Source License is not an open source license in the OSI sense. It allows most uses but restricts offering the software as a competing service, and each version converts to Apache 2.0 after a set period. LimeSurvey's GPL is the most permissive for internal use and has the longest history, with copyright dating from 2003.
What self hosting really costs
The software is free. Running it is not. When teams compare a hosted plan against self hosting, the hosted price is a number on a page and the self hosted cost is usually written as "a small server". That leaves out most of the work.
The server is the cheap part
A small virtual machine is enough for most form builders at low volume. The cost that grows is the database: it needs backups that are tested, not just scheduled, and enough disk for uploaded files. If respondents attach CVs, photos or PDFs, storage grows faster than the database does, and you will need object storage and a policy for how long files are kept.
Email delivery is the part that breaks quietly
Every form tool sends email: confirmations to respondents, notifications to the team. On a self hosted install you configure an outgoing mail service yourself, set up SPF, DKIM and DMARC records for the sending domain, and watch for bounces. When this is misconfigured, nothing visibly fails. Confirmations land in spam, notifications stop arriving, and the first sign is an applicant asking why nobody replied.
Spam and abuse
Public forms attract bots. Hosted services run spam filtering as part of the product. On your own install you add a CAPTCHA, rate limits and honeypot fields, and you keep them working as bots adapt. A form that receives 2,000 spam submissions overnight also fills your database and your notification channel.
Updates and security
A form builder is a public web application that accepts input from anyone. Security updates have to be applied promptly, which means someone reads the release notes, tests the upgrade on a copy and rolls it out. Projects that release often, which most of these do, judging by commits pushed in the past week, need this attention regularly. Skipping updates is how a self hosted form becomes the weakest point on your network.
Who is on call
Add up the hours. Initial setup, mail configuration, a monthly upgrade, restoring a backup once to prove it works, and handling the occasional incident. For a developer that may be a day to set up and a few hours a month after that. Multiply by the hourly cost of that person and compare it with the hosted plan. Self hosting wins clearly when volume is high, when data residency rules require it, or when the team already runs similar services. It rarely wins for a single contact form.
Data residency and privacy
A real reason to self host is control over where data is stored. Some organizations must keep personal data in a specific country, or cannot send applicant data to a third-party processor without a lengthy review. Running the form builder on your own infrastructure answers the question "where is the data" in one line.
Hosted services can also meet these needs, but you have to check. Look for the region where submissions and uploaded files are stored, whether you can choose it, whether a data processing agreement is offered, and how long data is kept after you delete it or close the account. Some hosted form tools store data in a fixed region and say so in their FAQ; others let enterprise customers pick. If a vendor's documentation does not answer these points, ask in writing before you collect anything sensitive.
Self hosting does not make the privacy work disappear either. Access control, retention, deletion requests and breach response become your processes rather than the vendor's.
The part neither route solves on its own: handling responses
Whichever way the form is hosted, the work that takes most of a team's time starts after the submission arrives. Someone has to read it, decide who owns it, reply, and record that the reply happened.
Most open source builders and most hosted builders treat that step as an export. Responses go to a results table, a spreadsheet or a webhook, and the team tracks ownership and status in another tool. The predictable failures follow: two people reply to the same applicant, or nobody replies because each assumed someone else had it.
When you evaluate options, check what happens to a single response after it arrives:
- Can each response have an owner and a status?
- Is there a history of who changed what and when?
- Can you send a reply from the same screen, and is the sent email recorded against the response?
- Can you email a group of respondents at once with their names merged in?
If the answers are no, budget for the separate tracking process or for a form tool with response management, which keeps the owner, status and replies on each response. Examples of how that plays out in applications, inquiries and events are on the use cases page.
How to decide
Stay on a hosted free plan if you have one or two forms and stay under the monthly submission cap. It is the lowest effort option.
Use a form backend if a developer controls the site's HTML and the main need is storing submissions and getting notified.
Self host an open source builder if submission volume makes per-response pricing expensive, data must stay on your infrastructure, and someone on the team will own the server, email delivery and upgrades as an ongoing job. Read the license against your intended use first.
Pick a hosted tool priced by seats rather than submissions if the cap is what pushed you toward self hosting but nobody wants to run a server. Some tools offer unlimited forms and responses on every plan, which removes the main reason to self host. Compare on the pricing page what a team of your size would pay against the hours a self hosted setup takes.
What to change first
Count last month's submissions and the hours your team spent moving them into a spreadsheet and chasing replies. If the submission cap is the problem, a seat-priced tool such as Halict or a self hosted builder both fix it; if the hours are the problem, choose whichever option keeps the owner and the reply on each response.
Q1. What is a form hosting service?
It is a service that publishes your form on a web address and stores the submissions, usually with email notifications and an export. Hosted builders such as Jotform provide the editor too, while form backends such as Formspree only store submissions from a form you write yourself.
Q2. Is there a free form hosting service with unlimited submissions?
Among the services checked in October 2026, Jotform's free plan allows 100 submissions a month and Formspree's free plan allows 50. Unlimited submissions usually come from self hosting an open source builder or from tools that price by number of users instead of responses.
Q3. Is it legal to use an AGPL form builder for my company?
Using an unmodified AGPL builder internally is generally straightforward. If you modify it and let others use it over a network, the license requires you to offer them your modified source. For client work or embedding in a product, have the license reviewed.
Q4. What is the hardest part of self hosting a form builder?
Usually email delivery and maintenance rather than installation. Confirmations and notifications need a properly configured sending domain, and the application needs regular security updates and tested backups. Plan for ongoing hours each month, not just a setup day.
Q5. Can I move my existing forms to a self hosted tool?
Most open source builders do not import forms from hosted services directly. Expect to rebuild the questions and export old responses as CSV to keep as an archive. Check whether the new tool can import CSV if you want past responses in the same place.