Larasend
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 facts
- 7
- Offers
- 1
- Sources
- 1
- Pricing
- Free offer
Overview
Built for Laravel teams on SES
Larasend is a self-hosted transactional email platform for Laravel teams. It provides an HTTP API, a dashboard with an activity log, API keys, delivery events, suppressions and a Laravel mail transport, and it sends through your own Amazon SES account. Your app sends through the Laravel driver or the API; Larasend validates the request, stores the MIME payload and metadata, queues delivery, and a worker sends the raw email through SES.
SES events for delivery, bounces, complaints, opens, clicks and suppressions come back through a webhook and update the dashboard, metrics and suppression list. API keys are project-scoped with scopes, expiry and rotation, and the README lists source health, SES quota sync and guardrails for verified domains, suppressions and complaint rate.
Read the full editorial overview
Requirements and limits
You need an Amazon SES account with a verified sending domain, Docker and Docker Compose for production-style installs, PostgreSQL 17 or newer, and Redis 7 or newer if you use the bundled Compose stack; local development needs PHP 8.4+ and Node.js 22+. SES stays the final authority on provider-side rejection, and Larasend accepts API sends even when its SES quota sync is stale or unavailable.
At the captured release the Laravel mail driver was not yet on Packagist and installed from a GitHub repository. The roadmap lists more providers beyond SES, deeper deliverability reporting and an update workflow for self-hosted Docker installs, so treat those as planned. SES charges are separate and were not captured.
Licence and maintenance
Larasend is open-source software under the MIT licence. This profile uses the README from the v0.1.0 release tag, published on 5 July 2026, which GitHub still listed as the latest release on 8 November 2026. By then the main branch had a commit dated 6 November 2026, and its README named Cloudflare Email Service as a second sending provider; the repository was created in May 2026, so this is a young project.
Other changes on the main branch after the v0.1.0 tag are not covered here. No installation or sending test was run for this profile.
Sources
Larasend: larasend-project · Evidence: documentation · Not checked
Plans & prices
Prices as listed by Larasend, before any tax or fee the pricing page does not state.
Scroll the table sideways for every column.
| Plan | Rate period not stated |
|---|---|
| Plan: Self-hosted | FreeTax: Confirm at checkoutUpfront: not established ConditionsDated 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. Sending runs through the buyer's own Amazon SES account, whose charges are separate and were not captured. |
Documented facts
Each fact comes from official documentation and shows when it was 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.
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.
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.
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.
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.
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.
Applies to the facts above: 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.
Not confirmed in our sources
We have not confirmed these terms for Larasend in the linked documentation. That does not mean Larasend lacks them; confirm them before you rely on them.
- Dedicated IP
- Support
- Overage charges
Sources & methodology
Facts come from the linked documentation. Documentation checks are not hands-on tests, and readable sources can have incomplete coverage.
Discovered an undocumented discrepancy or pricing shift? Submit a correction request.
Submit correctionLarasend alternatives
Other transactional email tools to weigh. Different billing units do not establish a cost winner, so compare plans side by side.
Resend
Transactional email
Sends application email, such as password resets and order confirmations, through the /emails API; marketing broadcasts use a separate API. · Evidence needs recheck
Documented price$20/moPrice needs recheckPrice terms
Documented price: $20/mo · Plan: Pro · 1-month commitment
Postmark
Transactional email
Sends transactional email and keeps bulk or broadcast email on separate Message Streams. · Evidence needs recheck
Documented price$15/moPrice needs recheckPrice terms
Documented price: $15/mo · Plan: Basic · 1-month commitment
Mailgun
Transactional email
Sends application email through an HTTP API or an SMTP endpoint. · Evidence needs recheck
Documented price$15/moPrice needs recheckPrice terms
Documented price: $15/mo · Plan: Basic · 1-month commitment
Larasend comparisons
Compare two products in the same category using their documented terms and sources.
- Larasend vs Amazon SES
- Larasend vs Brevo Transactional Email
- Larasend vs Elastic Email
- Larasend vs Hyvor Relay
- Larasend vs KumoMTA
- Larasend vs MailerSend
- Larasend vs Mailgun
- Larasend vs Mailjet
- Larasend vs Postmark
- Larasend vs Resend
- Larasend vs SendGrid
- Larasend vs SMTP2GO
- Larasend vs Haraka
- Larasend vs Loops Transactional Email
- Larasend vs Mailtrap Email API/SMTP
- Larasend vs Plunk
- Larasend vs Postal
- Larasend vs SendLayer
- Larasend vs SocketLabs