Forms and surveys decision

Cognito Forms

A competent developer can build a limited forms-and-submissions replacement (render/forms/storage/notifications) in about a week, but Cognito Forms' compliance, portal/workflow polish, payments, and document features are nontrivial to replicate and justify keeping the paid service for full production use.

Visit website
Subscription$24/month ✓ verified
Initial build30 hours
Monthly upkeep4 hours + $35
Evidence2/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.

What a replacement has to do

  • Render configured forms, accept and validate submissions, store entries, trigger notifications/webhooks.

What it still won’t have

  • Drag-and-drop visual form builder and theme editor
  • Built-in document generation (Word/PDF) and electronic signatures
  • Client portals and guest access
  • Payments integrations and card-on-file flows
  • SSO, folder permissions, and HIPAA/GDPR/CCPA attestation/certifications at scale

What remains hard

  • Compliance and regulationStay compliant with HIPAA, GDPR, CCPA and other privacy regulations.
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 hosted form service using Node.js (Express), Postgres, and a React front-end. Include: (1) a JSON-based form schema format and a React renderer with client-side validation; (2) Express endpoints to serve form schemas and accept submissions, persisting to Postgres; (3) server-side email notifications via SMTP and outgoing webhooks; (4) an admin React UI to list, search, view, and export submissions as CSV; (5) deployment scripts for Docker on a single VPS. Out of scope: drag-and-drop form editor, payments, document generation, SSO, HIPAA certification. Include error handling, input validation, basic tests (unit + integration for API), and README with deployment steps and backup/migration notes.
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! 1 moat quoted from the page