Transactional email comparison
Larasend 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.
Latest evidence check Nov 9, 2026
Who it is forLarasend 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.
Latest evidence check Nov 10, 2026
Who it is forThe publisher describes an official Ruby SDK for Loops, an email platform for software companies.
What the evidence answers
A reading of reviewed official documentation for Larasend and Loops Transactional Email. It is not a hands-on test, a ranking or a recommendation of one product.
- Common buyer questions answered
- 1 requirement
- Documented for one
- 4 requirements
- Not verified for either
- 2 requirements
- Prices
- Not like-for-like yet
Price
Larasend
Free plan · paid prices not verified ·
- Self-hosted: no subscription charge ·
Loops Transactional Email
Price not verified
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
- 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.
- 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.
Limits to check
- 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.
- 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 support and overage charges.
Documented for one product only, shown in the table below: Larasend: sending volume, log retention and webhooks and events; Loops Transactional Email: dedicated IP.
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
| Requirement | Larasend | Loops Transactional Email |
|---|---|---|
| Pricing | Free plan · paid prices not verified | Price not verified |
| Who it is for | 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. Verified Nov 6, 2026 · Larasend: larasend-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 | 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. Verified Nov 6, 2026 · Larasend: larasend-project | The selected Loops Ruby SDK documentation says the package requires an API key. Verified Nov 4, 2026 · Loops Transactional Email: loops-source |
| Sending volume | 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. Verified Nov 9, 2026 · Larasend: larasend-project | Not verified |
| Domains | 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. Verified Nov 9, 2026 · Larasend: larasend-project | 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 | 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. Verified Nov 9, 2026 · Larasend: larasend-project | Not verified |
| Webhooks and events | 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. Verified Nov 9, 2026 · Larasend: larasend-project | Not verified |
| Dedicated IP | Not verified | 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 |
| Coverage note | 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. | 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.
- Support Larasend: not verified · Loops Transactional Email: not verified
- Overage charges Larasend: not verified · Loops Transactional Email: not verified
Next steps
- Confirm Larasend'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 Larasend about support, overage charges and dedicated IP; our sources do not establish them yet.
- Ask Loops Transactional Email about support, overage charges and sending volume; our sources do not establish them yet.
- LarasendVisit LarasendProfile and plans
- Loops Transactional EmailVisit Loops Transactional EmailProfile and plans
Commissions never change costs, eligibility or rankings.