Transactional email comparison

Loops Transactional Email vs Plunk

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 Loops Transactional Email and Plunk. It is not a hands-on test, a ranking or a recommendation of one product.

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

Price

  • Loops Transactional Email

    Price not verified

  • Plunk

    Documented price: 1.00 per 1,000 emails overage (currency not stated) · Plan: Pay-as-you-go · no minimum commitment ·

    • Self-hosted: no subscription charge ·
    • Free tier: no subscription charge ·
    • Pay-as-you-go: 1.00 (currency not stated) overage per 1,000 emails, no monthly base charge · no minimum commitment ·

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.

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

Limits to check

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

Not verified yet

No reviewed evidence for either product on overage charges.

Documented for one product only, shown in the table below: Loops Transactional Email: dedicated IP; Plunk: sending volume, log retention, webhooks and events and support.

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.
RequirementLoops Transactional EmailPlunk
Pricing
Price not verified
Documented price: 1.00 per 1,000 emails overage (currency not stated) · Plan: Pay-as-you-go · no minimum commitment

See all 3 offers

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

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

Plunk describes a platform for transactional email, marketing campaigns and workflow automation.

Verified Nov 3, 2026 · Plunk: plunk-readme

Coverage limits
The selected Loops Ruby SDK documentation says the package requires an API key.

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

Plunk documents a self-hosted deployment option.

Verified Nov 3, 2026 · Plunk: plunk-readme

  • Self-hosted Self-hosting needs Docker and Docker Compose, an AWS SES account for sending and a domain name with subdomains for each service.
Sending volumeNot verified
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.

Verified Nov 10, 2026 · Plunk: plunk-docs-billing-project

Domains
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

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.

Verified Nov 10, 2026 · Plunk: plunk-project

Log retentionNot verified
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.

Verified Nov 10, 2026 · Plunk: plunk-docs-retention-project

Webhooks and eventsNot verified
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.

Verified Nov 10, 2026 · Plunk: plunk-docs-webhooks-project

Dedicated IP
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

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

Verified Nov 10, 2026 · Plunk: plunk-project

Coverage note

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

  • Overage charges Loops Transactional Email: not verified · Plunk: not verified

Next steps

  • Confirm Loops Transactional Email's current prices, billing term and taxes on its official pricing page.
  • Confirm the currency of Plunk's displayed price at checkout.
  • Ask Loops Transactional Email about overage charges, sending volume and log retention; our sources do not establish them yet.
  • Ask Plunk about overage charges and dedicated IP; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.