Why Postbag
Forms deserve a dependable place to land.
Postbag grew out of a real system routing leads from many small websites to one business. Losing a message was never an acceptable way to fail. It still isn't.
The origin
The first version had a very ordinary job.
Receive forms from a growing set of websites, keep every lead safe, and send each one to the right place. The sites did not all collect the same fields. The inbox on the other end could have a bad day. The person building the next site might be an agent.
That ordinary job exposed the product: a dependable place between a form and everything that happens after it.
many sites one dependable record
What stayed
The useful constraints became the principles.
No dramatic reinvention. Just the rules that kept the original system understandable as more sites, people and inboxes arrived.
- 01
Save first
Every message is safely on the record before Postbag tries to send it anywhere.
- 02
One front door
The dashboard, the CLI and your agent all use the same public API. No side doors.
- 03
Yours to run
Postbag Cloud and self-hosting are the same open-source product. Nothing held back.
Who
Built by one developer, in the open.
Hi — I'm Fahim. I run small business websites and the systems behind them, and Postbag is the piece I kept wishing existed. The repository is public, the server and product are AGPL-3.0, and the SDK, CLI and MCP server are MIT.
Read the sourceContact
A real form, routed by Postbag.
Questions about the product, self-hosting or security are all welcome. This form posts to Postbag and lands in my inbox — I read everything.
This site sets no tracking cookies. Postbag stores the data and delivery metadata needed to route your message. Read the privacy policy, terms, DPA and sub-processors list.
Give your forms somewhere to go.
Your agent can build and test the form before you even sign up. Claim it when you're ready.