Lead pipeline
Every submission becomes a tracked lead
New, Contacted, and Converted stages in one dashboard. See active enquiries and conversion rate without counting manually.
What Is a Form Backend?
A form backend is the server side infrastructure that receives, stores, and processes the data submitted through your HTML form.
When someone fills out a contact form on your website and clicks submit, their browser sends the data to a URL specified in your form action attribute. Without a backend to receive that request, the data goes nowhere.
Static sites, landing pages, and portfolios built on GitHub Pages, Netlify, Vercel, Cloudflare Pages, or plain HTML have no server side code. They cannot process form submissions on their own.
A form backend service like Formgrid acts as that server. You point your form action at a Formgrid endpoint URL. Every submission is received, stored, and forwarded to you automatically. No server to configure. No database to manage. No backend code to write or maintain.
Why Most Developers Need a Form Backend Service
- Static Sites Have No Server. GitHub Pages, Netlify, Vercel, Cloudflare Pages, and plain HTML files cannot process form submissions. The moment a user clicks submit the browser has nowhere to send the data. You need a form backend to receive it.
- Building One From Scratch Takes Too Long. Setting up a Node.js endpoint, configuring email, handling spam protection, storing submissions in a database, and maintaining the server takes days of work for something as simple as a contact form. That overhead is never worth it.
- Most Form Backends Stop at the Inbox. Basic form backends forward submissions to your email and nothing else. There is no way to track which leads you followed up on, where they came from, or what happened after the email arrived. Formgrid fixes this.
Compare Formgrid with a popular hosted option on our Formspree alternative page.
How Formgrid works
Four steps from zero to production. Step four mentions Google Sheets sync when you want rows without opening your inbox.
Create a form in the dashboard
Name it, pick notification settings, and note the unique endpoint path Formgrid assigns.
Copy the HTTPS endpoint URL
You will paste this value into the action of any HTML form that should post here.
Ship your static HTML unchanged except for the action URL
Jekyll, Hugo, Astro, Eleventy, or hand written pages all behave the same way.
Route submissions to email, the dashboard, and optional Sheets
Turn on Google Sheets sync from the integration screen when your ops team lives in a spreadsheet.
Minimal HTML example
index.html
<form action="https://formgrid.dev/api/f/your-form-id" method="POST">
<input type="text" name="name" placeholder="Your name" required />
<input type="email" name="email" placeholder="Email" required />
<textarea name="message" placeholder="Message"></textarea>
<button type="submit">Send</button>
</form>Replace your-form-id with the identifier from your workspace.
