MiniMailer

I built MiniMailer for the code I was writing, not for a marketing team. A Laravel app that sends a receipt. A support agent that answers a ticket. A job that finishes at three in the morning and mails the result to whoever asked for it.

The ordinary parts are ordinary. You verify a sending domain, then send through the REST API or point Laravel's mailer at it with one line of config. Every event that happens to the message afterwards comes back as a signed webhook: delivered, bounced, opened, clicked, complained. Inbound mail arrives parsed into JSON instead of raw MIME.

Three things I did differently.

The data stays in Europe, on every plan. Messages, addresses, events and backups sit in one European region, and the monitoring that reads error traces sits in Europe too. The free tier runs on the same infrastructure as the paid ones. I picked that before the first customer, because retrofitting it later is a migration rather than a setting.

Agents are senders, not integrations. There's an MCP server beside the REST API carrying 9 tools, so an agent connects once, reads your account as resources, and sends through calls that are safe to retry. Fewer tools described well beat one tool per endpoint, and every send is idempotent, so a retry after a timeout doesn't mail twice.

Reputation is tracked per agent. Three agents on one domain share one score, and the day it drops your dashboard can't tell you which of them spent it. MiniMailer keeps a second ledger one level down, per sending agent. You pay for it with one more field on the request: the agent has to say who it is.

It's in beta and closed for now, opening in Q4 2026. Leave your address on the waitlist at minimailer.app and I'll write to you when it opens.

If something here doesn't match what you find, tell me: hello@maudev.me.