# Build brief — a focused alternative to Jotform

> **Verdict:** Partly, if you narrow it · **Buildability:** 63/100 · **Category:** Forms
> **Source:** https://www.canitbevibecoded.com/jotform
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Jotform. Verify current pricing and capabilities before acting.

## Context

**Jotform** — Form builder with payments, approvals, apps, tables, and workflow tools. It currently costs $39/mo.

Basic forms are easy, but Jotform's broad widget library, payments, approvals, PDF generation, tables, apps, and compliance options create a large surface.

This brief describes a focused, single-operator replacement for the part of Jotform that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Build form creation, public forms, response storage, notifications, CSV export, and optional payment widgets.

- Create forms, validate submissions, store responses, and export the results.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Database.
- Form renderer/editor.
- Storage.
- Email.
- PDF generation if needed.

### Data and integrations

- Payment API.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a personal form builder to replace Jotform. Requirements:

- Node + Express + better-sqlite3. Two surfaces: an admin UI bound to localhost for
  building forms, and public form pages at /f/<slug> for anyone with the link.
- Form definitions stored as JSON in SQLite. Field types: text, email, textarea,
  select, checkbox, date, and file upload (files to an uploads/ folder, 10 MB cap).
- Server-side required-field and email-format validation, a per-form thank-you
  message, plus a honeypot field and a per-IP rate limit to keep bot spam out.
- Every submission stored with timestamp and form version; an admin table view per
  form with CSV export of all responses.
- Email me each submission as a plain-text summary via SMTP (creds in .env).
- Only the public form pages are exposed; admin stays on localhost. No user
  accounts, no telemetry.
- Out of scope: payment collection, PDF generation, approval workflows, and a
  widget catalog. The field types above are the whole palette.
- README: how to put the public side behind a reverse proxy and where uploads live.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Widget catalog.
- PDF/approval workflows.
- Payments.
- App builder.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [OhMyForm](https://github.com/ohmyform/ohmyform) — Open-source form builder prior art; useful for a simpler Jotform alternative

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/jotform