Forms and surveys decision
Wufoo
A competent engineer can build a useful subset (form builder, hosting, payments, API) in about a week and low ongoing maintenance, but Wufoo's audited hosting, large user base, polished UX and integrations are durable advantages that are costly to match — so building is realistic for focused needs but not a full replacement of the paid product.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Create form schema -> render public form -> accept submissions (including file uploads & payments) -> store entries in DB -> provide basic reporting and an API/webhooks for entries.
What it still won’t have
- SOC 2 / audited data center hosting and related compliance guarantees
- Enterprise-grade reliability, scaling, and SLA-backed support
- Large template/gallery catalog and polished drag-and-drop UX
- Built-in integrations catalogue and Zapier breadth
- Priority customer support and account management
What remains hard
- Compliance and regulation
Wufoo’s servers live in a SOC 2, Type II audited data center in the United States with industry-leading security measures in place.
- Brand trust
Trusted by 3+ million users and some of the world's most popular brands.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted lightweight form-builder using React for the editor and renderer, Postgres for form schemas and entries, S3-compatible storage for uploads, and a Node.js + Express backend. Include: drag-and-drop form schema editor, public form rendering with client and server validation, file upload handling (S3), Stripe payment field integration, REST API endpoints to list forms and fetch entries, webhooks on submission, basic reports CSV export, account-level quotas, error handling, and unit/integration tests. Out of scope: WYSIWYG theme gallery, enterprise SSO, SOC 2 certification, and an app-store of integrations.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productWufoo homepage
- official pricingWufoo pricing
- official docsWufoo features
- open sourceLimeSurvey/LimeSurvey
- open sourceheyform/heyform
Integrity checks
What held up, and what did not.
