Formizee

Formizee provides the backend infrastructure most form-heavy sites need — submission handling, email notifications, and analytics — without requiring teams to run their own server for something as common as a contact or signup form. It targets the same use case as Formspree and Typeform, but as a self-hostable, open-source alternative.

The project is a Turborepo monorepo with a clear separation of concerns: apps/api handles form submission processing, apps/dashboard is the form-builder and analytics UI, apps/vault manages secrets/credentials, apps/logdrain handles log aggregation, and apps/docs/apps/web cover documentation and marketing. It’s built with Next.js and shadcn/ui for the frontend, and deploys on serverless infrastructure (Cloudflare hosts the API and vault components in Formizee’s own deployment).

Apache-2.0 licensed, Formizee is fully open source with no separate enterprise-gated codebase — the same code that runs the hosted service is what you’d self-host.

What You Get

• A form submission backend with email notifications, so forms work without a custom server
• A dashboard for building forms and reviewing submission analytics
• A dedicated vault component for managing secrets and credentials separately from the API
• Serverless-friendly deployment (the project’s own hosted instance runs on Cloudflare)

Common Use Cases

• Adding a working contact or signup form to a static site without building custom backend infrastructure
• Replacing Formspree or Typeform with a self-hosted form backend for cost or data-ownership reasons
• Collecting and analyzing form submissions across multiple sites from one dashboard
• Running form infrastructure on serverless/edge platforms instead of a traditional server

Under The Hood

Architecture Formizee’s Turborepo monorepo separates concerns cleanly: apps/api processes form submissions, apps/dashboard is the builder/analytics UI, apps/vault isolates secrets and credential management as its own service rather than embedding it in the API, and apps/logdrain handles log aggregation independently. This separation means the vault (handling sensitive credentials) has a smaller, more auditable surface than if secrets handling were mixed into the general API codebase.

Tech Stack Next.js and shadcn/ui for the dashboard and web apps, deployed on serverless infrastructure with Cloudflare hosting the API and vault in Formizee’s own instance. Managed as a pnpm/Turborepo workspace with Biome for linting/formatting.

Code Quality The monorepo has dedicated internal and tools directories for shared logic and tooling, and a deployment directory documenting infrastructure setup; however, GitHub activity signals show low recent commit velocity, worth checking before depending on it for active feature development.

What Makes It Unique Formizee separates secrets/vault handling into its own deployable service rather than bundling credential management into the main API — a more security-conscious architecture than many form-backend clones that keep everything in one process.

Self-Hosting

Licensing Model Apache-2.0 licensed — the entire platform, including the API, dashboard, and vault, is open source with no separately licensed enterprise codebase.

Self-Hosting Restrictions None found; the same code that runs Formizee’s own hosted service is available to self-host.

License Key Required No.