Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Building your own form-handling API route is easy to start and expensive to finish. Here's how to actually weigh the hours against a hosted form backend.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Building your own contact form API is worth it only if you have unusual requirements or are doing it to learn. For most production sites, the ongoing maintenance of email delivery, spam filtering, and storage costs more engineering time than a hosted form backend.
Writing a route handler that accepts a POST and forwards it to an email API is genuinely quick — an hour, maybe two, if you've done it before. That's the part everyone estimates when they decide to build their own. It's also the smallest part of the job.
The parts that take real time are the ones you don't think about until a form starts getting real traffic:
A fair comparison isn't "how long to send my first test email" — it's total engineering time over a year, including maintenance. A rough version: initial build (spam handling, storage, an inbox view, autoresponders) plus a few hours a quarter keeping it working. That adds up to real cost, paid by whoever owns the codebase, indefinitely.
A hosted form backend like FormBridge collapses that into pointing your form's action at an endpoint (https://app.formbridge.ai/api/forms/fb_8h2k9p) — no SDK, no required field naming, any field name works. Spam scoring, notification email, and an inbox come with the endpoint.
Outside of those, most production sites are better served by not rebuilding a solved problem. The free tier of a hosted backend costs nothing up to 1,000 submissions a month — cheaper than the first afternoon of building your own.
A basic version — accept a POST, validate input, send an email — can be working in an afternoon. The real cost shows up later: spam filtering, retry logic, bounce handling, file uploads, and an inbox UI typically add days to weeks of work, plus ongoing maintenance whenever a dependency or provider changes.
When your requirements are genuinely unusual (custom routing logic, a compliance constraint that rules out third parties, or you're building the form pipeline as the product), or when the goal is explicitly to learn how the pieces fit together. For a typical marketing site or app contact form, that complexity isn't buying you anything.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.