Transactional email comparison

Haraka vs Loops Transactional Email

Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.

What the evidence answers

A reading of reviewed official documentation for Haraka and Loops Transactional Email. It is not a hands-on test, a ranking or a recommendation of one product.

Common buyer questions answered
1 requirement
Documented for one
3 requirements
Not verified for either
3 requirements
Prices
Not like-for-like yet

Price

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.

Dedicated IP
Haraka 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.
Loops Transactional Email The Loops API can return Loops’ dedicated sending IP addresses, which the SDK README says is intended for rare cases where you need to whitelist them.

Limits to check

  • Haraka Haraka is not a mail store, a local delivery agent or an IMAP server and is designed to work alongside those systems.
  • Haraka 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.
  • Loops Transactional Email The selected Loops Ruby SDK documentation says the package requires an API key.

Not verified yet

No reviewed evidence for either product on log retention, webhooks and events and overage charges.

Documented for one product only, shown in the table below: Haraka: sending volume and support; Loops Transactional Email: domains.

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
Documented scope and limits; unverified dimensions remain unknown.
RequirementHarakaLoops Transactional Email
Pricing
Free plan · paid prices not verified

Price not 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.

Verified Nov 6, 2026 · Haraka: haraka-project

The publisher describes an official Ruby SDK for Loops, an email platform for software companies.

Verified Nov 4, 2026 · Loops Transactional Email: loops-source

Coverage limits
Haraka is not a mail store, a local delivery agent or an IMAP server and is designed to work alongside those systems.

Verified Nov 6, 2026 · Haraka: haraka-project

  • Self-hosted 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.
The selected Loops Ruby SDK documentation says the package requires an API key.

Verified Nov 4, 2026 · Loops Transactional Email: loops-source

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.

Verified Nov 10, 2026 · Haraka: haraka-outbound-project

Not verified
DomainsNot verified
When an email message’s sender is set through the API, Loops takes only the sender username and appends the team’s sending domain automatically.

Supplier-maintained Node.js SDK README at release v7.4.0 captured on 9 November 2026; documentation of the API client, not a tested sending result or current plan entitlement. This parameter belongs to the email-message update endpoint; domain verification and the number of sending domains are not described in the README.

Verified Nov 10, 2026 · Loops Transactional Email: loops-js-project

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.

Verified Nov 10, 2026 · Haraka: haraka-outbound-project

The Loops API can return Loops’ dedicated sending IP addresses, which the SDK README says is intended for rare cases where you need to whitelist them.

Supplier-maintained Node.js SDK README at release v7.4.0 captured on 9 November 2026; documentation of the API client, not a tested sending result or current plan entitlement. The README does not say that a customer can reserve a dedicated IP of its own, or on which plans.

Verified Nov 10, 2026 · Loops Transactional Email: loops-js-project

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.

Verified Nov 10, 2026 · Haraka: haraka-project

Not verified
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.

Supplier-maintained Ruby SDK README at a pinned revision, captured 4 November 2026. Examples describe the selected client, not complete service coverage, current plan entitlements or a tested sending result.

3 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.

  • Log retention Haraka: not verified · Loops Transactional Email: not verified
  • Webhooks and events Haraka: not verified · Loops Transactional Email: not verified
  • Overage charges Haraka: not verified · Loops Transactional Email: not verified

Next steps

  • Confirm Haraka's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Confirm Loops Transactional Email's current prices, billing term and taxes on its official pricing page.
  • Ask Haraka about log retention, webhooks and events and overage charges; our sources do not establish them yet.
  • Ask Loops Transactional Email about log retention, webhooks and events and overage charges; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.