Skip to content

One calm place to receive. A clear route onward.

It starts as a form that simply works. The rest is there the day you want it — and invisible until then.

The receiving path

Each part does one job. Together, they make forms easy to leave alone.

Start with a form. Postbag keeps every message on the record, then sends it to the places that need to know.

  1. Where messages go

    Pick where you need to hear from people. Postbag keeps the rest orderly.

    Explore

  2. Saved first

    Someone writes to you at 2am. Your email is having a rough night. On Monday, the message is still there.

    Explore

  3. Where messages can go

    Set a place up once. Let every form use it when it needs to.

    Explore

  4. Field changes

    A site changed one question last night. Better to hear it from Postbag this morning.

    Explore

  5. Spam protection

    Spam is a label you can review, not a bin you can never open.

    Explore

  6. Self-hosting

    Postbag Cloud is the easy door. Self-hosting is the ownership door. They lead to the same product.

    Explore

When you want to look

The dashboard is another way into the same product.

Your forms, a live inbox, everywhere things go, and a record of every send. It all runs through the same API your agent uses — nothing useful is locked behind the screen.

See how agents work with Postbag

Dashboard

Forms · Streams · Deliveries See it, filter it, route it.

API

POST /v1/forms Create it, test it, hand it over.
Two entrances. One Form record.

The useful definition

A form backend is where your form's messages go, so your site doesn't need its own server.

Postbag adds the part that matters once one site becomes a few: it can gather many forms into one tidy feed and send it wherever it needs to go. And every message stays safely on the record the whole way through.

Give the form job to your agent.

It can build, wire and test the form before you even sign up. Claim it when it's worth keeping.

Create a form Read the quickstart