Plunk

What Plunk actually is

Plunk is an open-source email platform for transactional email, marketing campaigns, and workflow automation. It is the work of a small Belgian team — founded in August 2022 by Dries Augustyns, later joined by Carlo D'Agnolo — and it made an unusual move in August 2024: the whole codebase went open source under AGPL-3.0, after two years as a proprietary product. The GitHub project (useplunk/plunk) has since passed 5,000 stars, and the business model is now the classic open-core split: a hosted cloud at useplunk.com, or run it yourself with Docker Compose for free.

The product scope is wider than "transactional email API". Plunk handles four send types through one contact model: transactional sends via REST API or SMTP relay, campaign broadcasts (newsletters, announcements), event-triggered workflows with delays and branching, and inbound email delivered to your app as webhooks. Contacts are unlimited on every plan and carry a unified activity history across transactional, campaign, and workflow events. Supporting features include dynamic segments, custom sending domains with DKIM/SPF/DMARC set up automatically, open/click/bounce analytics, and email validation (typos, disposable domains, missing MX records) before you send.

Positioning matters here. Plunk pitches itself as one tool replacing Resend, SendGrid, Mailchimp, Customer.io, and Mailgun at once, and publishes a price comparison ($0.001/email versus $0.002–$0.004 for those vendors at 10,000 emails/month). In our view the honest framing is narrower: if you are a SaaS or indie developer who wants transactional email and modest marketing automation from one system — and especially if you want the option to self-host — Plunk is compelling. If you are an enterprise sender with deliverability consultants, dedicated IP pools, and contractual SLAs, it is not that.

One correction to flag: our database row claimed Plunk offers "IP warming" and launched in 2026. Neither is right. IP warming is not a documented Plunk feature, and the project dates to August 2022. The core claim in the row — free for 1,000 emails/month, then $0.001 per email, self-hostable — checks out.

Pricing: what you really pay

Plunk's pricing is among the simplest in the category. Two tiers, one meter:

• Free forever: 1,000 emails/month, no credit card. Includes transactional email, workflow automation, campaign broadcasts, inbound email, email validation, custom domains, click and open tracking, and unlimited contacts. Marketing emails carry a Plunk-branded footer on this tier, and inbound emails count against the 1,000.
• Pay as you grow: $0.001 per email, no base fee, no commitment, no feature gates. Removes the branding, adds a monthly spend cap you can set per category. Unlimited emails.

The unit economics are worth stating in absolute terms: 10,000 emails/month is $10; 100,000 is $100; a million is $1,000. The meter counts every send and receive — transactional sends are one credit per recipient, campaigns one per recipient, workflow sends one per send, inbound one per received message, and emails with attachments cost two credits regardless of attachment size. The per-category spend caps are a thoughtful touch: you can guarantee transactional capacity stays available even if a campaign over-sends.

Self-hosting is free in the sense that matters — the AGPL-3.0 codebase runs via Docker Compose and you own the data — but note what the pricing page says plainly: self-hosted instances run on your own infrastructure. Deliverability then becomes your problem (sending IPs, reputation, feedback loops), which is the hidden cost of every self-hosted email stack. Plunk's own comparison page undercuts the "pay-as-you-go scales badly" objection in our database notes: at $0.001 there is no volume cliff, only linear cost. What scales badly is not Plunk's price but the sending economics shared by every cloud email service at very high volume.

Against the alternatives this is genuinely cheap. Most competitors meter per email too but start several times higher, or meter per contact (which punishes list growth, something Plunk explicitly does not). For a side project on the free tier and a SaaS sending tens of thousands of transactional emails monthly, the cost is close to noise.

Performance & infrastructure

There is no infrastructure to inspect in the usual hosting sense — we cover VM and metal numbers at /benchmarks, not email pipelines — so this section is about the delivery stack and where it runs. The hosted platform is EU-based and GDPR-compliant by design, which is the team's Belgian roots showing and a real differentiator for European SaaS teams tired of US-centric data processing terms. The self-hosted variant deploys wherever you like.

Delivery features are respectable: SMTP relay (ports 465/587 with TLS) alongside the REST API, so frameworks that already speak SMTP work unchanged; template support with variable substitution; custom domains with DKIM, SPF, and DMARC configured automatically; inbound email with custom routing rules; and real-time analytics on opens, clicks, bounces, and unsubscribes. The API is plain HTTP and works from any language, with SDKs for Node.js and Python.

What we cannot verify from public sources is delivery performance itself: sending IP pools and their reputation, throughput limits, or an independent deliverability measurement. We have not tested Plunk's inbox placement, and we would not repeat vendor claims as if we had. For a small platform this is the single biggest unknown — deliverability is the product in transactional email, and it is earned over years of operations.

Reliability disclosure is thin as well. There is no published uptime SLA or service-credit schedule for the hosted platform, and no public status-page history we could cite. The project is actively maintained (the open-source transition in 2024 reinvigorated development), but it remains a small team. If your business stops when email stops, factor that into your architecture — a self-hosted option is the strongest hedge Plunk offers, because it moves availability into your own hands.

Where it falls short

Team size and track record. Plunk is a young, small company competing with vendors that have a decade of sending history and dedicated deliverability teams. Reputation is built on volume and time, and the hosted product is EU-only.

Deliverability tooling is basic versus the big ESPs: no documented dedicated IP offerings, no managed IP warm-up (our database's claim notwithstanding), no published feedback-loop or reputation dashboard. High-volume senders with strict inbox-placement requirements will outgrow it.

The marketing side is functional rather than deep: campaigns, segments, and workflows cover the common cases, but there is no advanced journey builder, no SMS or push, and third-party integrations are fewer than the incumbents offer. Email validation exists but is a pre-send check, not a full list-hygiene suite.

Finally, the self-hosting caveat again: AGPL-3.0 is a strong copyleft licence. That is fine for running the platform internally, but if you embed Plunk in a commercial product, the licence terms matter — read them before you commit.

Who should pick this

We would pick Plunk for indie hackers and SaaS teams that want one system for transactional email, newsletters, and triggered onboarding flows without paying per contact. It is our pick when EU data hosting matters, when open source is a requirement (audit, self-hosting, or just principle), and when budgets are small but the product still needs real email infrastructure. The free tier genuinely runs a modest product's transactional email.

We would not pick it for enterprise senders needing contractual SLAs, dedicated IPs, or guaranteed deliverability programmes; nor for teams that want deep marketing automation across channels. And if you self-host, make sure someone owns sending reputation — Plunk gives you the software, not the inbox placement.

Key takeaways

• Open-source (AGPL-3.0) email platform since August 2024: transactional API + SMTP relay, campaigns, workflows, inbound email, and unlimited contacts in one product.
• Pricing is two lines: free at 1,000 emails/month, then $0.001 per email with no base fee and per-category spend caps; attachments count double.
• Hosted platform is EU-based and GDPR-focused; self-hosting via Docker Compose is free but makes deliverability your responsibility.
• Founded 2022 in Belgium by Dries Augustyns; small team, 5,000+ GitHub stars, actively maintained.
• No published uptime SLA or deliverability guarantees — the main gap versus SendGrid/Mailgun-class vendors.
• Our database's "IP warming" and 2026 launch claims were wrong; the strongest facts are the pricing model and the self-hosting story.

Sources

• https://www.useplunk.com/pricing
• https://www.useplunk.com/pricing.md
• https://www.useplunk.com/
• https://docs.useplunk.com/concepts/billing.md
• https://github.com/useplunk/plunk
• https://github.com/useplunk/plunk/blob/next/README.md
• https://github.com/useplunk/plunk/blob/next/.env.self-host.example
• https://powermtaproviders.com/providers/plunk.html
• https://www.sequenzy.com/pricing/plunk