About FlintHive
FlintHive is one person: Arafat Uddin, working from Chattogram, Bangladesh.
I build small, focused developer tools. Right now there is one — FormForge, a form filler for QA and development work — and everything on this site comes from building it.
Why the tools work the way they do
I write tools that run inside other people's browsers, on pages I have never seen. That makes trust the whole problem. Anyone can write "handles React" and "makes no network requests" on a store listing. Nobody can check it.
So the rule I work to is that a claim has to be something you can test yourself, not something you take on faith:
- FormForge makes no network requests at all, and holds no access to any site when it is not being used. Both stores' own privacy disclosures say so, and you can read them without taking my word for it.
- The test suite ships inside the extension. You can open it and run the real fill engine in your own browser, on your own version of Chrome, on the free tier, with no account. It covered 73 deliberately awkward fields in September 2026, and grows with each release.
- I put a version of those fixtures on this site as a free tool anyone can use, including people who use a different form filler than mine. It grades whatever filled it and has no idea which tool that was.
That last one cost me something, which is the point. The first time I ran FormForge against it, my own extension failed a case — it filled a hidden honeypot field, the kind of trap a site uses to catch bots, which would have got a real user's form submission silently thrown away. My own test suite had not caught it in two weeks. The public page caught it on day one. It is fixed now, and the score on that page says whatever it says.
The honest parts
I am not a native English speaker, and I write with help. The words get edited; the measurements do not.
FormForge is new and has few users. I would rather say that than imply otherwise — everything on the comparison page is sourced and dated, including the numbers that do not flatter me.
There is no team. If you email support, I am the one who reads it.
Contact
support@flinthive.com — bug reports, licence problems, or anything about the tools.
If you run the form filler test and something fails, that is the most useful email I can get.