What is a form backend?

A form backend is a hosted service that receives, checks, stores and forwards what people type into your forms. Here is what it does and when you need one.

You can build a good-looking form with nothing but HTML and CSS, yet it will not do anything when someone presses submit. The missing piece is the part that receives the data, and a form backend is one way to get it without writing server code.

This article explains the term in plain language, lists the jobs a form backend does, and covers the cases where you do not need one.

The short definition

A form backend is a hosted service that gives you a URL. You put that URL in your form's action attribute, and the service handles everything that happens after the visitor presses submit.

Your form stays yours. You write the HTML, choose the fields and style it however you like. The service only receives what the form sends.

With FormDB, the URL looks like this:

<form action="https://api.formdb.io/f/your-form-id" method="POST">
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

What a form backend does

Receiving a form submission sounds like one task. In practice it is six.

1. Receive

The service accepts the HTTP request your visitor's browser sends. HTTP is the protocol browsers use to talk to servers, and a form submission is an HTTP request with the field values in its body.

Forms can arrive in several encodings. A standard HTML form sends URL-encoded text. A form with file inputs sends multipart/form-data. JavaScript code often sends JSON. FormDB accepts all three at the same endpoint. The details are in the endpoint reference.

2. Validate

Validation means checking that the data is acceptable: the email field contains an email address, required fields are filled in, a number is within range.

Browsers can do some of this with attributes like required, but those checks run on the visitor's device and can be skipped. A form backend repeats the checks on the server, where the visitor cannot turn them off. In FormDB you describe your fields in a form builder, and every submission is checked against that description. A submission that fails gets a 422 response that lists the problem for each field. We explain why this matters in client-side validation is not enough.

3. Filter

Any public form attracts spam, and every submission passes through the form backend, so that is the natural place to filter it.

FormDB has several layers: a honeypot field that catches bots which fill in everything, an optional captcha (a built-in one that needs no keys, or your own reCAPTCHA, hCaptcha or Cloudflare Turnstile keys), keyword-based content filters and your own rules for words, links, countries, languages and duplicates that move suspicious submissions to a Spam folder, IP address blocking, and a list of websites that are allowed to post to the form. See spam protection for how they fit together.

4. Store

Each accepted submission is saved so you can read it later, search it and export it. Without this, a submission exists only as an email that might land in a junk folder.

In FormDB the inbox has folders for Inbox, Spam and Trash, a search box, read and unread states, and CSV or JSON export. The submissions inbox page covers each of these.

5. Notify

Most people want to know when a submission arrives. A form backend sends an email with the submitted values so you do not have to keep checking a dashboard.

FormDB emails the workspace owner for every accepted submission that is not flagged as spam, and can post to Slack, Discord or Telegram. Paid plans can add extra recipient addresses per form and send an automatic reply to the person who submitted. If the form has a field named email, that address becomes the Reply-To of the notification, so replying goes to the person who wrote to you.

6. Forward

Finally, the data often needs to go somewhere else: a spreadsheet, a project database, your own application.

FormDB sends webhooks on every plan. Paid plans add direct connections to Google Sheets, Notion and Airtable, a Stripe integration for recording payment status, a REST API and a Zapier integration. A webhook is an HTTP request the service sends to a URL you choose each time a submission arrives, which is how you connect a form to anything that has no direct integration. Start with webhooks if that is what you need.

When you need a form backend

A form backend fits well when:

  • Your site is static. Sites built with a static site generator, or plain HTML files on a static host, have no server code to receive a form.
  • You build sites for other people. Clients want a contact form that works and an inbox they can read. They do not want to maintain a server.
  • You have a server but do not want form plumbing in it. Spam filtering, storage, email delivery and retries are a lot of code for a contact form.

When you do not need one

A form backend is not the right tool for everything.

  • Logins and account forms. Signing in, registering and changing a password must be handled by the application that owns the user accounts.
  • Forms that drive your own application logic. If a submission has to check stock, create an order or update a record in your database in the same request, that logic belongs in your application.
  • You already use a full-stack framework and want everything in one place. If your framework handles form posts and you are happy maintaining spam filtering and email delivery yourself, a separate service adds little.

It is also worth knowing what a particular service does not do before you choose it. FormDB, for example, does not host the form page for you. It is a backend for forms that live on your own site.

What to check when choosing one

These questions apply to any form backend:

  • Does it work without JavaScript? A plain HTML post should be enough. JavaScript should be optional.
  • Is validation done on the server? Browser checks alone are not protection.
  • What happens to spam? Moving suspected spam to a folder is safer than deleting it, because filters make mistakes.
  • What happens at the plan limit? Find out whether extra submissions are rejected, queued or billed.
  • How long is data kept? Retention periods differ between plans.
  • Can you get your data out? Look for export and for webhooks or integrations.

For FormDB the answers are: yes, yes, a Spam folder, held until you upgrade or the quota resets and never billed, 30 days on the Free plan and unlimited on paid plans, and CSV or JSON export and webhooks on every plan with more integrations and a REST API on paid plans.

How FormDB fits

Job

In FormDB

Receive

One endpoint per form, accepting HTML form posts, file uploads and JSON

Validate

Field types and rules defined in the form builder, enforced on the server

Filter

Honeypot, captcha, content filters and rules, IP blocking, allowed domains

Store

Inbox with search, Spam and Trash folders, CSV and JSON export

Notify

Email to the workspace owner, Slack, Discord and Telegram, extra recipients and auto-replies on paid plans

Forward

Webhooks on every plan, Google Sheets, Notion, Airtable, Stripe, REST API and Zapier on paid plans

The Free plan includes 250 submissions a month with 30-day retention, 100 MB of file storage, one webhook per form and Slack, Discord and Telegram notifications. Paid plans start at 2,500 submissions a month. Current plans are on the pricing page.

Try it with one form

The fastest way to understand a form backend is to point one form at it. How it works describes the path a submission takes through FormDB, and you can create a free account to get an endpoint and try it on a page you already have.

Your form can be livebefore your coffee is cold.

Create a form, paste one URL and send yourself a test. The Free plan covers 250 submissions a month, with no credit card required.