Single endpoint
One HTTP call, one JSON payload, one API key Bearer. Mail-Reacher routes to the right provider for your environment, applies the template, handles variables and persists the log.
Your dev emails never reach real users. Ta prod livre via your provider habituel (SES, Postmark, Mailgun, SendGrid ou your SMTP). Une seule API, multi-environnement, anti vendor-lock-in.
Like Mailtrap for simulation, but it actually delivers in production — and gives you Mail-Check to audit SPF / DKIM / DMARC / blacklists on every send.
A unified transport for the major providers. Your code does not change, the provider can — switch in one click, or route by project.
SPF, DKIM, DMARC, blacklists, reverse DNS, headers, content, TLS — a complete report for every address, on demand or continuously.
One endpoint POST /api/emails/send, environment-scoped API keys, and a SDK Laravel SDK to wire your sends in one line. The rest — provider routing, queues, retries, webhooks — lives in Mail-Reacher.
One HTTP call, one JSON payload, one API key Bearer. Mail-Reacher routes to the right provider for your environment, applies the template, handles variables and persists the log.
Each key carries an environment (test / prod) and granular scopes (emails:send, templates:read, contacts:write). Rotate anytime.
Facade MailReacher::send() on the PHP side, configuration via .env, integration native Laravel queues. The SDK handles retries, idempotency and structured logs.
Visual editor MJML avec real-time preview and dynamic variables {{ variable }}. Rendering stays reliable across email clients, and each template can be reused between test and production environments.
Mail-Reacher injects its own pixel de tracking et rewrites links in sent emails. You read opens and clicks from the dashboard and API without depending on each provider's webhook format — tracking stays consistent when you switch providers.
Resend, Postmark, Mailgun, SendGrid are excellent providers — but once your code is coupled to their SDK, switching is expensive. Mail-Reacher abstracts sending: you code against a stable API, choose the provider in configuration, and can switch SES → Postmark without opening a single code file.
A successfully sent email is not an email that arrive. SPF, DKIM, DMARC, blacklists, reverse DNS, headers, content — every detail matters and each provider exposes these signals differently, sometimes not at all. The Mail-Reacher's Mail-Check consolidates everything into a readable score out of 10, tracked over time.
How many apps still send real email from staging by accident? With Mail-Reacher, the API key carries the environment. mr_test_… simulate delivery in an internal inbox, mr_live_… sends for real. The code is identical. No more environment variable to forget.
An email that renders well in Gmail can break in Outlook, and a rushed template change can destabilize everything. Mail-Reacher uses MJML to generate HTML that holds up across major clients, with a visual editor and real-time preview — you see what your recipients will see.
Using SES, Postmark, Mailgun, SendGrid, Brevo or a custom SMTP on the same domain is possible. It can help you separate traffic, reduce lock-in and prepare fallback routes — but it needs clean DNS, consistent authentication and careful monitoring.
Mail-Reacher is designed for this exact setup: one integration in your app, provider choice in configuration, environment separation, unified logs, and Mail-Check scans so you can see when a DNS, content or provider change starts hurting deliverability.
Create a project. Connect a provider. Send a mail-check.
Decide later.