Transactional email comparison

Hyvor Relay vs Loops Transactional Email

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

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

Price

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.
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.
Dedicated IP
Hyvor Relay 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.
Loops Transactional Email 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.

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.
  • Loops Transactional Email The selected Loops Ruby SDK documentation says the package requires an API key.

Not verified yet

No reviewed evidence for either product on sending volume and overage charges.

Documented for one product only, shown in the table below: Hyvor Relay: 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.
RequirementHyvor RelayLoops Transactional Email
Pricing
Free plan · paid prices not verified

See all 2 offers

Price not verified
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

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

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

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.
The selected Loops Ruby SDK documentation says the package requires an API key.

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

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

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

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

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

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

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

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

2 requirements 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.

  • Sending volume Hyvor Relay: not verified · Loops Transactional Email: not verified
  • Overage charges Hyvor Relay: not verified · Loops Transactional Email: 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 Loops Transactional Email's current prices, billing term and taxes on its official pricing page.
  • Ask Hyvor Relay about sending volume and overage charges; our sources do not establish them yet.
  • Ask Loops Transactional Email about sending volume, overage charges and log retention; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.