Infrastructure for
the last mile
A form is the smallest piece of backend a website can need, and historically the most annoying to build. We built the piece so you do not have to.
MakeTheForm is a form backend. You point any HTML, React, Next.js, Webflow, or AI-built form at a single endpoint URL; we receive the submission, filter spam, store the full payload in a searchable inbox, and email it to you with the sender in Reply-To. There is no server to deploy, no database to run, and no secret to keep out of client code.
Every website eventually needs to receive something from a visitor: a message, an application, an RSVP, a lead. The form itself is ten lines of markup. Everything behind it is not: a POST handler, a spam strategy, a mail provider with a verified sending domain, somewhere durable to put the data, and a way to read it later.
That gap is why so many sites still ship a mailto: link that loses half its messages, or a contact form that quietly posts into nothing. It is also why AI site builders, which are genuinely good at producing the markup, hand you a form with nowhere to send it.
MakeTheForm is the missing half. One endpoint, and the parts nobody enjoys building are already built, already monitored, and already someone else’s problem at 3am.
What the system guarantees
These are not aspirations. They are invariants the product holds, and the reason it is built the way it is.
Never lose a submission
A submission is stored the moment it is accepted, before any notification is attempted. Email delivery can fail, a recipient can go unverified, a quota can run out. The payload is still in your inbox and still exportable. Storage and delivery are separate systems on purpose.
The endpoint is public, and that is fine
Your form key goes in client-side HTML, so we treat it as an address rather than a secret. Protection comes from origin rules, rate limits, and spam filtering. Not from pretending a string in a public page is confidential.
Explain, do not gate
An unverified email or a reached quota changes what we can deliver, never whether we accept. You keep setting up forms and reading code while the account is incomplete, and the interface tells you exactly what is limited and why.
Nothing submitted is ever rendered as markup
Every value that arrives from a visitor is displayed as plain text everywhere: the inbox, the email, the export. A form backend that renders attacker-controlled HTML is a cross-site scripting engine with extra steps.
Who it is for
People shipping static sites
Plain HTML on Netlify, GitHub Pages, or a folder on a VPS. You want a contact form and you do not want to stand up a server, a mail provider, and a spam filter to get one.
Send an HTML form to emailPeople building with AI
Lovable, Bolt, v0, Replit, and Claude will happily generate a beautiful form with nowhere to post it. One endpoint closes the gap, and the agent can wire it in a single prompt.
For AI buildersFront-end developers
React, Next.js, Vue, Svelte, Astro. You are perfectly capable of writing the backend. You just do not want to own another deployment, another secret, and another on-call surface for a contact form.
Browse platformsStart with one endpoint
The free plan is a real plan, not a trial. Create a form, paste the URL, and you are receiving submissions.