Lohnt sich dein eigenes Paperform?

Build a personal replacement for Paperform in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and Resend; do not offer alternative stacks.
The core loop is: compose branded document-like public forms, validate submissions, notify the owner, and provide a private response table with CSV export, leaving payments out of scope.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create a form builder with short text, long text, email, number, select, radio, checkbox, and file fields.
Publish each form at a stable slug with server-side validation and accessible labels.
Add honeypot, rate limiting, submission-size limits, and a clear privacy notice.
Store responses in SQLite and provide search, filters, detail view, and CSV export.
Send an owner notification without placing submitted values in logs.
Support a thank-you screen and one simple conditional branch.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out payment collection.
Deliberately leave out hundreds of third-party integrations.
Deliberately leave out multi-brand enterprise workspaces and compliance attestations.
Finish by running the tests and listing the exact commands used.