Skip to content
Postiix

About Postiix

Product teams don't usually choose to run three separate email systems. It happens gradually: a transactional API for receipts and resets, a marketing tool for campaigns, and whatever the templates end up living in. Each has its own contacts, its own suppression rules, and its own idea of what "delivered" means.

Postiix is built to be the operating layer underneath all of it — one API, one set of contacts, one place to see what actually happened to a message.

How we think about it

Transactional and marketing stay separate, on purpose

They have different senders, different suppression rules, and different consequences when something goes wrong. Postiix keeps them as distinct streams under one platform, instead of forcing one send path to serve both.

Test mode should run the real pipeline

A test send that skips templating, suppression checks, and logging doesn't actually verify your integration. Postiix runs the full pipeline in Test mode — the only thing that's skipped is the actual delivery.

Infrastructure should be observable

If your application sends an email, you should be able to see what happened to it — in your dashboard, and in your own systems, via a webhook, without polling.

What that looks like in practice

Idempotent by default

A retried request never sends a duplicate email.

A real Test mode

The full pipeline runs without reaching a real inbox.

Suppression per stream

A marketing opt-out never blocks a transactional send.

Observable by default

Every send and every webhook delivery is inspectable.

Who's behind it

Postiix is built and operated by Qbix Labs.