Compare
Formerie or your own form backend?
A form endpoint looks like an afternoon of work. The afternoon is the easy part. Here’s the rest, and when building it is still the right call.
In short
A self-built form backend gives you complete control, and you also own validation, spam defence, storage, retries, credentials, and the audit trail, for every site. Formerie provides those as a service behind a JSON API and SDK. Build it yourself when forms are core to your product or when your requirements don’t fit a hosted service.
When each one fits
Build it yourself when
Forms are core to your product, submissions must stay inside your own systems, or you already run this kind of infrastructure.
Use Formerie when
Forms are necessary but not your product, you run several sites, or you’d rather not maintain delivery code.
You can keep your UI
With the SDK or JSON API, your markup and state stay yours. Only the server side moves to Formerie.
What you’d take on
This compares a typical custom endpoint with Formerie as it works today. Your own build could do any of this; the question is who maintains it.
| Self-built | Formerie | |
|---|---|---|
| Control over behaviour | Complete | Within the product’s options |
| Server-side validation | You write it | Included |
| Spam checks and rate limiting | You write and tune it | Included |
| Storing submissions | You run it | Included |
| Retries for failed email | You write it | Included |
| Delivery log for non-developers | You build it | Included |
| Provider keys | You store and rotate them | Encrypted, held on the server |
| Ongoing cost | Your team’s time and hosting | Free plan; listed prices not charged during early access |
Spend that afternoon on your product instead.
Keep your UI and send the submissions to Formerie.