Email transaccional: comparación
Larasend vs Plunk
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.
Ú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.
Última comprobación de fuentes: 10 nov 2026
Para quién esPlunk describes a platform for transactional email, marketing campaigns and workflow automation.
Qué responden las fuentes
Una lectura de la documentación oficial revisada de Larasend y Plunk. No es una prueba práctica, una clasificación ni la recomendación de un producto.
- Preguntas de compra respondidas para ambos
- 4 requisitos
- Documentado solo para uno
- 1 requisito
- Sin verificar para ninguno
- 2 requisitos
- Precios
- Aún no comparables
Precio
Larasend
Plan gratuito · precios de pago sin verificar ·
- Self-hosted: sin cuota de suscripción ·
Plunk
Precio documentado: 1,00 por 1,000 emails (excedente) (moneda no indicada) · Plan: Pay-as-you-go · sin permanencia mínima ·
- Self-hosted: sin cuota de suscripción ·
- Free tier: sin cuota de suscripción ·
- Pay-as-you-go: 1,00 (moneda no indicada) excedente por 1,000 emails, sin cuota base mensual · sin permanencia mínima ·
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
- 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.
- Dominios
- 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.
- Retención de registros
- 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 y eventos
- 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.
Límites que revisar
- 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.
Aún sin verificar
No hay fuentes revisadas para ninguno de los productos sobre: IP dedicada y cargos por exceso.
Documentado solo para un producto, en la tabla de abajo: Plunk: soporte.
«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
| Requisito | Larasend | Plunk |
|---|---|---|
| Precios | Plan gratuito · precios de pago sin verificar | Precio documentado: 1,00 por 1,000 emails (excedente) (moneda no indicada) · Plan: Pay-as-you-go · sin permanencia mínima |
| Para quién | 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 | Plunk describes a platform for transactional email, marketing campaigns and workflow automation. Comprobado el 3 nov 2026 · Plunk: plunk-readme |
| Límites de cobertura | 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 | Plunk documents a self-hosted deployment option. Comprobado el 3 nov 2026 · Plunk: plunk-readme
|
| Volumen de envíos | 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 | 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. Comprobado el 10 nov 2026 · Plunk: plunk-docs-billing-project |
| Dominios | 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 | 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. Comprobado el 10 nov 2026 · Plunk: plunk-project |
| Retención de registros | 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 | 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. Comprobado el 10 nov 2026 · Plunk: plunk-docs-retention-project |
| Webhooks y eventos | 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 | 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. Comprobado el 10 nov 2026 · Plunk: plunk-docs-webhooks-project |
| Soporte | Sin verificar | 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. Comprobado el 10 nov 2026 · Plunk: plunk-project |
| 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. | 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 requisitos 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.
- IP dedicada Larasend: sin verificar · Plunk: sin verificar
- Cargos por exceso Larasend: sin verificar · Plunk: sin verificar
Próximos pasos
- 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.
- Confirma al pagar la moneda del precio mostrado de Plunk.
- Pregunta a Larasend por estos puntos: IP dedicada, cargos por exceso y soporte. Nuestras fuentes aún no los confirman.
- Pregunta a Plunk por estos puntos: IP dedicada y cargos por exceso. Nuestras fuentes aún no los confirman.
- LarasendIr a LarasendPerfil y planes
- PlunkIr a PlunkPerfil y planes
Las comisiones nunca cambian los costes, la idoneidad ni el orden.