Netlify Forms Alternative
Form handling built into Netlify hosting — and only Netlify hosting
Why Developers Move to Formboost
Netlify Forms only exists where the site is built and hosted by Netlify. Move to Vercel, Cloudflare Pages, GitHub Pages or a VPS and the form handling has to be rebuilt; forms rendered after the build, or by a JavaScript framework at runtime, need workarounds for build-time detection. Formboost is an endpoint that does not care where the page is hosted, works on a form added at runtime, and puts Slack, Discord and Telegram delivery on its free plan.
What Netlify Forms Does
Netlify Forms handles submissions for sites deployed on Netlify. You add a `netlify` (or `data-netlify="true"`) attribute to a form, Netlify's build detects it, and submissions appear in the Netlify dashboard with email, Slack and outgoing-webhook notifications. Spam is filtered with Akismet plus an optional honeypot or reCAPTCHA.
What it costs to switch
Nothing, to start. Formboost's free plan covers 10 forms and 500 submissions a month with no card, and email, Slack, Discord and Telegram delivery are all available at that tier — one destination per form, so you can move one form across and keep it running for free while you check the submissions land where you expect. Custom webhooks start on Starter at $9/mo.
Netlify prices Forms as an add-on to its hosting plans and the levels change — check netlify.com/pricing for current numbers before deciding. See the full pricing and feature comparison → · Netlify Forms's current pricing →
Where Formboost Differs
Host-independent: the same endpoint works on Netlify, Vercel, Cloudflare Pages, GitHub Pages or a bare server
No build-time detection — a form added by JavaScript at runtime works the same as static markup
500 free submissions a month across 10 forms, against 100 across the account
Slack, Discord and Telegram delivery on the free plan; custom webhooks, Google Sheets, Zapier and n8n from Starter at $9/mo
Spam screening with a score and reason on every submission, and an AI model from Starter — no Akismet account
No file uploads yet (on the roadmap) and no read API — Netlify has both
Netlify Forms vs Formboost in detail
In short
Netlify Forms is the path of least resistance if you're already on Netlify. But that's also its biggest problem: it only works on Netlify. The moment you deploy somewhere else — Vercel, Cloudflare Pages, GitHub Pages, your own VPS — you're on your own.
Key takeaways
- •Netlify Forms only works for sites hosted on Netlify, detected at build time from a form attribute.
- •Moving hosts means rebuilding form handling; an external endpoint moves with you.
- •Netlify's free tier caps submissions per month across the whole account.
- •Formboost's free plan is 500 submissions a month across 10 forms on any host.
Where Netlify Forms Falls Short
Hosting lock-in. Netlify Forms is exclusive to Netlify deployments. If you ever migrate hosts, or if your team uses a different provider, you need a full form backend replacement.
100 submissions/month free tier. Sounds generous, but a single active contact form on a real project can exceed that quickly. The next tier ($19/month) is expensive for what you're getting.
Tied to Netlify's build. Form detection happens at deploy time on Netlify's own infrastructure, so the form only exists where the site is hosted. Moving hosts means rebuilding the form handling.
Spam is handled by Akismet. Netlify runs submissions through Akismet and lets you add a honeypot field or reCAPTCHA. Formboost screens with its own heuristics on every plan and an AI model from Starter, records a score and reason on each submission, and never asks your visitors to solve a CAPTCHA.
Build-time dependency. Netlify Forms requires a netlify attribute on your HTML form at build time. Dynamic forms or forms added after the build don't work without workarounds.
Formboost: Works Anywhere
Formboost is a standalone form backend — no platform dependency, no build step, no attribute magic:
<form action="https://formboost.app/f/YOUR_ID" method="POST">
<input type="text" name="name" required />
<input type="email" name="email" required />
<textarea name="message"></textarea>
<button type="submit">Send</button>
</form>Works identically on Netlify, Vercel, GitHub Pages, Cloudflare Pages, or a bare Nginx server.
Feature Comparison
| Feature | Formboost | Netlify Forms |
|---|---|---|
| Free submissions/month | 500 across 10 forms | 100 across the account |
| Works on any host | Yes | Netlify only |
| Runtime-rendered forms | Yes | Needs a build-time workaround |
| Slack / Discord / Telegram | Free plan | Slack and email notifications |
| Custom webhooks | Starter ($9/mo) | Outgoing webhook notifications |
| Spam screening | Heuristics free, AI from Starter | Akismet, optional honeypot / reCAPTCHA |
| File uploads | On the roadmap | Yes |
| Read API | None — dashboard and CSV | Netlify API |
Why Formboost
- •No hosting lock-in — deploy anywhere, your form backend stays the same
- •Webhooks from Starter, chat delivery free — automations without being tied to one host
- •[Spam screening](/features/spam-protection) with a score and reason — no Akismet account, no CAPTCHA, zero config
- •One integration — works in any environment, including dynamic/SPA apps
Next steps
- •Migrate from Netlify Forms — the step-by-step version
- •Formboost vs Netlify Forms — the full matrix
- •Set up your first endpoint
Switching from Netlify Forms?
Most forms migrate in minutes. See the full step-by-step guide.
Frequently Asked Questions
Common questions about switching from Netlify Forms
Can I keep my existing form HTML when moving from Netlify Forms?
Yes. Formboost accepts an ordinary HTML form post, so in most cases the only edit is the form's action attribute — point it at your Formboost endpoint and leave the field names as they are. Your markup, styling and client-side validation are unaffected, and the field names you already use become the column names on your submissions.
Will I lose the submissions already stored in Netlify Forms?
Formboost does not import historical submissions from Netlify Forms, so export them before you close the account — every provider offers a CSV export, and it is the one step that is awkward to undo. Formboost starts collecting from the moment you repoint the form, and you can run both endpoints in parallel for a few days if you would rather overlap than cut over.
How long does moving one form actually take?
Minutes for the form itself: create the endpoint, change the action URL, submit a test entry and confirm it appears in the dashboard. Reconnecting notifications takes longer than the form does — a Slack, Discord or Telegram destination is a pasted webhook URL, and Google Sheets is a Google sign-in.
Do I need a credit card to try Formboost?
No. The free plan covers 10 forms and 500 submissions a month with no card and no expiry, and email, Slack, Discord and Telegram delivery are all available at that tier, one destination per form — enough to move a real form across and run it before deciding anything.
Ready to try Formboost instead of Netlify Forms?
Free to start, no credit card required.