Formserve
Features Templates Pricing Docs Blog FAQ
Sign in Create endpoint

Alternative comparison

Formserve vs Netlify Forms

Netlify Forms is genuinely convenient when your site already lives on Netlify - forms just work at build time with a single attribute. The catch is that your form handling is now coupled to your host. Formserve is a host-agnostic backend, so the form keeps working no matter where you deploy.

Try a working endpoint View integrations

§ 01 · Why Why teams switch to Formserve

Your host stops being a lock-in

Netlify Forms only capture submissions on builds deployed to Netlify. Move that site to Vercel, Cloudflare Pages, GitHub Pages, or S3 and the form silently stops working. A Formserve endpoint is just a URL, so the form is portable across every host.

One backend for a mixed fleet

Agencies and teams rarely host every site in one place. Formserve gives you the same endpoint model, inbox, and integrations across a fleet that spans several hosts, instead of one workflow on Netlify and something else everywhere else.

Routing beyond the deploy platform

Send each submission to email, Slack, Google Sheets, a CRM, or a webhook from one endpoint, without wiring it through Netlify functions or add-ons.

§ 02 · Compare What changes when you use Formserve

Formserve is intentionally not a form builder. It is the backend, inbox, workflow, and handoff layer for forms you already have.

Capability Formserve Netlify Forms
Works regardless of where the site is hosted Yes - any host No - Netlify deploys only
Zero-config when already on Netlify Requires adding an endpoint URL Yes - built into the platform
Automatic form detection at build time No - you set the form action Yes - detected from HTML on deploy
Survives a migration to another host Yes - endpoint is unchanged No - handling must be replaced
Invisible spam protection without CAPTCHA Yes - honeypot and rate limiting Yes - honeypot and reCAPTCHA
Business-owner inbox separate from build settings ✓ No - lives in the Netlify dashboard
Per-submission delivery timeline across integrations ✓ Limited
Reuse one endpoint across many client domains Yes - multiple allowed domains Tied to each Netlify site

§ 03 · Decision Choose Formserve when the form should outlive the hosting decision, and stay with Netlify Forms when everything already lives on Netlify.

Netlify Forms are a great fit for the case they were built for. If your site is on Netlify and staying there, adding a netlify attribute to a form and getting submissions with no separate service is hard to beat for convenience.

The risk is coupling. Your lead capture is now a property of your hosting provider, not of your project. The day you move a site to Vercel for edge functions, to Cloudflare Pages for its CDN, or to plain S3 and CloudFront to cut cost, the forms stop working and nobody notices until a lead goes missing. That is a real switching cost hiding inside a convenience.

Formserve decouples the two. The form posts to an endpoint URL that has nothing to do with where the HTML is served, so you can redeploy or re-platform freely and the backend, inbox, and integrations stay exactly the same. If you are certain you will never leave Netlify, that portability is not worth much - but few projects can promise that.

Portable by construction

The endpoint is a URL, not a platform feature. The same form works on Netlify today and Cloudflare Pages tomorrow with no change.

One workflow across a fleet

Manage forms for many sites on many hosts from a single dashboard, instead of per-host handling that differs site to site.

Handoff without infrastructure access

A business owner reads leads in the Formserve inbox without ever touching build settings or a hosting dashboard.

No CAPTCHA required

Spam is handled invisibly with a honeypot and per-endpoint rate limiting, so you are not adding friction to protect the form.

When Netlify Forms may still be enough

Netlify Forms is the right choice when every site you run is hosted on Netlify and will stay there, when you want truly zero-config form capture with nothing extra to sign up for, or when build-time form detection and the tight dashboard integration outweigh any concern about portability.

§ 04 · FAQ Common questions

What actually happens to a Netlify form if I move off Netlify?
It stops capturing submissions. Netlify detects and processes forms only on deploys served by Netlify, so on another host the POST has nowhere to go. A Formserve endpoint keeps working because it is independent of the host.
Can I keep hosting on Netlify and still use Formserve?
Yes. Formserve does not care where the HTML is served. Many users stay on Netlify for hosting and simply point the form action at Formserve so the backend is portable if that ever changes.
Does Formserve work on Vercel, Cloudflare Pages, GitHub Pages, and S3?
Yes. Any host that can serve an HTML form works, because the form just POSTs to the Formserve endpoint URL over HTTPS.
Is setup as simple as Netlify's single attribute?
Almost. Instead of a netlify attribute you set the form's action to your endpoint URL and add a honeypot field. It is one URL and one hidden input rather than fully automatic, in exchange for host independence.
Do I lose Netlify's spam filtering?
No. Formserve includes an invisible honeypot and per-endpoint rate limiting, and you can layer stricter protection per endpoint, without forcing a visible CAPTCHA on visitors.