Forms and surveys decision

Youform

A competent engineer can build a narrow self-hosted form system (forms, conditional logic, storage, integrations) using existing open-source projects, but reproducing Youform's polish, hosted scale, AI builder, analytics, and managed security would be significant work; keep paid if you need those.

Visit website
You pay

$29/mo

$348/yr

Read off the official pricing page.

You’d pay instead

$100one-off80 h to build

$0/mo8 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 Youform alternatives, with the arithmetic →

What a replacement has to do

  • Create a form schema, render the form to respondents, collect and store submissions, run conditional logic and partial-save, and export or forward responses via webhook/integration.

What it still won’t have

  • Hosted scaling, uptime SLAs and managed EU AWS hosting
  • Built-in AI form generator
  • Built-in analytics with drop-off heatmaps and advanced dashboards
  • Branded, polished UI and many pre-built templates/themes
  • SOC2-progress compliance and managed security posture

What remains hard

  • Brand trust90,000 + Users worldwide
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 self-hosted form-builder using: Postgres, Node.js (Express) or Python (FastAPI) backend, React for the frontend, S3-compatible storage (MinIO or AWS S3), and Redis for autosave sessions. Implement: form schema CRUD with JSON schema, multi-step renderer with conditional logic and answer piping, submission endpoints with validation and file uploads to S3, partial-save autosave + refill links, webhook and Google Sheets export, Stripe payment integration, and an admin dashboard to view/export responses and basic analytics (views/starts/completion rate). Out of scope: drag-and-drop WYSIWYG theme editor, AI form generation, enterprise SOC2 compliance. Include tests for API endpoints, end-to-end form submission flow, error handling for failed uploads/integrations, and deployment scripts (Docker + docker-compose).
How we checked5 sources · 3/3 runs agreed · evidence score 67

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
  • Evidence score67

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! 1 moat quoted from the page