Forms and surveys decision

Formsite

A capable developer can reproduce a useful subset (hosted forms, submissions, embeds, exports) in-house, but Formsite's scale, extensive integrations, payments handling, and production polish make a full replacement costly to match.

Visit website
You pay

$21/mo

$252/yr

Read off the official pricing page.

You’d pay instead

$100one-off80 h to build

$0/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 1 seat.

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 Formsite alternatives, with the arithmetic →

What a replacement has to do

  • Provide a web UI to design forms, serve a public form endpoint, store submissions, view/export results, and send email notifications or webhook integrations.

What it still won’t have

  • 2000+ third‑party integrations out of the box
  • Hosted scale / proven uptime for high submission volumes
  • Built-in payment processor integrations and PCI handling
  • Ready-made templates, themes, and advanced workflow features
  • 24/7/365 vendor support and uptime guarantees

What remains hard

  • Infrastructure at scaleProcessed over $500 Million in payments
  • Infrastructure at scaleBillions of forms submitted
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

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 hosted form service using React for the admin UI, a JSON schema-based form renderer, Node.js + Express for the API, PostgreSQL for form and submission storage, AWS S3 for file uploads, and Stripe for optional payments. In scope: (1) form creation/editing (save JSON schema), (2) public form endpoints with server-side validation and file uploads to S3, (3) submission storage and a web UI to list/export submissions as CSV, (4) email notifications and a webhook delivery retry queue, (5) an embeddable script/snippet and basic theming. Out of scope: drag-and-drop WYSIWYG builder with complex conditional-visual editing, multi-tenant billing UI, and 2000+ third-party integrations. Include authentication for the admin UI, input validation, error handling, unit tests for API routes, and basic end-to-end tests for the submit → store → notify flow.
How we checked5 sources · 2/3 runs agreed · evidence score 60

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
  • Hard moats found in the evidence-3
  • Evidence score60

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! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 2 moats quoted from the page