Email transaccional: comparación
Loops Transactional Email 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: 10 nov 2026
Para quién esThe publisher describes an official Ruby SDK for Loops, an email platform for software companies.
Ú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 Loops Transactional Email y Plunk. 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
Loops Transactional Email
Precio no verificado
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.
- Dominios
- Loops Transactional Email 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.
- Plunk Custom sending domains can be verified, with DKIM and SPF support.
Límites que revisar
- Loops Transactional Email The selected Loops Ruby SDK documentation says the package requires an API key.
- 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: cargos por exceso.
Documentado solo para un producto, en la tabla de abajo: Loops Transactional Email: IP dedicada; Plunk: volumen de envíos, retención de registros, webhooks y eventos y 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 | Loops Transactional Email | Plunk |
|---|---|---|
| Precios | Precio no verificado | Precio documentado: 1,00 por 1,000 emails (excedente) (moneda no indicada) · Plan: Pay-as-you-go · sin permanencia mínima |
| Para quién | The publisher describes an official Ruby SDK for Loops, an email platform for software companies. Comprobado el 4 nov 2026 · Loops Transactional Email: loops-source | Plunk describes a platform for transactional email, marketing campaigns and workflow automation. Comprobado el 3 nov 2026 · Plunk: plunk-readme |
| Límites de cobertura | The selected Loops Ruby SDK documentation says the package requires an API key. Comprobado el 4 nov 2026 · Loops Transactional Email: loops-source | Plunk documents a self-hosted deployment option. Comprobado el 3 nov 2026 · Plunk: plunk-readme
|
| Volumen de envíos | Sin verificar | 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 | 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. Comprobado el 10 nov 2026 · Loops Transactional Email: loops-js-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 | Sin verificar | 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 | Sin verificar | 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 |
| IP dedicada | 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. Comprobado el 10 nov 2026 · Loops Transactional Email: loops-js-project | Sin verificar |
| 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 | 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. | 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. |
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 Loops Transactional Email: sin verificar · Plunk: sin verificar
Próximos pasos
- Confirma los precios actuales, el plazo de facturación y los impuestos de Loops Transactional Email en su página oficial de precios.
- Confirma al pagar la moneda del precio mostrado de Plunk.
- Pregunta a Loops Transactional Email por estos puntos: cargos por exceso, volumen de envíos y retención de registros. Nuestras fuentes aún no los confirman.
- Pregunta a Plunk por estos puntos: cargos por exceso e IP dedicada. Nuestras fuentes aún no los confirman.
- Loops Transactional EmailIr a Loops Transactional EmailPerfil y planes
- PlunkIr a PlunkPerfil y planes
Las comisiones nunca cambian los costes, la idoneidad ni el orden.