Forms and surveys decision

Paperform

A capable developer can build a useful subset (form creation, rendering, submissions, Stripe payments and basic webhooks) in ~30 hours and maintain it cheaply, but matching Paperform's polished editor, templates, AI features, large integrations catalogue and enterprise compliance is not realistic for a single engineer.

Visit website
Subscription$24/month ✓ verified
Initial build30 hours
Monthly upkeep10 hours + $20
Evidence3/3 runs agree

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. All Paperform alternatives, with the arithmetic →

What a replacement has to do

  • Create form schema, render form for respondents, accept and store submissions (including file uploads and payments), run simple automations/webhooks and view/export results.

What it still won’t have

  • 30,000+ prebuilt templates and polished WYSIWYG editor
  • 2000+ native integrations catalogue
  • Built-in AI features and report insights
  • SOC 2 Type II compliance, SSO and enterprise security controls
  • Advanced analytics, Paperform-managed scaling, and priority support

What remains hard

  • Brand trustTrusted by 500K+ business owners and creators, and hundreds of millions of respondents.
  • Compliance and regulationSOC 2 Type II SSO & access management
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

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

Not run yet
Build a minimal self-hosted form builder using Node.js (Express), Postgres, React for the editor and renderer, and Stripe for payments. In scope: create/save form JSON schemas (fields, simple conditional logic, basic theming), render forms to respondents, validate and store submissions (files to S3), accept payments via Stripe, admin UI to view/export submissions, and a webhook sender for integrations. Out of scope: WYSIWYG rich design studio, enterprise SSO/SOC2 compliance, AI form generation, and 2000+ native integrations. Include error handling, input validation, unit tests for core APIs, and Docker deployment scripts.
How we checked5 sources · 3/3 runs agreed · evidence score 64

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.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page