Online form builder software source code
A form builder script is a ready-built, self-hosted alternative to Typeform, Jotform or Google Forms — sold once as source code — that lets you or your customers assemble forms by dragging fields, publish them anywhere, and keep every submission in a database you control.
Written by ZoopCoder, who build and sell one of the packages described below — that bias is declared in full further down this page.
Quick answers
How much does a form builder script cost?
About $30 to $250 for an off-the-shelf licence, against $12 to $99 per month forever for a hosted service. The break-even against a mid-tier Typeform or Jotform plan usually arrives within the first year.
Why self-host a form builder instead of using Typeform?
Data residency and cost. Submissions stay in your own database, which matters for health, financial, legal and government data, and there is no per-response ceiling to hit at the worst possible moment during a campaign.
What is the hardest feature to get right in a form builder?
Conditional logic. Show, hide, skip, require and calculate rules that hold up when fields are reordered or deleted are the thing cheap scripts fake — they let you set a rule in the builder and then never evaluate it server-side.
The one decision that matters: internal tool or multi-tenant product
Decide who builds the forms. If it is only your team, a single-workspace form builder is fine and the interesting features are logic and integrations. If you intend to sell workspaces to other people, you need per-tenant isolation, plan limits, branding removal as a paid feature and subscription billing — a fundamentally different codebase sold at a similar price.
| Model | Who uses it | Money flow | Where it breaks |
|---|---|---|---|
| Internal / single workspace | Your own team | None — it replaces a subscription | Cannot be sold on without a rewrite |
| Multi-tenant SaaS | Customers who sign up themselves | Monthly per workspace, tiered by forms, submissions and storage | Enforcing plan limits and quota accounting on the public submit endpoint |
| Embedded in your own app | Your users, inside your product | Part of your existing pricing | Needs a real API and an embeddable renderer, not just an iframe |
A quick test on any demo: set a plan limit of five submissions, then post a sixth submission straight to the form’s public endpoint with curl rather than through the browser. If it is accepted, the limit lives in the front end and your pricing tiers are decorative.
What a complete form builder must include
Drag-and-drop is table stakes and demos beautifully. These are the pieces that decide whether real forms survive contact with real users.
- A full field set: text, email, phone, number, date, dropdown, radio, checkbox, rating, signature, address, file upload and hidden fields
- Conditional logic evaluated on the server as well as in the browser — show, hide, skip-to, require and calculated fields
- Multi-page forms with a progress indicator, plus save-and-resume via a resumable link
- Validation that is defined once and enforced on both sides, including custom patterns and cross-field rules
- Spam defence that works without a third-party dependency: honeypot, timing check, per-IP rate limit, optional captcha
- Submission management: list, filter, search, view a single response, add internal notes, mark status, and export to CSV
- Notifications both ways — alert your team, and send the respondent a confirmation with their own answers
- Webhooks and an API on submission, so forms can feed a CRM, a sheet or a workflow tool
- File uploads with type and size limits, stored outside the web root, and a storage quota per workspace
- Embedding that actually works: inline script, iframe, popup and full-page link, with the iframe auto-resizing to content
What a form builder costs, self-hosted versus rented
This is the clearest cost comparison of any category on this site, because the hosted competitors publish their prices and meter the one thing you cannot predict: how many responses you get.
| Route | Typical cost | What you get | Limits |
|---|---|---|---|
| Marketplace script (regular licence) | $29–$69 | Builder and submissions; logic often front-end only | Single workspace; resale not permitted |
| Open source (Formbricks, OpnForm, Ohmyform) | Free | Genuinely capable builders; active projects | Multi-tenant billing is yours to add |
| Direct vendor, multi-tenant platform | $99–$249 | Tenant isolation, plan limits and billing included | Your server, your responsibility |
| Hosted (Typeform, Jotform, Formstack) | $25–$99+ per month | Nothing to run | Metered responses, storage caps, per-seat pricing |
The arithmetic: a $39/month hosted plan is $468 a year and rises with response volume, so a $149 licence on a $6 VPS pays for itself in about five months and then keeps paying. The costs on the self-hosted side are real but small: storage for uploads, outbound email deliverability — use a proper sending service, because form notifications landing in spam is the most common self-hosted failure — and the engineering time to keep it patched. The hosted case is strongest when the response volume is low and predictable; the self-hosted case is strongest when it spikes, when the data is sensitive, or when you want to resell it.
Where to buy, and what each source is good for
| Source | Best for | Watch out for |
|---|---|---|
| Open source (Formbricks, OpnForm) | Internal use where you have engineers | No billing layer — fine for internal, a project for a SaaS |
| WordPress plugins (Gravity Forms, WPForms) | Sites already on WordPress | Annual renewals; add-ons priced separately; tied to WordPress forever |
| General code marketplaces | Cheap single-workspace builders | Conditional logic that never runs server-side; plan limits that a curl request walks straight past |
| Direct from the developer | Launching a form SaaS with tenant billing already correct | Ask how quota is counted on the public submit endpoint, and test a file upload at the size limit |
Declared bias: what we sell
We are ZoopCoder. We build and sell FormCraftPro — a multi-tenant form-builder platform with drag-and-drop building, conditional logic, file uploads, payment fields, submission management and per-workspace plan limits — as source code from $149, with no recurring fee to us. So read this page knowing we are a vendor in the category we just described. Everything above is what we would check if we were buying rather than selling, including the parts that do not favour us: if your requirements are genuinely unusual a custom build beats every package here, and if you want zero operational responsibility a hosted service is simpler than any source code.
If you want a working example to measure against
The FormCraftPro demo runs the full stack, so you can use it as a yardstick for anything else you are evaluating — including the tests described on this page.
If you are comparing against hosted tools
The economics flip based on scale and headcount. These pages lay out the arithmetic against the hosted platforms most buyers weigh up.
Frequently asked questions
What is the best self-hosted alternative to Typeform?
Among free options, Formbricks and OpnForm are the most capable and both are actively maintained, giving you a modern builder with logic and integrations at no licence cost. Commercial source code is worth paying for when you need multi-tenant workspaces with plan limits and billing, because that layer is exactly what the open-source projects leave to you and it is the largest single piece of work in the category.
Can I sell forms as a service with a form builder script?
Only if the codebase is multi-tenant and the licence permits resale. You need per-workspace data isolation, quota enforcement on the public submission endpoint rather than in the UI, branding removal as a paid feature, and subscription billing with trials. Most inexpensive marketplace scripts are single-workspace and their regular licence forbids running the software as a service.
How do I stop spam on a self-hosted form?
Layer cheap defences before reaching for a captcha, because captchas cost you real submissions. A honeypot field that bots fill and humans never see, a minimum time-to-submit that rejects instant posts, and a per-IP rate limit will remove the large majority of automated spam. Add a captcha only on the forms that still get through, and always validate server-side.
Where are form submissions stored if I self-host?
In your own database on your own server, which is the main reason to self-host at all. That matters when submissions contain health, financial, legal or government data subject to residency rules, and it means no third party can meter, cap or lose access to your responses. It also makes you responsible for backups and encryption, so plan both before the first real form goes live.
Do form builder scripts support payments?
Better ones do, usually via a payment field that computes a total from the answers and sends the respondent to a gateway before the submission is recorded. Test the failure path specifically: if the payment fails or the respondent abandons the gateway, a well-built form keeps the submission as pending rather than either losing it or marking it paid. That behaviour is where most implementations fall down.
Is conditional logic hard to implement in forms?
It is the hardest part of the category, and the usual place a cheap script is exposed. Rules have to survive fields being renamed, reordered or deleted, they have to be evaluated on the server so a respondent cannot bypass a required field, and calculated fields have to recompute in the right order. Test it by setting a rule, deleting the field it depends on, and seeing whether the builder warns you or silently breaks the form.
Get a quote or a guided demo
Tell us your use case and we'll send pricing, a live demo walkthrough and licensing options for Online form builder software source code. Usually a reply within one business day (IST).