Lohnt sich dein eigenes Formasty?

Build a single-user, self-hosted form builder and response collector. Stack: Next.js 15 App Router, TypeScript, Tailwind, SQLite via better-sqlite3. No other hosted services.
Data model: forms(id, slug, title, schema JSON, theme JSON, createdAt), responses(id, formId, payload JSON, meta JSON, createdAt), deliveries(id, responseId, url, status, attempts).
Admin builder at /admin/forms/[id]: add, reorder, duplicate and delete fields. Field types: short text, long text, email, number, single select, multi select, dropdown, date, rating 1 to 5, file upload, consent checkbox, hidden field.
Per field: label, help text, required flag, placeholder, and simple conditional visibility (show this field when field X equals value Y).
Multi-step forms: fields grouped into steps, one step per screen, progress bar, back button, answers held in client state until final submit.
Public form at /f/[slug]: server-rendered, mobile-first, keyboard navigable, and revalidated on the server so client validation is never the only check.
Persist in-progress answers to localStorage keyed by form slug so a refresh does not wipe the form.
File uploads write to ./uploads with a size cap and mime allowlist defined in the schema; store the relative path in the response payload.
Spam control: hidden honeypot field, reject submissions completed in under 2 seconds, and a per-IP rate limit table in SQLite. No captcha, no third party.
Notifications: on submit, send a plain text digest of the response over SMTP with nodemailer using SMTP_HOST, SMTP_USER, SMTP_PASS, NOTIFY_TO from .env. If those are unset, log and continue instead of erroring.
Optional per-form webhook URL: POST the response JSON, 3 retries with backoff, log every attempt in deliveries.
Responses view at /admin/forms/[id]/responses: table with one column per field, text search, date range filter, detail drawer, delete, and CSV export of the current filter.
Embedding: an /embed/[slug] route plus a small public/embed.js that injects an iframe and auto-resizes it via postMessage.
Theming per form: accent color, one of three system font stacks, light or dark, optional cover image, custom thank-you message, optional redirect URL.
Auth: a single ADMIN_PASSWORD from .env and a signed httpOnly cookie session for all /admin routes. No user accounts, no OAuth, no analytics, no telemetry.
Seed script creating two demo forms: a three-step onboarding survey with conditional fields, and a one-page contact form.
Out of scope: payments, e-signatures, team accounts, template marketplace, A/B testing, AI form generation.
Deliver a README with setup steps, a .env.example, a note on backing up form.db plus ./uploads, and a Dockerfile listening on port 3000.
Ship working code, not scaffolding: npm install, npm run seed, npm run dev must yield a fillable form at /f/contact and a visible row in the responses table.