postmarkapp.comcontributed by Samuele Ongaro
The value is the network, the data or the infrastructure. Keep paying.
Sends the email your application produces — receipts, password resets, notifications — over an API or SMTP. It keeps separate sending infrastructure for transactional mail, stores the full message history, and reports on bounces and opens.
Do not build this. Transactional deliverability is the product, and it is a reputation you cannot bootstrap. A password reset that does not arrive is an outage you cannot see from your own side. What you are paying for is separated sending infrastructure, relationships with mailbox providers, and somebody watching the reputation full time. WHY THIS ONE IN PARTICULAR - Transactional and marketing mail kept apart at the provider level is the whole design here, and it is the right one. A receipt failing because a campaign got complaints is the specific disaster this prevents - If you send both, use separate streams or separate providers. Never one reputation for both WHAT TO DO INSTEAD OF BUILDING - Rent a relay, always. Compare on price at your volume and on the quality of the bounce and complaint feedback - Never run your own mail server for application email. Clean address, reverse DNS, warmed reputation and feedback loops with every large provider is a job, not a configuration WHAT YOU MUST DO REGARDLESS - **SPF, DKIM and DMARC**, with DMARC actually enforcing rather than sitting at none. Read the aggregate reports — they tell you who is sending as you - A separate subdomain for transactional mail, warmed slowly - Consume bounces and complaints and act on them: hard bounce suppresses immediately, complaint suppresses permanently - One delivery row per recipient per message, written before sending, idempotent, with the provider's message id recorded. That makes a resume exact and lets you change provider by rewriting one file - A per-recipient daily cap, so a loop cannot send somebody four hundred messages. This costs an afternoon and prevents a very bad day WHAT TO BUILD A local mail catcher for development, so nothing reaches a real person by accident and nobody needs a provider account to work. That is under Mailtrap elsewhere in this catalogue, it is a weekend, and it removes a whole class of embarrassing mistakes. AND THE CHECK NOBODY RUNS Send your own password reset to addresses at three different large providers and see where each lands. Most people have never looked, and the answer is sometimes the spam folder. THE ONE-LINE VERSION Rent the relay and keep transactional apart from marketing. Build the development catcher, and go and check where your own reset email lands.
What you lose
- Sending IP reputation built over years, which is the entire reason a password reset arrives
- Separation of transactional from marketing streams, so a campaign cannot poison your receipts
- Bounce, complaint and spam-trap handling wired into feedback loops with the mailbox providers
- Delivery timing measured in seconds, and a status page you can point at when it is not
- Message history and a searchable log of what was actually sent to whom
If you would rather not build
- Amazon SES — the cheap provider you build this layer on top of
- Resend and Loops — friendlier APIs, same underlying trade
What it costs
read from their page 25 Aug 2026
| Plan | Billed monthly | Billed yearly | Last read |
|---|---|---|---|
| Basic | $15/mo | — | 25 Aug 2026 |
| Pro | $16.50/mo | — | 25 Aug 2026 |
| Platform | $18/mo | — | 25 Aug 2026 |
Their pricing page is where these came from. Seeing a different price? Tell us.
The escape hatch
open source · no votes, no paid placement
Postal
$0Full mail server for application email, with queues and bounce handling.
postalserver/postalfree · open source
Keila
$0Newsletter tool built on Elixir that sends through your own provider.
pentacent/keilafree · open source
Why this verdict
our own opinion · changed only by a person
24/100
Verdict no at 24: SMTP is trivial and deliverability is not. A self-run mail server for transactional email means password resets landing in spam, which is worse than any subscription. Rent the reputation, build the queue and the log.
History
tracked since 6 Aug 2026 · nothing is ever overwritten
Questions about Postmark
answered from the record above
Is Postmark free?
No — the plan we track is $15 a month. Basic at the 10,000 emails per month tier. Pro is $16.50 and Platform $18 at the same volume; additional emails are billed per thousand.
Can you replace Postmark by building your own?
KEEP IT. The value is the network, the data or the infrastructure. Keep paying. Replacement score 24 out of 100, build time longer than it saves. Read what you lose before you decide.
How much does Postmark cost?
$15 a month on Basic — $180 a year. Recorded 25 Aug 2026.
What do you lose by replacing Postmark?
Sending IP reputation built over years, which is the entire reason a password reset arrives; Separation of transactional from marketing streams, so a campaign cannot poison your receipts; Bounce, complaint and spam-trap handling wired into feedback loops with the mailbox providers; Delivery timing measured in seconds, and a status page you can point at when it is not; Message history and a searchable log of what was actually sent to whom. If any of those carry weight for you, keep paying.
Is there an open-source alternative to Postmark?
Yes: Postal, Keila. The prompt on this page is for when you want it your way instead.
Related entries
same category first, most replaced first
WiseStamp
Mailtrack
CuratedEvery week, something stops being worth paying for.
New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click. Nothing is being sent yet — your address is kept here, and the first issue is the first thing it is used for.
free forever · no tracking pixel · stored here, never passed to anyone