send.webforms.toRead the docs →

Comparison

The FormBackend alternative for forms that go more than one place

FormBackend covers rules-engine and white-label features across a wide tier spread. WebForms adds conditional routing to more destination types in one submission.

Start freeSee pricing

FormBackend runs a conventional tiered model with a genuinely wide feature spread: a rules engine, custom email sender domains, project grouping and team members all appear, but each is gated to a specific tier, with white-labelling and custom domains reserved for the top Business plan.

Their integration list leans toward Slack, Google Sheets and Zapier rather than a native Discord or Telegram destination, so reaching either of those means a webhook and an automation platform in between rather than a direct connection.

WebForms includes email, Slack, Discord, Telegram and webhooks as native destinations from the start, with routing rules deciding where a submission goes and a delivery log recording what happened at every one of them.

When to stay with FormBackend

Switching has a real cost. These are the cases where we would not bother.

WebForms vs FormBackend

Capability by capability, then their published prices. Anything we quote for FormBackend was read off their own pricing page on the date shown, but prices change - check their pricing directly before deciding.

CapabilityWebFormsFormBackend
SetupPoint form action at your endpoint. Works on fully static sites.Same endpoint-per-form model, plus an optional hosted form builder.
Submission storageStored, searchable, exportable as CSV or JSON.Stored and exportable.
Fan-out per submissionEmail, Slack, Discord, Telegram and webhooks from one submission.Slack and Google Sheets on the Business tier; webhooks and Zapier from Simple up.
Conditional routingRoute on field values to different destinations per rule.A rules engine and custom email routing from the Freelancer tier up.
Delivery logPer-destination status, response and retry history.No per-destination delivery log documented.
Spam filteringHoneypot, Turnstile, rate limits and an AI classifier that learns from your marks.Spam protection included on every paid tier.
White-label sendingCustom from-name on paid plans; full white-label as an add-on.Custom email sender domains and white-label notifications on the Business tier only.
API accessRead-only Submissions API with scoped keys.API access from the Freelancer tier up.

FormBackend pricing

Read from their pricing page on . Prices in USD.

PlanPriceSubmissions
Free$01 form, plus a separate free hosted-builder plan with unlimited submissions50 / month
Simple$5 / month$4.17 / month billed yearly1,000 / month
Freelancer$14 / month2 months free billed yearly5,000 / month
Business$50 / month2 months free billed yearly10,000 / month

Moving from FormBackend

  1. Export your submissions

    Download your submission history from FormBackend before changing anything.

  2. Create matching forms

    Add one WebForms form per FormBackend form and copy each endpoint URL.

  3. Update the action attributes

    Swap the endpoint URL in your markup. Field names carry over without modification.

  4. Rebuild destinations, then add routing

    Recreate the integrations you rely on, then add routing rules if a form needs different destinations depending on what was submitted.

Try it without deciding anything

The free plan includes 300 submissions a month, unlimited forms, email delivery, stored submissions and spam filtering, with no card required and no expiry. Point one form at it and keep FormBackend running on the others until you are convinced.

Questions

The markup change is one line per form, since both use a plain endpoint URL. Recreating destinations in the dashboard is the bulk of the work.

Other comparisons