Transactional email comparison
Larasend vs Plunk
Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.
Latest evidence check Nov 9, 2026
Who it is forLarasend is a self-hosted transactional email platform for Laravel teams with an HTTP API, dashboard, activity log, API keys, delivery events, suppressions and a Laravel mail transport, sending through your own Amazon SES account.
Latest evidence check Nov 10, 2026
Who it is forPlunk describes a platform for transactional email, marketing campaigns and workflow automation.
What the evidence answers
A reading of reviewed official documentation for Larasend and Plunk. It is not a hands-on test, a ranking or a recommendation of one product.
- Common buyer questions answered
- 4 requirements
- Documented for one
- 1 requirement
- Not verified for either
- 2 requirements
- Prices
- Not like-for-like yet
Price
Larasend
Free plan · paid prices not verified ·
- Self-hosted: no subscription charge ·
Plunk
Documented price: 1.00 per 1,000 emails overage (currency not stated) · Plan: Pay-as-you-go · no minimum commitment ·
- Self-hosted: no subscription charge ·
- Free tier: no subscription charge ·
- Pay-as-you-go: 1.00 (currency not stated) overage per 1,000 emails, no monthly base charge · no minimum commitment ·
A complete like-for-like price comparison is not established; the next steps say what is missing.
Common buyer questions answered
Even when labels match, check each source for differences in plans, units and scope.
- Sending volume
- Larasend Larasend syncs your Amazon SES sending quota but accepts API sends even when that sync is stale or temporarily unavailable; SES remains the final authority for provider-side send rejection.
- Plunk Each recipient of a transactional send or campaign, each workflow send step and each received inbound email uses one credit toward monthly usage; an email with attachments uses two credits regardless of attachment size.
- Domains
- Larasend Sending domains are your own SES-verified domains: you add each in Larasend and publish the DKIM records it shows in Route 53 or another DNS provider.
- Plunk Custom sending domains can be verified, with DKIM and SPF support.
- Log retention
- Larasend Because you self-host the control plane, email logs and metadata stay in infrastructure you control; the README states no retention window.
- Plunk Rendered email HTML is kept for 90 days and API request logs for 30 days; email metadata and metrics are kept indefinitely.
- Webhooks and events
- Larasend Amazon SES delivery, bounce, complaint, open and click events come back to Larasend through an SES webhook; Larasend then updates its activity dashboard, metrics, suppressions and webhook deliveries.
- Plunk Plunk sends real-time HTTP requests to your application through a workflow Webhook step, triggered by events such as email bounces, spam complaints or custom events.
Limits to check
- Larasend Larasend requires an Amazon SES account with a verified sending domain, PostgreSQL 17 or newer, Docker and Docker Compose for production-style installs, and Redis 7 or newer with the bundled Compose stack.
- Plunk Plunk documents a self-hosted deployment option.
- Plunk Self-hosting needs Docker and Docker Compose, an AWS SES account for sending and a domain name with subdomains for each service.
Not verified yet
No reviewed evidence for either product on dedicated IP and overage charges.
Documented for one product only, shown in the table below: Plunk: support.
Not verified means our reviewed sources do not establish it. It does not mean a product lacks the capability or that it costs nothing.
Side-by-side evidence
Documented values with their sources and check dates; requirements the sources do not establish stay marked.
- Documented as supported
- Documented as unsupported
- Not verified Sources do not establish it
- Not applicable
| Requirement | Larasend | Plunk |
|---|---|---|
| Pricing | Free plan · paid prices not verified | Documented price: 1.00 per 1,000 emails overage (currency not stated) · Plan: Pay-as-you-go · no minimum commitment |
| Who it is for | Larasend is a self-hosted transactional email platform for Laravel teams with an HTTP API, dashboard, activity log, API keys, delivery events, suppressions and a Laravel mail transport, sending through your own Amazon SES account. Verified Nov 6, 2026 · Larasend: larasend-project | Plunk describes a platform for transactional email, marketing campaigns and workflow automation. Verified Nov 3, 2026 · Plunk: plunk-readme |
| Coverage limits | Larasend requires an Amazon SES account with a verified sending domain, PostgreSQL 17 or newer, Docker and Docker Compose for production-style installs, and Redis 7 or newer with the bundled Compose stack. Verified Nov 6, 2026 · Larasend: larasend-project | Plunk documents a self-hosted deployment option. Verified Nov 3, 2026 · Plunk: plunk-readme
|
| Sending volume | Larasend syncs your Amazon SES sending quota but accepts API sends even when that sync is stale or temporarily unavailable; SES remains the final authority for provider-side send rejection. Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026. Sending volume and charges are those of the buyer's own Amazon SES account, which were not captured. Supplier description, not a test. Verified Nov 9, 2026 · Larasend: larasend-project | Each recipient of a transactional send or campaign, each workflow send step and each received inbound email uses one credit toward monthly usage; an email with attachments uses two credits regardless of attachment size. Plunk billing documentation (docs source at release v0.18.0), captured 9 November 2026. Applies to the hosted version; a per-category monthly cap can be set for transactional, campaign, workflow and inbound emails. Supplier statement, not a hands-on test. Verified Nov 10, 2026 · Plunk: plunk-docs-billing-project |
| Domains | Sending domains are your own SES-verified domains: you add each in Larasend and publish the DKIM records it shows in Route 53 or another DNS provider. Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026; recommended setup, not a tested installation. The README states no limit on the number of domains. Verified Nov 9, 2026 · Larasend: larasend-project | Custom sending domains can be verified, with DKIM and SPF support. Dated publisher project README at release v0.18.0, captured on 9 November 2026; supplier feature list, not a tested verification. Verified Nov 10, 2026 · Plunk: plunk-project |
| Log retention | Because you self-host the control plane, email logs and metadata stay in infrastructure you control; the README states no retention window. Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026; supplier description. Log storage, backups and any pruning were not tested. Verified Nov 9, 2026 · Larasend: larasend-project | Rendered email HTML is kept for 90 days and API request logs for 30 days; email metadata and metrics are kept indefinitely. Plunk data-retention documentation (docs source at release v0.18.0), captured 9 November 2026. The 90-day and 30-day windows are compiled in and run as scheduled jobs on the worker process in self-hosted deployments. No retention test was performed. Verified Nov 10, 2026 · Plunk: plunk-docs-retention-project |
| Webhooks and events | Amazon SES delivery, bounce, complaint, open and click events come back to Larasend through an SES webhook; Larasend then updates its activity dashboard, metrics, suppressions and webhook deliveries. Publisher project README at release v0.1.0 (commit 0995381) captured 8 November 2026; supplier description, not a tested integration. Event publishing needs an SES configuration set; the README does not describe outgoing webhook payloads, retries or endpoint limits. Verified Nov 9, 2026 · Larasend: larasend-project | Plunk sends real-time HTTP requests to your application through a workflow Webhook step, triggered by events such as email bounces, spam complaints or custom events. Plunk webhooks documentation (docs source at release v0.18.0), captured 9 November 2026. Internal events listed there include email sent, delivery, open, click, bounce, complaint and received. No webhook delivery test was performed. Verified Nov 10, 2026 · Plunk: plunk-docs-webhooks-project |
| Support | Not verified | The README lists the public Plunk documentation and a Discord server; no paid support plan is named in it. Dated publisher project README at release v0.18.0, captured on 9 November 2026; supplier statement, no support request was made. Verified Nov 10, 2026 · Plunk: plunk-project |
| Coverage note | Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms. | Publisher project README captured 3 November 2026. Self-hosting and email delivery entail separate infrastructure, setup and service costs. No email, account, deployment, integration or deliverability test was performed. |
2 requirements without reviewed evidence here
Not verified means the reviewed sources do not establish it; it does not mean a product lacks it or that it costs nothing.
- Dedicated IP Larasend: not verified · Plunk: not verified
- Overage charges Larasend: not verified · Plunk: not verified
Next steps
- Confirm Larasend's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
- Confirm the currency of Plunk's displayed price at checkout.
- Ask Larasend about dedicated IP, overage charges and support; our sources do not establish them yet.
- Ask Plunk about dedicated IP and overage charges; our sources do not establish them yet.
Commissions never change costs, eligibility or rankings.