Plunk

Plunk — Open-source email console you self-host on top of your own AWS SES account. Plunk is not a sender: it is a UI, contact store, event system and campaign builder that sits on top of Amazon SES. Self-hosted, you get a dashboard, templates and automation at SES's $0.10 per thousand, with your data in your own Postgres and your own region. The trade is that you own the deployment, and you inherit SES's sandbox exit before anything works at all. Founded 2023. Bootstrapped. Open source under AGPL-3.0.

We track it in 1 comparison — Email APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Time to first send — 30 min, 4th of 13.
• Throughput ceiling — 50,400 emails/hr, tied for best across 2 of 3 tools.
• Pricing model — pay-as-you-go, tied for best across 4 of 13 tools.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• React Email / MJML — , 10th of 12. Resend records react-email, mjml.
• IP warmup — No. Postmark records Yes.
• Inbound parsing — No. Postmark records Yes.
• MCP server — No. Resend records Yes.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 22 of 25 tracked fields carry a value for Plunk, and 0 of those cite a document you can open. Nothing here carries a verification date yet, which is itself a reason to check before committing. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is AhaSend. Plunk is ahead on Hosted templates (code-editor against none) and Product scope (both against transactional-only). AhaSend takes llms.txt docs (Yes against No) and Suppression list (Yes against Partial). That pattern repeats across the rest of the roster — see Plunk alternatives for the other rivals, each compared the same way.

Founded

2023

Funding

Bootstrapped

Licence

AGPL-3.0 (open source)

Fields we track

22 of 25

The cheapest honest way to get a dashboard, contacts and campaigns on top of SES pricing, and the only option here that puts message data in your own database. You take on the deployment and SES's onboarding at the same time.

Time to first send

30 min4th of 13

Inferred

React Email / MJML

–10th of 12

Inferred

IP warmup

○No9th of 11

Inferred

Inbound parsing

○No9th of 12

Inferred

Throughput ceiling

50,400 emails/hr1st of 3

Inferred

MCP server

○No6th of 7

Inferred

BIMI

○No10th of 11

Inferred

Pricing model

pay-as-you-go1st of 13

Inferred

Plunk is the right call in these situations, each one drawn from a field we actually record:

• Teams who already run SES and want a UI over it.
• Data-residency requirements no managed vendor satisfies.
• Self-hosters who would rather own the stack than rent it.
• Time to first send is your binding constraint. Plunk records 30 min, 4th of 13 in the Email APIs roster. We define that field as wall-clock from starting signup on a clean account to a message delivered to a Gmail inbox that is NOT a verified address on the account.
• Throughput ceiling is your binding constraint. Plunk records 50,400 emails/hr, the best figure in the Email APIs roster. We define that field as documented default sending rate for a new account, expressed as emails per hour, before requesting a limit increase.
• Pricing model is your binding constraint. Plunk records pay-as-you-go, the best figure in the Email APIs roster.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• React Email / MJML. Plunk records , 10th of 12 in the Email APIs roster. Resend records react-email, mjml on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• IP warmup. Plunk records No on the Email APIs table. Postmark records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Inbound parsing. Plunk records No on the Email APIs table. Postmark records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• MCP server. Plunk records No on the Email APIs table. Resend records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• BIMI. Plunk records No on the Email APIs table. Postmark records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 3 of the 25 fields we track for Plunk are still blank: Log retention, Free tier and Dedicated IP. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.