Two personas, one product.
The solo developer with one contact form and the operator with fifteen sites feeding one partner. Postbag serves both; the advanced model stays hidden until the second persona needs it.
-
Contact form
The solo-dev path. You have one form on one site and want an endpoint and an email. You meet exactly one new noun: Form.
Read more → -
Agencies and fleets
The operator's path. Fifteen sites, fifteen slightly different forms, one partner who wants one shape between two dates. Configured without code.
Read more → -
Lead routing
A lead is worth money. It should be stored before it is sent, sent to every system that needs it, and visible if any of those systems was down.
Read more → -
AI-built websites
If an agent wrote the site, the agent should wire the form. Postbag makes that a four-call conversation, and leaves the wiring in the repo for the next session.
Read more → -
Static sites and JAMstack
Static hosting has no server to receive a form. Postbag is the server, and it does not care which host you use or whether you move.
Read more →
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.