Skip to content
FormSubmit
Comparisons

Best Form Backend Services: A Practical Buyer's Guide

Choosing the best form backend? Compare hosted backends, platform forms, form builders and DIY serverless on spam protection, uploads, pricing and privacy.

FormSubmit Team

6 min read

Comparison checklist of form backend services weighing spam protection, file uploads, pricing and privacy

The best form backend is the one that works with your stack out of the box, stops spam without hurting real visitors, delivers submissions reliably to the tools you already use, and has predictable pricing and limits. For most static sites and marketing sites, that means a hosted form backend; for teams with custom logic, a DIY serverless handler can make more sense.

This guide does not hand out scores or rankings. Instead it gives you the criteria that matter, the four main categories of form backend services, and a checklist you can apply to any vendor, including us.

What to evaluate in a form backend

1. Spam protection

Spam is the problem that ruins most contact forms. Look for layers rather than a single trick:

  • A honeypot field that is silently dropped
  • A time trap that flags submissions sent faster than a human types
  • Content heuristics (link counts, known spam phrases)
  • Rate limiting per IP
  • Optional captcha support: reCAPTCHA, hCaptcha or Cloudflare Turnstile
  • Ask whether spam counts toward your quota

Our honeypot vs captcha guide explains how these layers work together.

2. Integrations and delivery

Email is the baseline. Beyond that, check for signed webhooks (so your receiver can verify requests), plus direct connectors for the tools you use, such as Slack or Google Sheets. Two questions people forget: are integrations gated behind higher plans, and are failed deliveries retried automatically?

3. File uploads

If you need resumes, briefs or screenshots, confirm the per-file maximum, total storage, whether files are private, and how links in emails are protected. Also check whether plain HTML uploads work or whether JavaScript is required for larger files.

4. Pricing model and limit behavior

Pricing pages show prices; few explain what happens at the limit. The options vary across vendors:

  • Submissions over the limit are rejected
  • Submissions are stored but held until you upgrade
  • Forms stop working until the next billing cycle

For a client site, a form that silently stops accepting leads is worse than a slightly higher bill. Read the docs, not just the pricing table.

5. Data privacy

Look for a published privacy policy and DPA, clear retention settings, and details on how personal data like IP addresses is stored. If you work under GDPR, our GDPR contact form guide covers what to ask.

6. Developer experience

Good DX means: a plain HTML snippet that works on first try, JSON responses for fetch, CORS support, clear error codes, and a test button so you are not submitting your own contact form ten times.

The four categories of form backend services

Hosted form backends

Services such as Formspree, Basin, Getform, FormSubmit and others give you an endpoint URL; you keep your own markup. They work with any site: static HTML, WordPress, Webflow, React, Astro and AI-built sites. This category is usually what people mean by "form backend services." If you are looking for a Formspree alternative, you are comparing within this group, so focus on the criteria above rather than headline prices.

Platform forms

Some hosts, Netlify Forms being the best-known example, detect forms in your HTML at deploy time and collect submissions. Setup is minimal if you already host there. The trade-off is portability: the form is tied to that platform, and features and limits are whatever the platform offers.

Form builders

Google Forms, Typeform, Tally, Jotform and similar tools host the form itself. They shine for surveys, quizzes and multi-step flows with conditional logic. The trade-off is that the form is embedded (often as an iframe) or lives on the vendor's page, so it does not fully match your site's design, and you have less control over markup and accessibility.

DIY serverless

Write a function on Vercel, Netlify, Cloudflare Workers or AWS Lambda that parses the request and sends an email through a transactional email provider. You get full control. You also own spam filtering, storage, file handling, retries and the admin view.

Form backend comparison checklist

Use this table as a scorecard. Fill in the last column for each vendor you are considering by checking their own site.

CriterionWhy it mattersWhat good looks like
Plain HTML supportWorks without JS, on any hostaction + method="POST" is enough
Spam layersFewer junk emails, fewer false positivesHoneypot, time trap, heuristics, rate limit, optional captcha
Spam and quotaBots should not burn your planSpam does not count toward limits
Limit behaviorLeads should never vanishSubmissions kept, clear alerts before the limit
Integrations on all plansNo surprise upgradesWebhooks and connectors on entry plans
Signed webhooksVerify requests are genuineHMAC signature header with timestamp
File uploadsResumes, briefs, imagesPrivate storage, signed expiring links
Domain allowlistStop endpoint reusePer-form allowed domains
Retention controlsData minimizationConfigurable deletion period
ExportNo lock-inCSV and JSON
BrandingClient-facing workNone on any plan

Who each type suits

  • Freelancers and agencies shipping marketing sites: hosted form backends. One setup pattern works across every client stack, and white-label options matter.
  • Static site and JAMstack developers: hosted form backends, or platform forms if you are committed to one host. See forms for static sites.
  • Teams running surveys, quizzes or payment forms: form builders, because they handle logic and multi-page flows.
  • Product teams wiring forms into their own app: DIY serverless or your existing API, because the data belongs in your database.
  • Small business owners on WordPress: a hosted form backend avoids another plugin to update; see WordPress sites.

Where FormSubmit fits

FormSubmit is a hosted form backend. Facts you can compare against the checklist:

  • Plans: Free ($0, 1 form, 50 submissions a month), Starter ($5/month, 2 forms, 1,000), Pro ($15/month, 10 forms, 5,000) and Business ($50/month, unlimited forms, 10,000). Yearly billing gives two months free.
  • Every plan, including Free, includes email notifications, layered spam protection, reCAPTCHA, hCaptcha and Turnstile support, signed webhooks, Slack, Discord, Google Sheets, Airtable, Mailchimp and Kit integrations, file uploads, a domain allowlist and CSV/JSON export.
  • Spam does not count toward your quota. Over the monthly limit, submissions are still stored but locked until you upgrade or the month resets, and you are emailed at 80% and 100%.
  • No FormSubmit branding on thank-you pages, hosted forms or emails, on any plan.

What it does not do: there is no conditional logic, multi-page forms or payment collection, and no public REST API for reading submissions (use webhooks, integrations or export). If you need those, a form builder or a custom backend may suit you better.

How to choose the best form backend in an afternoon

  1. List your must-haves: file uploads, specific integrations, captcha, branding removal.
  2. Shortlist two or three vendors from the category that fits your situation.
  3. Build the same test form for each and submit valid data, a honeypot hit and an oversized file.
  4. Check how each handles email delivery, the dashboard and the error responses.
  5. Read the limit behavior and privacy terms, then decide.

For side-by-side notes on specific services, see our comparison pages. To try FormSubmit against your checklist, build a form with the free form generator and compare plans on the pricing page.

Last updated .

Frequently asked questions

What is the best form backend for a static site?

The best fit is usually a hosted form backend that works with plain HTML, includes layered spam protection and sends email notifications without setup. If you are locked into one host and need only basic collection, that host's built-in forms may be enough.

How do I evaluate a Formspree alternative?

Compare the same criteria you would for any form backend: spam protection layers, file upload limits, which integrations are included on which plans, what happens at the submission limit, and data privacy terms. Check each vendor's site for current pricing.

Are free form backends good enough?

For a personal site or a low-traffic portfolio, often yes. Check the monthly submission cap, whether spam counts toward it and whether branding appears on emails or thank-you pages.

Should I just write a serverless function instead?

It is a good option if you need custom logic or already run backend code. For a contact form, the hidden cost is email deliverability, spam filtering, storage and retries, which you then maintain yourself.

Related resources

Keep reading

Your form backend is 60 seconds away

Sign up with Google or email, create a form, paste the endpoint. Free forever for small sites — no credit card.