# Build brief — a focused alternative to Fomr

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

## Context

**Fomr** — Visual form builder with unlimited responses, design controls, sharing, and embeds. It currently costs $17/mo.

A useful single-owner form builder is a realistic focused project. Matching Fomr's visual editor, design depth, managed delivery, collaboration, integrations, and confidence that every public submission arrives turns it into an ongoing product rather than a one-shot clone.

This brief describes a focused, single-operator replacement for the part of Fomr 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

Create a single-owner form builder with live preview, publishable links, response storage, email notifications, and CSV export.

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

## Requirements

### Functional

- Node.js 22 or newer.
- Self-hosted deployment target.

### Data and integrations

- SMTP credentials in .env for optional notifications.

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 a deliberately narrow personal form builder inspired by Fomr, starting from an empty repository.
Use exactly this stack: Next.js 16, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM.
The core loop is create a form, preview it, publish it, collect responses, and export them.
Make it single-owner and protect the admin area with an ADMIN_PASSWORD from .env.
Create an admin form editor with a reorderable field list and a live respondent preview.
Support short text, long text, email, number, select, radio, checkbox, rating, date, and content blocks.
Allow required fields, labels, help text, placeholders, choices, and basic min/max validation.
Support one simple conditional rule per field: show it when another answer equals a configured value.
Add form-level colors, font choices, logo upload, cover image, spacing, and light or dark appearance.
Publish each form at /s/<slug> with accessible labels, keyboard navigation, and mobile layouts.
Validate every submission on the server against the saved form schema.
Store forms, immutable schema versions, responses, and timestamps in SQLite.
Provide a private response table with search, detail view, deletion, and CSV export.
Send optional owner notifications through SMTP, but keep collection working when SMTP is absent.
Add a honeypot, per-IP rate limiting, request-size limits, and safe upload handling for branding assets.
Include a configurable thank-you message and optional redirect URL.
Handle empty, loading, validation, success, not-found, and recoverable failure states.
Keep user data local and add JSON export and import for forms.
Do not add analytics, telemetry, ads, billing, or third-party accounts.
Put every secret in .env and include a complete .env.example.
Write unit tests for schema validation and branching plus one end-to-end publish-and-submit test.
Create a README covering setup, deployment, data location, backups, SMTP, security limits, and recovery.
Deliberately exclude custom domains, team collaboration, OAuth integrations, payments, and enterprise compliance.
Deliberately exclude a marketplace-sized template library and promise only personal-scale reliability.
Run tests and a production build before finishing, fixing failures instead of merely describing them.

## 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:

- Real-time team collaboration.
- Custom domains and managed TLS.
- Managed uptime, backups, and abuse controls.
- Integration catalog.
- Template and theme depth.

## What you still own after launch

- 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 reviewed project implementation is linked yet.

## Existing alternatives

Before building, compare these checked options:

- [HeyForm](https://heyform.net) — Typeform-style visual forms without the rent; one container to own the whole thing
- [Tally](https://tally.so) — A generous hosted form builder with logic and unlimited responses; branding is the upsell
- [OpnForm](https://opnform.com) — Open-source forms with unlimited respondents; the free self-hosted builder team stops at two

## Prior art

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

- [HeyForm](https://github.com/heyform/heyform) — Open-source form builder with public forms, logic, and response collection
- [Formbricks](https://github.com/formbricks/formbricks) — Open-source survey and experience-management platform

---

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