Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database (gitforms-landing.vercel.app)
got tired of paying $29–99/month for simple contact forms on landing pages and side projects (Typeform, Tally, etc.).So I built GitForms: an open-source contact form that stores submissions as GitHub Issues.How it works:Form runs on your Next.js 14 site (Tailwind + TypeScript)
On submit → creates a new Issue in your repo via GitHub API
You get instant email notifications from GitHub (free)
Zero ongoing costs:No database, no backend servers Deploy on Vercel/Netlify free tier in minutes Configurable via JSON (themes, text, multi-language)
Perfect for MVPs, landing pages, portfolios, or any low-volume use case.Repo: https://github.com/Luigigreco/gitforms License: CC-BY-NC-SA-4.0 (non-commercial only – fine for personal projects, not client work).Curious what HN thinks: would you use this? Any obvious improvements or edge cases I missed?Thanks!
13 comments
[ 54.0 ms ] story [ 666 ms ] threadGood that you've positioned it for prototypes.
- that the code is 100% mit licensed (it's not)
- that this is in any way gdpr compliant (there are literal rules around this)
- that your data is encrypted and private (it isn't encrypted? Unless being written in Italian is encryption now?)
- that they'll have 99.9% uptime (there is no SLA for vercel hobby tiers)
- "No middlemen. No third-party storage. Every submission lives in your GitHub..." (that is the very definition of third-party storage and a middleman)
If you know it's a glued-together solution that you'll have to rip apart if your program scales, why make it so complex in the first place?
https://feature-refactor-for-cloudfl.first-contact.pages.dev...
It's no longer "live" so I wouldn't try and use it. I was using Supabase free tier to manage auth, and got tired of keeping it live. Good lesson learnt.
The Git trademark policy says they don't want people to name things like this.
> you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service
<https://git-scm.com/about/trademark>
Good luck on that hill.
Meanwhile, OP's project goes brrr.
It seems like you want to make this into some kind of viable business, and I don't mean to dissuade by any means, but this was a three-day project by a perfectly good guy, but one guy, extremely junior, that I was tasked with training on basic networking and systems administration duties. I don't want to speak ill of the man. I liked him a lot, but he was extremely hard to teach, could not seem to understand even the bare basics of how computers and the systems they collectively form when networked operate. But he could make this exact application, on his own, in a matter of days, before LLMs were a thing.
Not saying you can't manage it, but this is like trying to sell people sandwiches. Plenty make businesses doing exactly that, but you either need a captive audience or really good sandwiches, because most of the time anyone who wants one can make it themselves pretty easily.
Glad to see someone executing on this, and I love how descriptive the landing page is.
I even have it connected to a google sheet and google scripts, to send me emails for entries matching some patterns.
Heavily depends on Google, yes, but for something free that honestly I won't care if stops working (like a prototype) I'm ok with it.