This published overview needs review. Verified catalogue facts changed; review dependent conclusions.
Haraka
Haraka is a Node.js SMTP server with a modular plugin architecture; the README says it handles thousands of concurrent connections and delivers thousands of messages per second.
- Verified facts
- 7
- Offers
- 1
- Sources
- 2
- Pricing
- Free offer
Overview
What Haraka is
Haraka is a Node.js SMTP server with a modular plugin architecture. The README says it handles thousands of concurrent connections and delivers thousands of messages per second; this profile has not measured that. It is widely deployed as a filtering MTA, or as a mail submission agent on port 465 (and legacy 587) with the auth and DKIM plugins enabled.
For application email, the relevant part is the built-in outbound delivery engine: mail flagged as relaying, for example by an auth plugin, is queued for outbound delivery automatically. Every SMTP transaction runs through hooks such as connect, helo, mail, rcpt, data and queue, each of which can be extended with a few lines of JavaScript, and the plugin registry covers auth, DNSBLs, DKIM, SpamAssassin, rspamd, Redis, ClamAV and queue backends.
Read the full editorial overview
Scope and setup
Haraka is not a mail store, a local delivery agent or an IMAP server; the README says it is designed to work alongside those systems. It also does not describe an HTTP sending API, a dashboard or delivery analytics, so an application that wants those needs another layer in front of it.
Haraka requires Node.js and installs from npm. Setup creates a service directory with config and plugins folders. By default, mail for the domains in the host list is accepted and forwarded through the smtp-forward plugin, and active plugins are chosen in a config file.
Licence and maintenance
Haraka is released under the MIT License. It was created by Matt Sergeant and is currently maintained by Matt Simerson. On 5 November 2026 the haraka/Haraka repository was not archived, and GitHub listed v3.4.0, published that day, as the latest release.
Help is available through GitHub issues, a mailing list and a getting-started screencast. No installation, relay or deliverability test was run for this profile, and servers, IP reputation and DNS remain the operator's work and cost.
Sources
Haraka: haraka-project · Evidence: documentation · Not checked
Plans & prices
Prices as listed by Haraka, before any tax or fee the pricing page does not state.
Scroll the table sideways for every column.
| Plan | Rate period not stated | Coverage limits |
|---|---|---|
| Plan: Self-hosted | FreeTax: Confirm at checkoutUpfront: not established ConditionsDated publisher documentation at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; supplier description, not a deployment or independent test. Applies to the MIT-licensed software, which the README says requires Node.js and is installed with npm. Servers, IP addresses, DNS, third-party services used by plugins and managed offerings have separate costs and terms; no hosted Haraka service or paid support was established. | The documented default for outbound concurrency is 10,000 simultaneous deliveries per worker (concurrency_max); the effective total is that value multiplied by the number of nodes.ConditionsDated publisher documentation (docs/Outbound.md) at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; outbound.ini table. A configurable default, not a measured or guaranteed delivery rate. |
Documented facts
Each fact comes from official documentation and shows when it was verified.
Who it is for
Haraka is a Node.js SMTP server with a modular plugin architecture; the README says it handles thousands of concurrent connections and delivers thousands of messages per second.
Coverage limits
Haraka is not a mail store, a local delivery agent or an IMAP server and is designed to work alongside those systems.
Sending volume
A default installation queues outbound mail to disk and delivers it to the appropriate MX for each recipient domain, retrying temporary failures automatically on the configured backoff schedule.
Dated publisher documentation (docs/Outbound.md) at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; supplier description, not a throughput or deliverability test. Mail is outbound only when a plugin marks it as relaying, for example after SMTP AUTH.
Dedicated IP
By default the operating system’s routing table chooses the source IP; an operator can pin outbound mail to a specific IP per sender or domain by binding the address to a local interface or alias and setting mx.bind and mx.bind_helo in a get_mx plugin hook.
Dated publisher documentation (docs/Outbound.md) at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; configuration guidance, not a deliverability test. The operator supplies and warms the IP addresses.
Support
The README lists GitHub Issues, a mailing list (implemented as a Haraka plugin) and a getting-started screencast as the ways to get help.
Dated publisher documentation at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; supplier description, not a deployment or independent test. These are community channels; response times and any paid support are not stated in the README.
Applies to the facts above: 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.
Not confirmed in our sources
We have not confirmed these terms for Haraka in the linked documentation. That does not mean Haraka lacks them; confirm them before you rely on them.
- Domains
- Log retention
- Webhooks and events
- Overage charges
Sources & methodology
Facts come from the linked documentation. Documentation checks are not hands-on tests, and readable sources can have incomplete coverage.
Discovered an undocumented discrepancy or pricing shift? Submit a correction request.
Submit correctionHaraka alternatives
Other transactional email tools to weigh. Different billing units do not establish a cost winner, so compare plans side by side.
Resend
Transactional email
Sends application email, such as password resets and order confirmations, through the /emails API; marketing broadcasts use a separate API. · Evidence needs recheck
Documented price$20/moPrice needs recheckPrice terms
Documented price: $20/mo · Plan: Pro · 1-month commitment
Postmark
Transactional email
Sends transactional email and keeps bulk or broadcast email on separate Message Streams. · Evidence needs recheck
Documented price$15/moPrice needs recheckPrice terms
Documented price: $15/mo · Plan: Basic · 1-month commitment
Mailgun
Transactional email
Sends application email through an HTTP API or an SMTP endpoint. · Evidence needs recheck
Documented price$15/moPrice needs recheckPrice terms
Documented price: $15/mo · Plan: Basic · 1-month commitment
Haraka comparisons
Compare two products in the same category using their documented terms and sources.
- Haraka vs Amazon SES
- Haraka vs Brevo Transactional Email
- Haraka vs Elastic Email
- Haraka vs Hyvor Relay
- Haraka vs KumoMTA
- Haraka vs Larasend
- Haraka vs Loops Transactional Email
- Haraka vs MailerSend
- Haraka vs Mailgun
- Haraka vs Mailjet
- Haraka vs Mailtrap Email API/SMTP
- Haraka vs Plunk
- Haraka vs Postal
- Haraka vs Postmark
- Haraka vs Resend
- Haraka vs SendGrid
- Haraka vs SendLayer
- Haraka vs SMTP2GO
- Haraka vs SocketLabs