Formizee

Open-source form submission platform, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (Apache-2.0) form submission and management platform — think Formspree or Formcarry, but self-hostable with built-in ClickHouse analytics and per-tenant encryption [1][4].
• Who it’s for: Developers building static sites, Jamstack apps, or any frontend that needs a form backend without rolling their own. Not a no-code form builder — this is an API endpoint service with a dashboard [4].
• Cost savings: Formspree’s free tier caps at 50 submissions/month; Formizee gives 250 — five times more at $0. The Pro plan will be $5/month for 1,000 submissions versus Formspree’s $10/month for comparable volume [1][2].
• Key strength: Best free tier in its direct competitor set, edge-first architecture on Cloudflare for global low latency, AES-256 per-tenant encryption on submission data, and a genuinely permissive open-source license [1][4].
• Key weakness: 177 GitHub stars, solo developer, Pro plan listed as “Coming Soon” as of this writing, and the self-hosting stack — Cloudflare Workers plus ClickHouse plus LibSQL — is substantially harder to run on a bare VPS than a Docker Compose tool [2][4].

---

What is Formizee

Formizee is a form submission backend. You point an HTML <form> at a Formizee endpoint, submissions come in, you view the data in a dashboard with realtime analytics, and optionally get email notifications. The project positions itself explicitly against Formspree, Formcarry, Formester, FormBold, and SlapForm — the class of services that let you handle form submissions from static sites without writing backend code [4].

The open-source claim is substantive. The code is Apache-2.0 on GitHub — not a “source available” or “Fair-code” arrangement with commercial restrictions, just a permissive license [4]. The technical foundation is deliberately modern: Hono for the API layer, Next.js for the dashboard, LibSQL (Turso’s SQLite fork) as the primary database, and ClickHouse for analytics. The API runs on Cloudflare’s edge network, which is the basis for the “global low latency” claim on the homepage — form submissions hit a Cloudflare point of presence rather than routing to a single origin server somewhere in Virginia [1][4].

Formizee S.L. is registered in Valencia, Spain and built entirely by one person, Pau Chiner [3][5]. The about page states this plainly: “Formizee is a small, independent SaaS built and run by one person. It’s not backed by venture capital or part of a big tech company.” [3] That transparency matters — it sets accurate expectations about support response times, roadmap reliability, and what happens if the maintainer burns out.

The product scope is narrower than Typeform or Tally. Formizee is a form backend — submission ingestion, storage, analytics, notifications, API access. The homepage headline says “Design, build and analytics” [1], but based on the README and site content, the core use case is developers who already have HTML or React forms and need somewhere to send submissions, not non-technical users who need to build forms without writing markup.

---

Why people choose it

Independent reviews of Formizee don’t exist yet — the project is too new and too small to have accumulated G2 reviews, Trustpilot entries, or Reddit threads. What follows is drawn from primary sources (website, README, legal documents) and context from the broader self-hosted tools conversation.

Versus Formspree. This is the competition Formizee picks itself [4]. Formspree’s free plan: 50 submissions/month. Formizee’s free plan: 250 [1][2]. That 5x gap matters most for side projects, portfolios, and early-stage products that are genuinely low-volume but where 50/month runs out in a week of promotion. On paid tiers, Formspree charges $10/month for 1,000 submissions; Formizee’s Pro will cost $5/month for the same [2]. Formspree is also fully proprietary — no self-hosting, no source code access. Formizee’s Apache-2.0 license changes that equation completely for developers who care about data ownership.

Versus Formcarry and Formester. The Formizee homepage lists the free tier limits of its competitors side by side: Formcarry 50/month, Formester 100/month, FormBold 100/month, SlapForm 50/month [1]. Formizee’s 250/month wins that comparison cleanly. The omission from that list — Tally and OpnForm — is worth noting; those are the more capable open-source alternatives.

On privacy and data sovereignty. Formizee is registered as an EU company (Spain), GDPR-compliant by design, and implements per-tenant AES-256 encryption on submission data [1][5]. This means submission data stored for your endpoint isn’t commingled with other customers’ data in plaintext. For contact forms that collect email addresses, inquiries, or anything sensitive, that’s a meaningfully different security posture than what most form SaaS vendors describe. The broader case for self-hosting form data — keeping customer inquiries off third-party servers entirely — is the same motivation that drives teams off Formspree and Typeform in general [6].

---

Features

Based on the README, homepage, and pricing page:

Core form handling:

• Form endpoints — submit HTML forms via POST directly to the Formizee API [4]
• Dashboard to view, filter, and manage all submissions [1][4]
• Multiple forms per workspace, configurable per-form settings [2]
• API keys for programmatic access — up to 10 on free, 1,000 on Pro [2]
• REST API with open access (“unlike other companies, here we give you the freedom to use our API as you like”) [1][4]

Analytics and observability:

• Realtime submission analytics powered by ClickHouse [4]
• Request volume metrics, submission counts per endpoint [1]
• Stats displayed on the main dashboard [1]

Security and compliance:

• Per-tenant AES-256 encryption on all submission data [1]
• Auth.js authentication for dashboard access [4]
• GDPR-compliant processing — EU company, EU data handling standards [5]

Developer experience:

• SDKs in multiple languages (mentioned on homepage, no full language list available) [1]
• tRPC typed API internally; REST API for external consumers [4]
• Integration examples in the README for common use cases [4]
• External integrations (Slack, webhooks to third-party services) listed as “Coming Soon” [1]

Teams and workspace:

• Team member support with permission controls [1]
• Up to 10 members free, 100 members on Pro [2]
• Storage: 100 MB free, 1 GB Pro [2]

What isn’t there yet:

• External integrations and notifications beyond basic — listed explicitly as “Coming Soon” [1]
• The Pro plan itself is “Coming Soon” [2]
• No drag-and-drop form builder with conditional logic — this is an endpoint service, not a form creation tool

The “Coming Soon” markers are a genuine flag. You cannot pay for Pro yet, and the integrations that would connect Formizee to email providers, Slack, or Zapier-style automation don’t exist yet either.

---

Pricing: SaaS vs self-hosted math

Formizee Cloud:

• Hobby (Free): 1,000 API requests/day, 250 submissions/month, 100 forms, 10 API keys, 1 member, 100 MB storage, community support [2]
• Pro ($5/month, “Coming Soon”): 100,000 API requests/day, 1,000 submissions/month, 1,000 forms, 1,000 API keys, 100 members, 1 GB storage, email support [2]

Formizee Self-Hosted:

• Software cost: $0 (Apache-2.0) [4]
• Infrastructure: depends on your setup — see deployment section

Competitor pricing for context:

• Formspree: Free for 50 submissions/month; $10/month (Basic) for 1,000 submissions; $40/month for unlimited
• Typeform: Free for 10 responses/month; $25/month (Basic) for 100 responses
• Tally: Free tier with unlimited forms; Pro at $29/month
• Formcarry: Free for 50/month; paid from $9/month

Concrete savings math:

A landing page collecting 600 contact form submissions per month exceeds Formspree’s free tier (50) and Basic tier (1,000 but $10/month). On Formizee Pro that same workload is $5/month — $60/year saved against Formspree alone [2]. Self-hosted on a $5/month Hetzner VPS (assuming you can actually run the stack — see below): roughly $60/year in server costs vs $120/year on Formspree.

The savings are real but in a different magnitude than escaping Zapier or Typeform enterprise. Form backends were already cheap. The stronger financial argument for Formizee is eliminating per-submission costs entirely on self-hosted while keeping analytics, encryption, and API access intact.

---

Deployment reality check

The cloud version of Formizee runs across eight separate services: Vercel (frontend/dashboard), Cloudflare Workers (API), Tinybird (ClickHouse analytics), Turso (SQLite/LibSQL), AWS (SMTP relay), BetterStack (status), Sentry (error logging), Stripe (payments) [4]. That list tells you what you’re dealing with when you self-host.

The README links to a local development guide and a contributing guide, but there is no documented Docker Compose path for a production self-hosted deployment [4]. This is a Cloudflare Workers–native architecture, and that creates a genuine problem for anyone trying to run it on a conventional VPS: Workers aren’t a standard runtime, ClickHouse has real resource requirements, and the LibSQL/Turso dependency assumes edge database access patterns.

What you realistically need to self-host:

• A way to run Cloudflare Workers locally or a compatible edge runtime substitute
• A self-hosted ClickHouse instance (feasible, but requires 2–4 GB RAM minimum and maintenance)
• LibSQL-compatible database
• SMTP service for email notifications
• Node.js runtime for the Next.js dashboard

Honest assessment: If you’re a developer who has built Cloudflare Workers projects and understands the Hono framework, self-hosting Formizee is achievable with meaningful effort and some architecture substitutions. If you’re a non-technical founder who wants to escape Formspree with a simple self-hosted alternative, this is not that — at least not yet. There is no “run this one docker-compose up command” guide, and the production infrastructure model assumes cloud primitives, not a bare VPS [4].

At $5/month for the Pro tier when it launches, the cost case for self-hosting over using Formizee’s own cloud is weak for most users. The self-hosting argument is about data sovereignty and auditability, not economics.

---

Pros and cons

Pros

• Genuine Apache-2.0 license. No commercial use restrictions, no “Fair-code” ambiguity. Fork it, embed it in a product, audit it [4].
• Best free tier in its stated competitor set. 250 submissions/month versus 50–100 for every direct competitor listed on the homepage [1][2].
• Per-tenant AES-256 encryption. Submission data is encrypted at rest, not stored in shared plaintext tables [1].
• ClickHouse analytics built in. Realtime metrics without integrating a separate analytics product [4].
• Edge-first architecture. Cloudflare-hosted API means lower submission latency for global users [1].
• EU company, GDPR by default. Spain-registered, EU data handling — not an afterthought privacy policy from a US company [5].
• Honest about its nature. The about page explicitly says “one person, no VC” — no misleading corporate language for a solo project [3].
• Cheap Pro pricing. $5/month when it launches is genuinely the cheapest paid option in this category [2].

Cons

• 177 GitHub stars. Early-stage signal. Fewer users means fewer edge cases caught, thinner documentation, higher risk that something breaks in production and nobody has filed the issue yet [4].
• Pro plan is “Coming Soon.” You can’t pay for the product today. You’re on the free tier (250 submissions/month) or self-hosting [2].
• Solo developer, no team, no funding. Single point of failure for maintenance, releases, and support [3][4].
• Self-hosting is not Docker-simple. Cloudflare Workers + ClickHouse + LibSQL is a more complex stack than most self-hosted tools ship. No documented VPS deployment path [4].
• No form builder. No conditional logic, branching, multi-step flows, or visual editor. It’s a submission endpoint with a dashboard — not a Typeform replacement [1][4].
• Integrations not built yet. No Slack, no webhooks to third-party services, no email automation — all “Coming Soon” [1].
• No independent reviews. Zero third-party analysis means no war stories, no reported bugs, no production feedback from real users outside the maintainer.

---

Who should use this / who shouldn’t

Use Formizee if:

• You’re a developer with a static site or React app that needs a form endpoint, and you’re hitting Formspree’s 50/month free tier wall.
• You care about per-tenant encryption and EU data residency for contact form submissions.
• You want Apache-2.0 source code you can read, audit, or fork.
• You’re willing to bet on an early-stage project in exchange for better economics and data control.
• You need form analytics without paying for a separate analytics tool.

Skip it (stay on Formspree) if:

• You need proven uptime, a real support team, and SLAs — this is a one-person operation.
• You need integrations with email providers, Slack, or automation platforms — those don’t exist yet.
• You’re provisioning something for a client or employer where production reliability is non-negotiable.

Skip it (use Tally) if:

• Non-technical people need to build or edit forms without touching HTML.
• You want conditional logic, multi-step flows, and embedded form design tools.
• You want a visual form product with a large existing user base.

Skip it (use OpnForm) if:

• You need a full open-source Typeform alternative with drag-and-drop builder.
• You want Docker-based self-hosting with a documented deployment guide.
• You need more GitHub activity and contributor history behind the codebase.

---

Alternatives worth considering

• Formspree — the direct target. More mature, production-tested, documented SLAs. Expensive free tier (50 submissions), fully proprietary, no self-hosting.
• Tally — generous free tier, visual form builder, no self-hosting option. Better for non-technical users who need to create forms, not just receive them.
• OpnForm — open-source Typeform alternative with Docker self-hosting and a full form builder. If you want open source with an actual form creation UI, this is the more mature option.
• HeyForm — another open-source form builder with more GitHub history and a Docker-deployable self-hosting path.
• Formspark — developer-focused form backend similar in positioning to Formizee, but proprietary and paid-only.
• Basin — polished paid form backend, no self-hosting, clean API.
• Netlify Forms / Vercel Forms — if you’re already deployed on these platforms, the built-in form handling may be sufficient without a third-party service.

For developers who specifically want open source and data ownership, the practical shortlist is Formizee vs OpnForm. Formizee if you need a submission endpoint with analytics and don’t need a form builder. OpnForm if you need users to build their own forms without code.

---

Bottom line

Formizee is technically better-built than its price and GitHub star count suggest. The ClickHouse analytics, per-tenant encryption, and edge-first Cloudflare architecture are infrastructure decisions that established players in this space haven’t made. The Apache-2.0 license is real, the free tier is the most generous in its category, and the $5/month Pro pricing — when it actually launches — will be the cheapest full-featured option available.

The honest risk is that this is one person’s solo project with 177 stars and no paying customers yet. The Pro plan isn’t live, integrations aren’t built, and self-hosting requires more ops knowledge than the homepage implies. Watch the GitHub commit history for the next six months. If the Pro plan ships and the integrations roadmap moves, this becomes a serious recommendation for any developer who’s been paying Formspree’s per-submission tax. Right now it’s a well-architected early bet.

If deploying Formizee — or evaluating which open-source form backend fits your stack — is the blocker, upready.dev handles exactly that: one-time setup, your infrastructure, your data.

---

Sources

1. Formizee Homepage — The Open-Source Forms Platform — https://formizee.com
2. Formizee Pricing Page — Hobby and Pro plan details — https://formizee.com/pricing
3. Formizee About Page — “Made With Love: a love letter to all indie developers” — https://formizee.com/about
4. Formizee GitHub README — https://github.com/formizee/formizee (177 stars, Apache-2.0, maintained by Pau Chiner)
5. Formizee Terms of Service — Company and legal details: Formizee S.L., Valencia, Spain — https://formizee.com/legal/terms-of-service
6. Dmitry Tsvetkov, pixeljets.com — “Self-hosted is awesome” — general self-hosting cost and data control context — https://pixeljets.com/blog/self-hosted-is-awesome/