Coder Legion - Recent posts tagged form

Slope Intercept Form with Gradient Descent

Wed, 27 May 2026 07:11:28 +0000

Hello, I'm Ganesh. I'm building git-lrc, an AI code reviewer that runs on every commit. It is free, unlimited, and source-available on Github. Star git-lrc on GitHub to help more developers discover the project. Do give it a try and share your feedback for improving the product.

Slope-Intercept Form equation

A residual is the difference between the actual y value and the predicted y value.

Residule = (Actual Y - Predicted Y)

Finally, the residual is squared, and the sum of all the residuals is calculated, which is called the Mean Squared Error (MSE).

(Residual)^2 is nothing but the vertical distance between the predicted line and the actual data points, squared.

The lesser the value, the greater the accuracy.

Using this Mean Squared Error (MSE), we can adjust the slope and y-intercept to minimize the error.

Conclusion

Will discuss Gradient Descent in the next part.

Any feedback or contributors are welcome! It’s online, source-available, and ready for anyone to use.

⭐ Star git-lrc on GitHub
Slope Intercept Form with Gradient Descent

Formspree Alternatives in 2026: Open Source, Cheaper, and Self-Hostable

Thu, 19 Mar 2026 13:54:51 +0000

If you've been using Formspree and recently looked at your bill or hit a submission wall, you're not alone. A lot of developers are actively searching for alternatives, and for good reason.

Formspree is a solid product. But its paid plans start at $10/month for only 200 submissions per month. Costs climb quickly as your submission volume grows. The free plan caps you at 50 submissions per month and only stores your submissions for 30 days. Meaning if you don't log in and export, you lose your data.

In this article I'll walk through the best Formspree alternatives in 2026, covering price, features, self-hosting options, and which one is right for your use case.

Why Developers Look for Formspree Alternatives

Before jumping into the list, here are the most common reasons people switch:

Price Formspree's free tier is limited and paid plans add up fast
No form builder — Formspree is purely a backend. If you need a shareable form link without writing HTML, you're out of luck
No self-hosting If you care about data ownership or GDPR compliance, Formspree gives you no option to run it yourself
30-day submission history on free plan Your data disappears if you don't export it in time
No open source option You're locked in. No transparency, no customisation

If any of those hit home, keep reading.

The Best Formspree Alternatives in 2026

1. Formgrid.dev: Form Builder + Form Backend in One Place

Best for: Developers who want a form backend AND non-technical users who need a shareable form link. Both in one tool.

What makes it different:

Most form tools pick a lane, either a form backend for developers or a no-code form builder for everyone else. Formgrid does both.

You can point your existing HTML form to a Formgrid endpoint URL, exactly like Formspree. Or you can use the drag-and-drop form builder, get a shareable link, and send it via WhatsApp or email without touching any code.

<!-- Your existing HTML form — unchanged -->
<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="Your Email" required />
  <textarea name="message" placeholder="Your Message"></textarea>
  <button type="submit">Send Message</button>
</form>

Key features:

Drag-and-drop form builder with shareable link
HTML form endpoint; works with any static site
Spam protection (honeypot + rate limiting)
Instant email notifications
File uploads
CSV export
Self-hostable with Docker
100% open source (MIT license)
GDPR friendly; no tracking, no data selling

Pricing:

Plan	Price	Submissions
Free	$0/month	50/month
Premium	$8/month	5,000/month
Business	$29/month	15,000/month

The bottom line: If you're paying $10/month for Formspree and only need a form backend, Formgrid gives you the same thing for $8/month, plus a form builder and self-hosting option that Formspree doesn't have.

formgrid.dev

Formgrid Landing Page:

Formgrid Dashboard:

Example Form Built By Formgrid:

2. Getform: Simple and Clean Form Backend

Best for: Developers who want a straightforward Formspree replacement with a clean dashboard.

Getform is a popular alternative that covers the basics well. It stores submissions, sends email notifications, and supports file uploads. The interface is clean and developer-friendly.

Key features:

HTML form endpoint
Email notifications
File uploads
Webhooks
Zapier integration

Pricing: Starts at $19/month for paid plans. Has a free tier.

Drawback: No form builder. No self-hosting. Slightly more expensive than Formgrid for similar submission limits.

3. Basin: Minimal and No-Frills

Best for: Developers who want the simplest possible form backend with no distractions.

Basin is intentionally minimal. Point your form at their endpoint, receive emails, done. No dashboard overload, no feature creep.

Key features:

HTML form endpoint
Email notifications
Spam protection
Simple dashboard

Pricing: Free tier available. Paid plans start at $8/month.

Drawback: Very limited compared to other options. No form builder, no self-hosting, minimal integrations.

4. Netlify Forms: Great If You're Already on Netlify

Best for: Developers whose sites are deployed on Netlify.

Netlify Forms is built directly into the Netlify platform. If you're already deploying on Netlify, it's the easiest possible option — just add netlify to your form tag and you're done.

<form name="contact" method="POST" data-netlify="true">

Key features:

Zero setup if you're on Netlify
Spam filtering
Email notifications
Dashboard in Netlify

Pricing: 100 submissions/month free with Netlify. Paid plans through Netlify's pricing.

Drawback: Only works if your site is on Netlify. If you host anywhere else, this isn't an option.

5. Staticforms: Completely Free

Best for: Developers who want a completely free form backend for low-volume projects.

Staticforms is a free, no-account-required form backend. You just use your email address as the identifier.

Key features:

Completely free
No account required
Email notifications
Honeypot spam protection

Pricing: Free.

Drawback: No dashboard, no submission history, no file uploads, no self-hosting. Works for very basic contact forms but nothing more.

Side-by-Side Comparison

Feature	Formspree	Formgrid	Getform	Basin	Netlify Forms
Form builder	❌	✅	❌	❌	❌
HTML endpoint	✅	✅	✅	✅	✅
Shareable form link	❌	✅	❌	❌	❌
Self-hostable	❌	✅	❌	❌	❌
Open source	❌	✅	❌	❌	❌
File uploads	✅ Paid	✅	✅	✅ Paid	✅ Paid
Free tier	✅ 50/mo	✅ 50/mo	✅	✅	✅ 100/mo
Starting price	$15/mo	$8/mo	$29/mo	$8/mo	Bundled
GDPR friendly	⚠️	✅	⚠️	⚠️	⚠️

Which One Should You Use?

Use Formgrid if:

You want a form backend AND a form builder in one tool
You care about open source and self-hosting
You're paying too much for JotForm or Formspree and want to cut costs
You need to share a form link with someone non-technical via WhatsApp or email
GDPR compliance matters to you

Use Getform if:

You just want a clean, simple form backend replacement
You don't need a form builder
You're happy with a hosted service

Use Basin if:

You want the most minimal option possible
You just need basic form submission handling

Use Netlify Forms if:

Your site is already on Netlify
You want zero additional setup

Use Staticforms if:

You need something completely free
Volume is very low and you don't need a dashboard

Final Thoughts

Formspree is a good product but it's no longer the obvious choice in 2026. The market has moved and there are now better options at lower prices, especially if you care about open-source, self-hosting, or need both a form backend and a form builder in one place.

If I were switching today I'd go with Formgrid. It's the only tool on this list that gives you a form backend for developers AND a no-code form builder for non-technical users, at a lower price than Formspree, with full self-hosting support.

You can try it free at formgrid.dev — no credit card required.

Full disclosure: I built Formgrid. I wrote this comparison as honestly as I could. If anything looks inaccurate, let me know in the comments.

Tags: #webdev #html #opensource #tutorial

Most Contact Forms Don’t Fail Because of Code — They Fail Because of Human Behaviour

Tue, 17 Mar 2026 09:41:43 +0000

A small observation from building real-world contact forms that completely changed how I think about them.

Most developers assume contact form problems are technical.

We think about things like:

validation
spam protection
email delivery
backend logic

And to be fair — those things do matter.

But after working with real websites and real clients, I’ve noticed something surprising:

Most contact forms don’t fail because of code.

They fail because of what happens after the form is submitted.

The system works… but the result doesn’t

A typical contact form setup looks like this:

User submits form
Backend processes it
Email is sent
Business owner eventually reads it

From a developer perspective, everything is working.

No errors. No bugs. No failed requests.

But from a business perspective?

Leads are still being lost.

The real failure point: the inbox

The problem is simple:

Email is not a real-time system.

Most business inboxes are chaotic.

They’re full of:

marketing emails
invoices
spam
automated notifications

A genuine enquiry can easily:

get buried
get ignored
get seen too late
land in spam

And the developer never sees this happen.

Why this actually matters

In many industries, speed is everything.

Think about:

plumbers
electricians
locksmiths
emergency services

When someone fills out a contact form, they often send the same enquiry to multiple businesses.

The first person to reply usually wins.

Not the best website.
Not the best developer.
The fastest responder.

Real-world scenario

A customer submits 3 enquiries:

Company	Response Time	Outcome
Company A	5 minutes	Wins job
Company B	1 hour	Too late
Company C	Never sees email	Lost lead

All three websites worked perfectly.

Only one business gets paid.

As developers, we optimise for:

correctness
reliability
clean architecture

But we rarely ask:

Where does this message actually go, and how quickly will it be seen?

That’s the part that directly affects business outcomes.

The actual solution isn’t more code

You don’t need:

a more complex backend
a better framework
more validation rules

You need better delivery.

The message needs to arrive somewhere the user is already paying attention.

For example:

SMS
WhatsApp
Slack
push notifications
CRM alerts

Anywhere that gets seen instantly.

What changed when I tested this

While building sites for small businesses, I kept seeing the same issue — enquiries sitting unread in inboxes.

So I started experimenting with sending submissions directly to WhatsApp instead.

The difference was immediate.

Businesses that used to reply hours later were suddenly responding within minutes, simply because the message showed up where they were already active.

That observation eventually led me to build a small tool called Web2Phone to handle this more reliably — but the key takeaway came before the tool itself.

It was simply this:

Delivery speed matters more than the form itself.

Practical takeaway for developers

Next time you build a contact form, don’t just ask:

“Does it submit correctly?”

Ask:

“How fast will the client actually see this message?”

Because that’s what determines whether the lead is won or lost.

Final thought

A contact form isn’t just a data collection tool.

It’s part of a real-time communication system.

If the message isn’t seen quickly, the system has already failed — even if the code is perfect.

What are you using?

Curious how others are handling this in production:

Email only?
CRM integrations?
Slack notifications?
SMS or WhatsApp?

Would be interesting to hear what’s working best.

Why Email-Only Contact Forms Are Failing in 2026 (And What Developers Should Do Instead)

Mon, 02 Mar 2026 12:01:00 +0000

Email delivery isn’t the problem anymore. Visibility is.

In 2026, email-only contact forms are technically reliable but increasingly ineffective for urgent workflows. Here’s what developers should rethink.

The Illusion of Reliability

For years, most contact form systems followed the same model:

HTML form
Backend endpoint
SMTP configured
Return 200 OK

Technically, everything works. Emails are delivered. Logs are clean. No bounce issues.

And yet businesses still miss leads.

The problem isn’t deliverability. It’s visibility.

SMTP Success ≠ Human Attention

There’s a dangerous assumption built into many form backends:

If the email is delivered, the human will see it.

That assumption no longer holds.

Gmail tabs filter notifications
Spam detection is aggressive
Inbox overload hides important messages
Mobile users don’t constantly monitor email

For low-urgency contact pages, this might be fine.

But for emergency services, trades, agencies, and competitive local businesses — response time determines revenue.

Developers optimise for:

API reliability
Retry logic
Queue performance
Webhook success

But the metric that matters most for many businesses is:

Response time.

If a locksmith receives an enquiry at 11pm but sees it at 7am, the job is gone.

The first responder wins.

Where Email-Only Systems Break Down

Email-only contact forms work well for:

Portfolio sites
Low-volume brochure sites
Non-urgent enquiries

They struggle in:

Emergency trades
Healthcare services
Agencies competing for inbound leads
Time-sensitive booking workflows

In these cases, the issue isn’t whether the message was sent — it’s whether it was seen in time.

What Developers Should Do Instead

1. Use Multi-Channel Delivery

Combine email with higher-visibility channels such as WhatsApp or SMS.

2. Implement Fallback Logic

If the primary channel fails, automatically retry via a secondary channel.

3. Add Domain Allow-Listing

Restrict which domains can submit to your endpoint to reduce abuse and spam.

4. Use Rate Limiting + Honeypots

Lightweight spam protection reduces malicious traffic without degrading UX.

5. Log Delivery Without Retaining PII

Store delivery metadata. Hash destination values. Remove message content after successful delivery.

Rethinking Notification Architecture

The better question is not:

Was the email delivered?

It’s:

How fast can the business actually see and respond to this enquiry?

That shift changes backend architecture decisions.

Some newer form backends now prioritise instant messaging delivery (such as WhatsApp) with automatic email fallback if delivery fails. That kind of architecture focuses on visibility rather than just SMTP success.

If you're curious about how WhatsApp-first systems compare to traditional email-first tools, I wrote a deeper technical comparison here:

https://web2phone.co.uk/blog/formspree-vs-web2phone-2026/

Final Thought

Email isn’t broken.

But email-only contact forms are increasingly incomplete for urgent workflows.

Developers have already mastered reliable delivery.

The next optimisation layer is:

Visibility
Notification priority
Response speed

In many industries, the fastest responder wins.

Coder Legion - Recent posts tagged form

Slope Intercept Form with Gradient Descent

Slope-Intercept Form equation

Conclusion

Formspree Alternatives in 2026: Open Source, Cheaper, and Self-Hostable

Why Developers Look for Formspree Alternatives

The Best Formspree Alternatives in 2026

1. Formgrid.dev: Form Builder + Form Backend in One Place

Formgrid Landing Page:

Formgrid Dashboard:

Example Form Built By Formgrid:

2. Getform: Simple and Clean Form Backend

3. Basin: Minimal and No-Frills

4. Netlify Forms: Great If You're Already on Netlify

5. Staticforms: Completely Free

Side-by-Side Comparison

Which One Should You Use?

Final Thoughts

Most Contact Forms Don’t Fail Because of Code — They Fail Because of Human Behaviour

The system works… but the result doesn’t

The real failure point: the inbox

Why this actually matters

Real-world scenario

The developer blind spot

The actual solution isn’t more code

What changed when I tested this

Practical takeaway for developers

Final thought

What are you using?

Why Email-Only Contact Forms Are Failing in 2026 (And What Developers Should Do Instead)

The Illusion of Reliability

SMTP Success ≠ Human Attention

The Developer Blind Spot

Where Email-Only Systems Break Down

What Developers Should Do Instead

1. Use Multi-Channel Delivery

2. Implement Fallback Logic

3. Add Domain Allow-Listing

4. Use Rate Limiting + Honeypots

5. Log Delivery Without Retaining PII

Rethinking Notification Architecture

Final Thought