Netlify Forms Alternative: OperatorStack vs Netlify Forms

On April 14, 2026, Netlify changed what a form submission costs. The changelog is one line: "Now form submissions are free across all Credit plans. Previously, each form submission cost 1 credit." Most of the "Netlify Forms is getting expensive" posts you can find were written before that.

So this comparison does not get to be about price, the same way the Tally comparison does not. If you deploy on Netlify and you want a contact form that emails you, Netlify Forms is two HTML attributes and costs nothing, and you should use it.

The argument for an alternative is about who creates the form endpoint. With Netlify, you do not. Your build does, by reading your HTML at deploy time, and everything awkward about Netlify Forms follows from that one fact.

Your Build Creates the Form, Not You

Turning on a Netlify form is one attribute:

<form name="contact" method="POST" data-netlify="true">
  <input name="email" type="email" />
  <button>Send</button>
</form>

At deploy time, Netlify's post-processing parses the static HTML it is about to serve, finds forms carrying data-netlify="true" (or the bare netlify attribute), strips that attribute out, and injects a hidden field:

<input type="hidden" name="form-name" value="contact" />

That injected field is what routes the submission. The name on the <form> becomes the form's identity in the Netlify UI, and two forms with the same name are the same form.

This is genuinely elegant for a hand-written HTML page. It is also the source of every Netlify Forms problem people actually hit, because a parser that reads your built HTML can only see forms that exist in your built HTML.

The Hidden Duplicate Form

If your form is rendered by React, Vue, Svelte, or any client-side framework, the parser sees nothing at deploy time. No endpoint gets created. The form renders fine in the browser, the submit handler fires, and the POST lands on a route that does not handle it.

Netlify's documented fix is to ship a second, hidden copy of the form in your static HTML:

<form name="pizzaOrder" data-netlify="true" style="display:none;">
  <input name="order" type="text" />
  <input name="form-name" type="hidden" value="pizzaOrder" />
</form>

Then your real component has to include the form-name field itself:

<form name="pizzaOrder" method="post" onSubmit={handleSubmit}>
  <input type="hidden" name="form-name" value="pizzaOrder" />
  <input name="order" type="text" onChange={handleChange} />
  <input type="submit" />
</form>

Two declarations of the same form, in two files, in two languages, that have to agree on the form name and on every field name.

The AJAX Body Is Not JSON

The other thing that costs people an afternoon: Netlify's form endpoint takes URL-encoded bodies, not JSON. The documented submit handler is this shape, and the encoding is not optional:

const handleSubmit = (event) => {
  event.preventDefault();
  const formData = new FormData(event.target);

  fetch("/", {
    method: "POST",
    headers: { "Content-Type": "application/x-www-form-urlencoded" },
    body: new URLSearchParams(formData).toString(),
  });
};

Note the target: "/", your own site root. That is the whole architecture in one line. There is no form service URL, because the endpoint is your deployment. Netlify's edge intercepts the POST before your app sees it.

Which answers the portability question before you ask it. Move the site to Vercel or Cloudflare Pages and that fetch("/") starts posting into your own app, which has no idea what to do with it.

Where the Submission Goes

An OperatorStack form has no build step in it. You create a form in the dashboard, get a key like frm_abc123, and point markup at the endpoint:

<form method="POST" action="https://api.operatorstack.dev/v1/f/frm_abc123">
  <input name="email" type="email" required />
  <input name="company" type="text" />
  <input type="hidden" name="_redirect" value="https://yoursite.com/thanks" />
  <button>Send</button>
</form>

The _redirect field is the no-JavaScript path: the endpoint answers with a 303 and the browser lands on your own thank-you page. Underscore-prefixed fields are treated as instructions and stripped from the stored data.

Or through the SDK, if the script tag is already on the page:

await OperatorStack.submitForm("frm_abc123", {
  email: "founder@example.com",
  company: "Acme",
});

The SDK call is the version that matters for this comparison, because of what it adds on the way out. submitForm attaches visitor_id: getOrCreateVisitorId() to the body before sending. That is the same visitor ID your page views were recorded under, so the submission arrives already attached to the session that produced it.

On the server, three things happen to that submission that do not happen on Netlify:

Netlify's submissions are a good list of submissions. They are just a list that has never seen your traffic, your referral codes, or your waitlist.

Side by Side

When Netlify Forms Is the Right Call

Three cases, and they are not edge cases.

You need file uploads. OperatorStack's endpoint parses multipart bodies but keeps only the string values, so a file is dropped rather than stored. Netlify takes the upload, up to 8 MB per request with a 30-second timeout and one file per input field. If your form collects a resume or a screenshot, this comparison is over.

You want spam handled for you. Every Netlify submission runs through Akismet before it reaches your verified list, and you can add a honeypot with one attribute, netlify-honeypot="bot-field", or a reCAPTCHA with data-netlify-recaptcha="true". That is a better out-of-the-box spam story than a honeypot and a rate limit.

Your site is hand-written HTML on Netlify and the form emails you. Two attributes, no script tag, no account anywhere else. Adding a tool to replace that is a downgrade.

The Actual Decision

Ask what you want to do with a submission a week after it arrives.

If the answer is "read it" or "reply to it," Netlify Forms already does that and costs nothing. If the answer involves the word "which" ("which campaign", "which page", "which of these people also joined the waitlist"), you need the submission joined to something, and Netlify's form store has nothing to join it to.