splitforms.com

Raman Makkar

Founder of splitforms

I'm a full-stack developer building splitforms — the form backend I wish existed when I was shipping my own projects. I write most of the posts on this blog, and I answer the support email myself.

Background

I founded splitforms in 2012 and have been building it ever since — mostly in TypeScript, Postgres, and the Next.js / React side of the JAMstack. Before splitforms I shipped SaaS products and developer tools, and along the way I burned a lot of hours re-implementing the same boring form-handling glue: an HTTP endpoint, a queue, a spam filter, a notification email, sometimes a webhook. Every project, the same plumbing. splitforms is what happens when you finally decide to build that plumbing properly, once, for everyone.

splitforms is independent and bootstrapped, funded entirely by paying customers — never venture capital. That shapes almost every product decision: I'd rather build a focused product I can stand behind than a sprawling one I can't.

Why splitforms

The form-backend space has been weirdly stagnant for years. The expensive tools charge enterprise prices for what is, fundamentally, an HTTP endpoint and a queue. The cheap ones run on shoestrings and silently drop traffic during launches. The free tiers shrink every six months and the upgrade paths are priced as a punishment for growing. Most of the dashboards feel like they were last touched in 2017.

I built splitforms because the gap is real and the fix isn't complicated — it's a matter of caring about the basics. A free tier that's actually useful (500 submissions, no card, no time limit). Sane Pro pricing ($5/month for 5,000 submissions a month) and an Annual plan at $49/year for projects that want one predictable bill. Signed webhooks unlocked from the $5/month Pro plan. A dashboard built this decade. Plain HTML integrations and data export, so leaving is always one URL change away.

Areas of focus

Most of what I write about and ship lives at the intersection of these four areas:

  • Form backends. The HTTP endpoint, the queue, the retry semantics, the email deliverability tuning. This is the unglamorous infrastructure that has to work every time, especially during a launch spike — you can watch the live record on the status page.
  • Developer tools and DX. Less SDK rot, more copy-paste HTML. The integration is a standard form POST or a fetch() call — nothing to npm-install, version-pin, or migrate when frameworks shift again. Boring is good.
  • Automatic spam detection. A honeypot and per-IP rate limits catch the obvious bots, and rule-based content scoring catches the long tail without making visitors prove they're human. I write a lot about spam-filter false-positive review UX and what actually works in production versus what just looks impressive in a benchmark.
  • MCP for AI agents. splitforms ships a first-class Model Context Protocol server so coding agents — Claude Code, Cursor, Windsurf — can list forms, read submissions, and generate template HTML directly. Most form backends still ship a JavaScript SDK from 2018; I'd rather ship a protocol from 2026.

Contact

The fastest ways to reach me. I read everything and reply to almost all of it within a day or two.

Latest posts by Raman

The six most-recent guides, tutorials, and comparisons I've published on the splitforms blog.

See the full archive for everything I've written.

About splitforms

splitforms is a form backend API for developers building static sites, JAMstack apps, and modern web frameworks. Point any HTML form's action at https://splitforms.com/api/submit and submissions land in your dashboard with built-in spam filtering and email notifications — no server to run. Read more on the homepage or the about page.