A Netlify Forms Alternative That Works on Any Host

Netlify Forms is a genuinely clever bit of design. Add data-netlify="true" to a form, Netlify's build step spots it in your HTML, and submissions start arriving. Nothing to configure, nothing to wire up.

That cleverness is also the reason people end up looking for something else.

Why People Leave

The submission cap is what usually starts it. A hundred a month sounds like plenty until a contact form gets discovered by bots, or one post does well and a week's worth of traffic arrives on a Tuesday. Now you're on a paid plan for a feature that wasn't why you picked the host.

The bigger issue is that the form only works on Netlify. Detection happens in Netlify's build system, so if you move to Vercel or Cloudflare Pages or an S3 bucket, the markup comes with you and the submissions just stop. No error, no warning — the form posts into the void. Your contact form has quietly become an argument against changing hosts, which is exactly backwards for something that's meant to be one <form> tag.

And because detection means parsing your built HTML, forms rendered by JavaScript often aren't detected at all. Debugging that involves reading build logs and guessing, which is a strange way to spend an afternoon.

The Portable Version

The alternative is boring in a good way: point the form at a URL.

<form action="https://api.bluejayrelay.com/f/frm_yourtoken" method="POST">
  <input name="email" type="email" required>
  <textarea name="message"></textarea>
  <button type="submit">Send</button>
</form>

No build-step magic, no attribute that only means something on one platform, no detection to fail. That form works identically on Netlify, Vercel, GitHub Pages, Cloudflare Pages, an S3 bucket, or a laptop serving files with Python's HTTP module. Change hosts and nothing about it changes.

Side by Side

	Netlify Forms	Bluejay Forms
Works off Netlify	No	Any host
Setup	Build-time HTML attribute	Form action URL
Silent detection failures	Possible with JS-rendered forms	No detection step to fail
Spam protection	Honeypot, reCAPTCHA	Honeypot → content heuristics → CAPTCHA → AI scoring
File uploads	Yes	Yes
Autoresponder	No	Yes
Submission digest	No	Daily or weekly
CSV export	Yes	Yes
Origin restriction	No	Yes

Spam Is Where the Real Difference Is

Everyone offers a honeypot — a hidden field humans leave empty and lazy bots fill in. It catches the crude stuff and nothing more.

What I think matters more is having stages, so you can use only as much friction as a given form actually needs. Content heuristics run server-side, looking at link density and repetition and the usual spam tells, with nothing added to your page. Above that there's a Turnstile CAPTCHA for a form that's genuinely under attack, and above that an AI score for the borderline submissions the earlier layers can't call either way.

The point of the ladder is that most forms never climb it. You start with an invisible honeypot and only make real visitors do work if something specific goes wrong — rather than putting a CAPTCHA in front of every human forever because of bots you got in 2023. Stopping form spam without a CAPTCHA goes through the layers properly.

Migrating Takes About Two Minutes

Both are drop-in backends, so this is mechanical. Create a form, copy the endpoint, then swap data-netlify="true" (and the hidden form-name field, if you have one) for action="..." and method="POST". Set a notification email and a redirect URL if you want a thank-you page. Export your existing submissions from Netlify for your records, because they stay where they are.

Your field names, layout, styles, and validation don't change at all. The only thing that moves is where the browser posts.

When You Should Just Stay

If you're on Netlify, you expect to stay on Netlify, and you fit comfortably in the free tier — don't move. It's bundled, it works, and one fewer service in your stack is a real benefit that people undervalue.

Move when one of those stops being true. You're paying for submissions, you're eyeing another host, or the form has grown into something that needs actual spam handling and autoresponders and origin controls. That's when the coupling starts costing more than the convenience is worth.

---

Own your forms instead of renting them from your host. Try Bluejay Forms free.