Announcing Winnow

I am announcing Winnow, FormBeam's spam project for developers who want a form backend with little extra work in the setup, and no CAPTCHA for the people who actually fill out the form.

People hate CAPTCHAs, and you have watched that hate show up as a lost message. Someone you actually wanted, a customer or a hire or a reader with a real question, opens the contact form and hits the checkpoint. They click the box, wait for the images, miss one, start over, and close the tab. The industry treats that as the price of not drowning in bots, which is how a hard problem gets parked on the one person who was never the problem.

You were looking for a form backend so you would not have to stand up mail, storage, and spam yourself. Formspree and tools like it already made the developer side of that easy. They handle a CAPTCHA for you, so you do not wire site keys or drop a widget yourself, and setup stays short. The people filling out the form still had to go through it. The hard problem got automated for you and left sitting on the visitor, which is how a contact form keeps costing you the message you wanted.

Spam on a public contact form is genuinely hard, and it has been hard for a long time. The junk is cheap, repetitive, and it changes when the old tricks stop working. Making the visitor do the work protects the inbox well enough and costs you the message. You traded a bot problem for a conversion problem and called it security. It is overdue for a contact form to stop working that way.

I would not put that tax on a form I use myself. Winnow keeps the hard part on FormBeam's side so a real person can write a message and send it. You should not have to ship a challenge widget or open a second spam account to get a usable inbox, and a bot should not become an email you have to delete or a webhook you have to filter again. Junk can still sit in the dashboard.

Winnow is already in testing, and even this early it is exceptionally fast, which is the point of putting the filter on our side: it should not become another script on the page or another wait for the person submitting. The work is ongoing, because bots will keep changing, and the project is to keep the grain, throw the chaff, and leave both the developer and the visitor alone.