I built FormFlow because form projects kept repeating the same work in four places: a data model, validation service, admin interface, and frontend form. The first contact form was simple. File uploads, spam protection, notifications, exports, and permissions were not. FormFlow moves the form definition and submission workflow into Strapi. An editor builds the form in the Strapi admin. A frontend requests a sanitized schema over REST and renders it with its own components. The server validates final submissions again and stores them in the project's Strapi database. The frontend is deliberately unopinionated. There is no iframe and no bundled stylesheet. The React and Vue SDKs are renderless; they provide state, validation, conditional visibility, file handling, and accessible prop getters, while the application keeps its markup and design system. Teams can also ignore the SDKs and call the REST API directly. FormFlow is open-core. The MIT-licensed free core includes unlimited forms and submissions, standard fields, file uploads, validation, the submission inbox, CSV/JSON export, basic spam controls, email notifications, RBAC, the REST API, and SDK compatibility. Some advanced workflows are licensed separately, and the repository documents that boundary. The product is live on npm. The most useful feedback now is implementation feedback: create one real form, render it in an existing frontend, and tell me where the schema, validation, or submission contract gets in your way. Install it with: ```bash npm install @formflowjs/strapi-plugin-formflow ```

FormFlow

Visual form builder for Strapi

Visual form builder for Strapi