Transactional email comparison

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

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

Price

  • Hyvor Relay

    Free plan · paid prices not verified ·

    • Self-hosted: no subscription charge ·
    • Enterprise License: Vendor quotation required ·
  • 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
Hyvor Relay Multiple sending domains can be managed, with DKIM signing enforced.
Plunk Custom sending domains can be verified, with DKIM and SPF support.
Log retention
Hyvor Relay 30 days of delivery logs
Plunk Rendered email HTML is kept for 90 days and API request logs for 30 days; email metadata and metrics are kept indefinitely.
Webhooks and events
Hyvor Relay Real-time event webhooks report deliveries, bounces, domain verifications and other events.
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.
Support
Hyvor Relay Self-hosted: Community support
Plunk The README lists the public Plunk documentation and a Discord server; no paid support plan is named in it.

Limits to check

  • Hyvor Relay Sign-in requires an OpenID Connect (OIDC) provider: Hyvor Relay has no login or signup system of its own.
  • Hyvor Relay Self-hosting needs a PostgreSQL database (self-hosted or managed) and Docker Compose or Docker Swarm on the app servers, running on the host network for direct access to the public IP addresses.
  • 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: Hyvor Relay: dedicated IP; Plunk: sending volume.

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.
RequirementHyvor RelayPlunk
Pricing
Free plan · paid prices not verified

See all 2 offers

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
Hyvor Relay is a self-hosted, open-source email API for developers that sends over SMTP from your own infrastructure; the README says it is powerful enough to send millions of emails a day.

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.

Verified Nov 6, 2026 · Hyvor Relay: hyvor-relay-project

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

Verified Nov 3, 2026 · Plunk: plunk-readme

Coverage limits
Sign-in requires an OpenID Connect (OIDC) provider: Hyvor Relay has no login or signup system of its own.

Hyvor Relay home page captured 8 November 2026 (FAQ); supplier statement, not a tested login. Applies to self-hosted installations of the software.

Verified Nov 9, 2026 · Hyvor Relay: hyvor-relay-home-20261109a

  • Self-hosted Self-hosting needs a PostgreSQL database (self-hosted or managed) and Docker Compose or Docker Swarm on the app servers, running on the host network for direct access to the public IP addresses.
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
Multiple sending domains can be managed, with DKIM signing enforced.

Hyvor Relay home page captured 8 November 2026; supplier feature description, not a tested setup. The page states no limit on the number of domains.

Verified Nov 9, 2026 · Hyvor Relay: hyvor-relay-home-20261109a

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 retention
30 days of delivery logs

Hyvor Relay home page captured 8 November 2026: full delivery logs, including headers, status and SMTP traces, are searchable for 30 days. The project README gives the same 30 days for send logs and SMTP conversations. Supplier statement, not a test.

Verified Nov 9, 2026 · Hyvor Relay: hyvor-relay-home-20261109a

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 events
Real-time event webhooks report deliveries, bounces, domain verifications and other events.

Hyvor Relay home page captured 8 November 2026; supplier feature description, not a tested integration. No limit on webhook endpoints is stated.

Verified Nov 9, 2026 · Hyvor Relay: hyvor-relay-home-20261109a

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
Sending uses the public IPv4 addresses of your own servers (one or more per server); Hyvor Relay chooses the sending IP by the queue each IP belongs to, which you can configure.

Hyvor Relay self-hosting guide (relay.hyvor.com/hosting) captured 8 November 2026. In the guide the operator rents or buys the servers, and so their IP addresses, from a provider of their choice. Supplier guidance, not a deployment or deliverability test.

Verified Nov 9, 2026 · Hyvor Relay: hyvor-relay-hosting-20261109a

Not verified
Support
  • Self-hosted Community support
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

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 Hyvor Relay: not verified · Plunk: not verified

Next steps

  • Confirm Hyvor Relay's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Confirm the currency of Plunk's displayed price at checkout.
  • Ask Hyvor Relay about overage charges and sending volume; 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.