Sends application email, such as password resets and order confirmations, through the /emails API; marketing broadcasts use a separate API. · Preuves à revérifier
Prix documenté20 $US/moisPrix à revérifierConditions tarifaires
Prix documenté : 20 $US/mois · Offre : Pro · engagement de 1 mois
Transactional email sent by API or SMTP from your application, inside an all-in-one platform that also runs marketing campaigns. · Preuves à revérifier
Prix documenté9 $US/moisPrix à revérifierConditions tarifaires
Prix documenté : 9 $US/mois · Offre : Starter · engagement non établi
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.
KumoMTA is an open-source message transfer agent designed for high-performance outbound email, comparable to commercial enterprise MTAs such as Momentum, PowerMTA and Halon.
Haraka is a Node.js SMTP server with a modular plugin architecture; the README says it handles thousands of concurrent connections and delivers thousands of messages per second.
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.
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.
KumoMTA is an open-source message transfer agent designed for high-performance outbound email, comparable to commercial enterprise MTAs such as Momentum, PowerMTA and Halon.
Haraka is a Node.js SMTP server with a modular plugin architecture; the README says it handles thousands of concurrent connections and delivers thousands of messages per second.
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.
New accounts start in the sandbox in each AWS Region: verified recipients only, at most 200 messages per 24 hours and 1 per second, until production access is granted.
KumoMTA is intended for experienced email operations professionals who are used to high-performance sending environments and familiar with DevOps practices.
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.
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.
Official SocketLabs Node.js client library README (socketlabs/socketlabs-nodejs, release 1.4.4 commit ffe9f947), captured 9 November 2026; the README describes sending through the SocketLabs Injection API. Client library documentation of the basic message type, not a tested limit. The README does not state account-level sending limits or prices.
Throughput depends on the hardware you deploy: for many millions of messages per hour the publisher advises the largest server you can, on bare metal or public or private cloud, with or without Kubernetes.
Publisher hardware guide (docs/userguide/installation/hardware.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026; supplier sizing guidance, not a measured throughput or performance test.
A default installation queues outbound mail to disk and delivers it to the appropriate MX for each recipient domain, retrying temporary failures automatically on the configured backoff schedule.
Dated publisher documentation (docs/Outbound.md) at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; supplier description, not a throughput or deliverability test. Mail is outbound only when a plugin marks it as relaying, for example after SMTP AUTH.
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.
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.
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.
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.
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.
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.
Sending events (sends, deliveries, opens, clicks, bounces, complaints, rejections, rendering failures and delivery delays) can be published to CloudWatch, Data Firehose, Pinpoint, SNS or EventBridge.
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.
Message events can be sent as webhooks to a user-defined HTTP endpoint, with queuing built in for durability if the receiving HTTP service has an error.
Publisher documentation (docs/userguide/operation/webhooks.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026. Webhooks are set up in the Lua policy script, with the log_hooks helper recommended. Supplier documentation, not a tested integration.
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.
Several pools of sending IP addresses can be managed, and specific senders or recipients can be configured to be delivered from certain IP addresses.
Postal feature list (docs.postalserver.io) captured 9 November 2026. Postal runs on your own servers, so the IP addresses are your own; no IP price or warm-up service is stated.
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.
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.
By default mail leaves through the host's default interface; IPs can be grouped into pools, and a queue tied to a pool spreads its sends across the pool's IPs by weighted round robin. Separate IPs per mail stream are recommended to isolate reputation.
Publisher documentation (docs/userguide/configuration/sendingips.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026. The sending addresses are configured on the operator's own hosts. Supplier guidance, not a deliverability test.
By default the operating system’s routing table chooses the source IP; an operator can pin outbound mail to a specific IP per sender or domain by binding the address to a local interface or alias and setting mx.bind and mx.bind_helo in a get_mx plugin hook.
Dated publisher documentation (docs/Outbound.md) at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; configuration guidance, not a deliverability test. The operator supplies and warms the IP addresses.
Community support, plus paid Professional Services and Commercial Support from the KumoMTA team.
Publisher FAQ (docs/faq/how_can_i_get_help_with_kumomta.md) at release 2026.09.29-b90d8bc1 (commit b90d8bc) captured 8 November 2026. Paid support and services are arranged by contacting the KumoMTA team; the FAQ gives no prices or response times. Community support is described on the user guide's How To Get Help page.
The README lists GitHub Issues, a mailing list (implemented as a Haraka plugin) and a getting-started screencast as the ways to get help.
Dated publisher documentation at release v3.4.0 (commit 2e1ea5b6) captured on 9 November 2026; supplier description, not a deployment or independent test. These are community channels; response times and any paid support are not stated in the README.
Paid plans can keep sending past the monthly quota with pay-as-you-go, capped by default at 5 times the quota; sending then pauses until the next billing cycle.
Plans are billed annually and the sending limit resets each month; when a plan limit is reached, SendLayer upgrades the account automatically so emails do not fail.
SendLayer pricing page captured 9 November 2026 (FAQ on billing). Supplier statement, not a tested limit; the upgrade price is not stated in that answer.
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.
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.
Publisher client README at the captured repository revision, 4 November 2026. SDK evidence is scoped to the named service; client licence does not establish service, trademark or documentation terms. No account or sending test.
Publisher client README at the captured repository revision, 4 November 2026. SDK evidence is scoped to the named service; client licence does not establish service, trademark or documentation terms. No account or sending test.
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.
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.
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.
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.
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.
Quels outils de email transactionnel proposent une offre gratuite ?
Resend, Postmark, Mailgun, SendGrid, MailerSend, SMTP2GO, Brevo Transactional Email, Elastic Email, Mailjet, Plunk, Postal, Hyvor Relay, KumoMTA, Haraka et Larasend documentent une offre gratuite sur leurs pages de tarifs officielles. Les offres gratuites limitent généralement l’usage, le nombre d’utilisateurs ou les fonctionnalités ; vérifiez les limites dans chaque fiche.
Combien coûte un logiciel de email transactionnel ?
Parmi les prix d’entrée documentés des offres payantes : Resend à partir de 20 $US/mois, Postmark à partir de 15 $US/mois, Mailgun à partir de 15 $US/mois, Amazon SES à partir de 0,16 $US par 1,000 emails, first 10 million a month (dépassement) et SendGrid à partir de 19,95 $US/mois. Les prix proviennent des pages officielles aux dates indiquées ; les unités et les périodes de facturation diffèrent, comparez donc des offres équivalentes.