Form backend for developers
Connect any HTML form to one endpoint. Receive spam-filtered submissions by email and in a searchable inbox, without building or hosting backend code.
Free plan No card required
<form action="New contact from Enterprise Lead
just nowada@example.com
Job application: Senior Engineer
10:15p.chen@example.com
Newsletter signup
09:30hello@example.com
Point your form’s action attribute at your endpoint. We handle the rest: spam, routing, and notifications. Infrastructure handled.
<form action="https://mtform.co/f/xhq92k" method="POST">
<input type="email" name="user_email" />
</form>Set your form action to the URL and you are done. Works with plain HTML, React, Next.js, Vue, Astro, Webflow, and anything an AI builder generates.
Honeypot handling, rate limits, and origin rules run before anything reaches you. Filtered submissions stay in a spam view you can review, never silently deleted.
Every submission is stored the moment it is accepted, before any email is attempted. A mail outage delays the notification, it does not lose the payload.
Notifications arrive with the sender in Reply-To, so answering a contact form is one keypress instead of a copy and paste.
A form backend is the server side of a web form: the part that receives the POST, filters spam, stores the submission, and delivers it to you. HTML can describe a form but cannot process one, so without a backend a form has nowhere to send anything. A hosted form backend gives you that endpoint without deploying or maintaining a server.
Yes. Set your form action to a hosted endpoint URL and the submission is received, spam filtered, stored, and emailed to you. This is a two-line change to your markup, needs no JavaScript, and works on static hosts like GitHub Pages and Netlify that cannot run server code.
No. The endpoint lives in client-side HTML that anyone can view, so it is an address rather than a credential. Forms are protected by restricting which domains may submit, by rate limits, and by spam filtering. Any provider telling you to hide a key that ships in the page is describing something that cannot work.
Nothing is lost. A submission is stored the moment it is accepted, before any notification is attempted, so storage and delivery are independent. An unverified recipient, a mail outage, or an exhausted quota delays the email while the payload stays in your inbox and remains exportable.
Yes. The endpoint accepts an ordinary POST, so it does not care what rendered the form. That covers plain HTML, React, Next.js, Vue, Svelte, Astro, and Webflow, along with pages generated by Lovable, Bolt, v0, Cursor, and Replit, which produce working markup but no backend to receive it.
Stop building custom form backends. Start routing data reliably today.
Create free endpoint