Skip to content

Everything a form backend should do, and the routing most of them skip.

Postbag receives forms, stores every submission durably, and delivers each one by rules. Six capabilities carry the product; each has its own page with specifics, code and limits.

And a dashboard that is just another API client.

Forms, a live inbox, destinations, routes, streams (shown as Bags), deliveries, events and API keys. Everything it does goes through the same /v1 an agent uses; there is no UI-only capability.

The Postbag dashboard showing a form's page: its submit URL, the Inbox, Embed, Fields, Send to and Settings tabs, and two received submissions
A form in the production dashboard. Real screenshot, real submissions.

What is a form backend?

A form backend is a hosted endpoint that receives HTML form submissions so a website does not need server code of its own. The site's <form action> points at the backend; the backend stores the submission and notifies someone. Postbag is a form backend that also routes: it can group many forms into one stream, map their differing fields onto one versioned schema, and deliver that shape to several destinations with rules, while keeping every submission as a durable row. It is multi-tenant, self-hostable, and driven entirely through one API so that AI agents can set it up without a browser.

Your first form is three minutes away.

Sign up, get a submit URL, point a form at it. The first submission lands in your inbox and your email. Everything else appears when you need it.