Email transaccional: comparación

Haraka vs Larasend

Precios, funciones documentadas y límites de fuentes oficiales fechadas, lado a lado. Lo desconocido sigue siendo desconocido; con unidades de facturación distintas no se pueden comparar los costes directamente.

  • Haraka

    Última comprobación de fuentes: 10 nov 2026

    Para quién esHaraka 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.

  • Larasend

    Última comprobación de fuentes: 9 nov 2026

    Para quién esLarasend 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.

Qué responden las fuentes

Una lectura de la documentación oficial revisada de Haraka y Larasend. No es una prueba práctica, una clasificación ni la recomendación de un producto.

Preguntas de compra respondidas para ambos
1 requisito
Documentado solo para uno
5 requisitos
Sin verificar para ninguno
1 requisito
Precios
Aún no comparables

Precio

  • Haraka

    Plan gratuito · precios de pago sin verificar ·

    • Self-hosted: sin cuota de suscripción ·
  • Larasend

    Plan gratuito · precios de pago sin verificar ·

    • Self-hosted: sin cuota de suscripción ·

Aún no hay una comparación de precios completa en igualdad de condiciones; los próximos pasos indican qué falta.

Preguntas de compra respondidas para ambos

Aunque las etiquetas coincidan, revisa en cada fuente las diferencias de planes, unidades y alcance.

Volumen de envíos
Haraka 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.
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.

Límites que revisar

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

Aún sin verificar

No hay fuentes revisadas para ninguno de los productos sobre: cargos por exceso.

Documentado solo para un producto, en la tabla de abajo: Haraka: IP dedicada y soporte; Larasend: dominios, retención de registros y webhooks y eventos.

«Sin verificar» significa que nuestras fuentes revisadas no lo establecen. No significa que a un producto le falte la función ni que no cueste nada.

Evidencia lado a lado

Valores documentados con sus fuentes y fechas de comprobación; los requisitos que las fuentes no establecen quedan marcados.

  • Documentado como compatible
  • Documentado como no compatible
  • Sin verificar Las fuentes no lo establecen
  • No aplica
Alcance y límites documentados; las dimensiones sin verificar siguen como desconocidas.
RequisitoHarakaLarasend
Precios
Plan gratuito · precios de pago sin verificar

Plan gratuito · precios de pago sin verificar

Para quién
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.

Comprobado el 6 nov 2026 · Haraka: haraka-project

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.

Comprobado el 6 nov 2026 · Larasend: larasend-project

Límites de cobertura
Haraka is not a mail store, a local delivery agent or an IMAP server and is designed to work alongside those systems.

Comprobado el 6 nov 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.
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.

Comprobado el 6 nov 2026 · Larasend: larasend-project

Volumen de envíos
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.

Comprobado el 10 nov 2026 · Haraka: haraka-outbound-project

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.

Comprobado el 9 nov 2026 · Larasend: larasend-project

DominiosSin verificar
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.

Comprobado el 9 nov 2026 · Larasend: larasend-project

Retención de registrosSin verificar
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.

Comprobado el 9 nov 2026 · Larasend: larasend-project

Webhooks y eventosSin verificar
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.

Comprobado el 9 nov 2026 · Larasend: larasend-project

IP dedicada
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.

Comprobado el 10 nov 2026 · Haraka: haraka-outbound-project

Sin verificar
Soporte
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.

Comprobado el 10 nov 2026 · Haraka: haraka-project

Sin verificar
Nota de cobertura

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.

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.

1 requisito sin evidencia revisada aquí

Sin verificar significa que las fuentes revisadas no lo establecen; no significa que el producto no lo tenga ni que no cueste nada.

  • Cargos por exceso Haraka: sin verificar · Larasend: sin verificar

Próximos pasos

  • Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de Haraka en su página oficial de precios; aquí solo está verificado su plan gratuito.
  • Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de Larasend en su página oficial de precios; aquí solo está verificado su plan gratuito.
  • Pregunta a Haraka por estos puntos: cargos por exceso, dominios y retención de registros. Nuestras fuentes aún no los confirman.
  • Pregunta a Larasend por estos puntos: cargos por exceso, IP dedicada y soporte. Nuestras fuentes aún no los confirman.

Las comisiones nunca cambian los costes, la idoneidad ni el orden.