What is a form backend? A plain-English guide

A form backend is a hosted service that receives your website’s form submissions, so you don’t have to write or run server code. Your HTML form posts to the service’s URL. The service checks the data, filters spam, stores it and sends it to you, usually by email. In short, it is the server half of a form, rented instead of built. This guide explains what a form backend is, how form backends work step by step, and when one is the right choice.

A form has two halves

Every web form has two parts.

The front end is what visitors see: inputs, labels, a button. It’s plain HTML (or a component in React, Vue or Svelte) and any website can show it.

The back end is what happens after someone presses Send. The browser posts the data to a URL, and code at that URL has to read it, validate it, decide whether it’s spam, save it somewhere and tell you about it.

Traditional websites ran that code themselves, often a PHP script. Modern sites are frequently static files on a CDN, built with a site generator or a site builder, or generated by an AI tool. They have a front end but no place to run code. A form backend service supplies the missing half.

How form backends work

Here is the journey of one submission through a form backend like FormDoc:

1. The visitor submits. The browser sends the fields to the URL in the form’s action, such as https://api.formdoc.dev/v1/submit.
2. The form is identified. A hidden access_key field tells the service which form this is and whose inbox it belongs to.
3. Limits are checked. Oversized posts are refused (FormDoc allows 64 KB of text, 50 fields and 10,000 characters per field) and rate limits stop floods.
4. Spam is filtered. A hidden honeypot field catches simple bots, spam scoring looks for signs like many links or disposable email addresses, and an optional captcha adds a final check.
5. The submission is stored. FormDoc encrypts it before saving and deletes it automatically when the plan’s history period ends.
6. You’re notified. You get an email with the fields in a readable table. Spam is never emailed.
7. The visitor gets a response. A thank-you page, a redirect to your own page, or a success message inside the form.

All of this happens on the service’s servers. Your site stays exactly as simple as it was.

Notice what the access key does in this flow. It identifies the form, nothing more. Because it can only be used to send submissions, never to read them or change settings, it’s safe to leave in public HTML. That is what lets a form backend work without any secret on your site. With FormDoc you only get a key after confirming your email address, so the inbox that receives submissions is always one that agreed to it.

What the code looks like

The front end barely changes. You set the action, add the key and keep your fields:

<form action="https://api.formdoc.dev/v1/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
  <button type="submit">Send</button>
</form>

The step-by-step version, with labels and every reserved field explained, is in how to send an HTML form to email without PHP.

Form backend vs building your own

You can always write the back end yourself. The question is whether it’s worth it for the forms you have.

Task	Build your own	Form backend service
Receive and parse posts	Write and host an endpoint	Included
Validate size and fields	Your code	Included
Block spam	Honeypot, scoring, captcha, rate limits to build	Included
Send email reliably	Mail provider, domain setup, bounces	Included
Store data safely	Database, encryption, deletion	Included
Maintain over time	Updates, monitoring, outages	The service’s job
Custom business logic	Full control	Webhooks or JSON API

Building your own makes sense when the form is part of a larger application that already has a server, or when submissions must trigger complex logic inside your own systems. For contact forms, enquiries, sign-ups and feedback on a site without a server, a form backend saves you a project you’d otherwise keep maintaining.

What a good form backend service should offer

Not all services are the same. When you compare, look for:

• No server code required. Plain HTML should be enough.
• A public key that is safe to expose. It should only allow sending submissions, never reading them.
• Spam protection in layers, so you don’t have to force a puzzle on every visitor.
• Replies that reach the visitor. FormDoc sets the Reply-To header to the email the visitor typed, so pressing Reply just works.
• Clear data handling. Know where submissions are stored, whether they’re encrypted and when they’re deleted. FormDoc stores them encrypted in Mumbai, India, and keeps IP addresses only as a one-way hash.
• A way out to other tools. Webhooks, a JSON API or chat notifications for when email isn’t enough.
• Works with your stack. Static generators, frameworks and site builders should all be supported.

The features page lists what FormDoc does against each of these.

Who uses a form backend

Form backends suit anyone whose site has a form but no server:

• People with a portfolio or small business site on static hosting.
• Developers using a static site generator or a front-end framework.
• Site builder users who can paste custom HTML.
• Anyone who built a site with an AI tool and needs the form to actually deliver.
• Agencies that build many small sites and want one place to manage their forms.

Common questions

Is a form backend the same as a form builder?

No. A form builder gives you a hosted form, usually on its own page or in an embed, and controls how it looks. A form backend only handles what happens after submission, so you keep your own HTML, styles and layout.

Do I need JavaScript to use a form backend?

No. A plain HTML form with method="POST" works on its own. If you want the form to show success without leaving the page, FormDoc offers an optional script, and the form still works when JavaScript is off.

Can I send submissions somewhere other than email?

Yes. FormDoc sends email on every plan. On Pro you can also send submissions to a webhook, Slack or Google Sheets, and developers can use the JSON API to handle responses in their own code.

Try it on your site

The fastest way to understand a form backend is to use one. The docs have setup guides for most platforms, and you can get a free access key at https://app.formdoc.dev/new in a couple of minutes.