The best form backends for developers

Web3Forms sends form submissions to your inbox without a server, and its free tier is unusually literal about the word free: unlimited forms, unlimited domains and two hundred and fifty submissions a month, with no charge attached to any of it. A free plan is often a demonstration; this one is closer to a working allowance for a small site.

The first step is correspondingly short. You request an access key against an email address and put it in a hidden field, which means a contact form can go live without creating an account first. For a personal site or a small brochure site that is the whole job.

The cost shows up as you grow. Both paid tiers are billed yearly rather than monthly, and file uploads and autoresponders sit behind them. There is no form editor of any kind, so how the form looks is entirely your own stylesheet, and any logic between one question and the next is yours to write. Customisation is unbounded for the same reason the product supplies none of it. Against that, the value for money on the free tier is hard to argue with.

Formspree does one thing: it receives the submission. You write the form in your own HTML, set its action to an endpoint, and the service validates the data, filters the spam and sends you the result. There is no editor, and that is the product rather than a gap in it.

That shape decides everything else. How the form looks is entirely your stylesheet, so the appearance the product supplies is close to nothing and the appearance you can achieve has no ceiling at all. Customisation is total for the same reason. Logic lives in Form Rules, which route a submission to different addresses, flag it as spam or change where the visitor lands, rather than in branching a respondent sees.

The cost is the audience. Somebody who cannot write a form tag gets nowhere, and the free tier's fifty submissions a month is a testing allowance rather than a working one. What it buys is that nothing about the form is decided for you.

Forminit is the same shape of product as any form backend: your markup posts to its endpoint, and it stores, filters and forwards what arrives. It was called Getform.io until recently and the old address still resolves, which is worth knowing when older write-ups point somewhere that no longer carries the name.

Where it puts its effort is the onward journey. The paid tiers add webhooks to an endpoint you choose, a REST API for pulling submissions programmatically, and direct delivery into Slack, Discord and Google Sheets, with form analytics tracking where a submission came from. That is a fuller answer to what happens after submit than the category usually gives, and it arrives at the first paid step rather than the last.

The cost is that everything visible is still yours to build. How the form looks is your stylesheet and nothing else, so customisation has no ceiling and no starting point either, and any logic a respondent experiences is yours to write. The free plan's hundred submissions a month is an evaluation allowance, and branding removal applies to notification emails, the one surface the product renders itself.

Basin receives submissions from forms you have already built, and its distinguishing decisions are both about limits. Spam does not count against your monthly allowance, which matters more than it sounds when the allowance is the thing you are paying for. And going over the cap does not close the form.

That second decision is the one worth pausing on. A form that hits its limit and closes turns a successful campaign into lost data. Basin keeps delivering instead, and bills the excess by the thousand on a published sliding scale that falls as volume rises. The rate is published in full, and it is the number to read before a campaign rather than after it.

The cost is that nothing visible arrives with it. There is no editor, so how the form looks is whatever your own stylesheet does and customisation is limited only by what you are willing to write. The free plan's fifty submissions a month is for trying it rather than using it.