Your application already knows how to send mail through Amazon SES; NitroMTA lets it keep that code, change the endpoint and keys, and deliver from IP addresses you actually control. The engine answers a submission only after the message is committed to disk, so accepted mail survives a crash, a power cut, and even the loss of its host when the disk survives. Capture mode runs the whole engine locally and shows each message in a browser at port 9090 instead of sending it, which makes testing painless before any DNS exists. Out in production, new IPs warm up receiver by receiver from fifty messages a day, rising after clean days and backing off when complaints, bounces, or throttling climb. Each provider gets its own connection limits and cooldowns, hard bounces and spam complaints suppress the address automatically, and outgoing mail is DKIM-signed and sent over TLS with MTA-STS and DANE verified where published. Templates, identities, configuration sets, tenants, dedicated IPs, and SES-shaped events through an SNS subset cover the SES surface your tooling expects, and a CLI explains why any given message is still waiting. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Cold outreach dies in the spam folder long before a prospect reads it, and Warmbly is the open-source platform that keeps your mailboxes warm, capped, and credible while campaigns run from the accounts you already own. Connect Google Workspace, Microsoft 365, or any SMTP and IMAP mailbox, and Warmbly checks SPF and DMARC records, scores mailbox health, then warms each account gradually, starting near 10 messages a day and ramping toward a 40-per-day ceiling instead of blasting from day one. Campaigns run as multi-step sequences spread across many mailboxes, with per-mailbox daily caps, minimum spacing between sends, and weekday sending windows, so volume grows without one account absorbing all the risk. Opens, clicks, bounces, and complaints stream into a deliverability view with suppression handling, while every reply from every mailbox lands in one unified inbox your whole team can work in real time. A built-in CRM tracks contacts, pipelines, deals, tasks, and meetings next to the conversations that created them. Visual playbooks react the moment a reply, booking, bounce, or warmup dip arrives: branch on intent or confidence, let an AI step read the reply and act only with the actions you allow, open the deal, post to Slack, update HubSpot or Pipedrive, and test the whole path on a canvas before it goes live. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Larasend gives Laravel teams a self-hosted transactional email platform that sends through their own Amazon SES or Cloudflare account while keeping the dashboard, delivery logs, and message data on their own servers. Send mail with a simple POST to the emails API, or point existing mailables and notifications at the Larasend transport with one environment variable and no code rewrite. Every message lands in an activity dashboard where you can filter by status, search recipients and message IDs, open a preview with headers and metrics, and resend failures in one click. Delivery, bounce, complaint, open, and click events stream back from the provider and update each message timeline, so a missing receipt becomes a traceable record instead of a support mystery. Suppression lists build themselves from bounces and complaints, and guardrails watch complaint rates and verified domains before reputation damage can spread. Scoped API keys with expiration and rotation keep each project separate, while workspace roles control who can view, send, and administer. When replies arrive, the shared inbox threads inbound and outbound mail into conversations your team can assign, snooze, annotate, and answer with attachments and drafts. Webhooks notify your other systems about deliveries and inbound mail, and reusable templates keep recurring notices consistent across projects. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Parse DMARC reads the DMARC aggregate reports that Google, Microsoft, and Yahoo email about your domain every day and shows you, in one dashboard, who is sending mail as you and whether it passes authentication. It fetches the reports over IMAP, unpacks the gzip, zip, and XML attachments automatically, and charts your pass rate, message volume, and top sending sources at a glance. Any report opens down to its raw records, so when an unfamiliar IP starts sending as you, the evidence is one click away instead of buried in XML. Reports forwarded through Exchange or Outlook as message attachments are unwrapped too, and a local Maildir intake covers servers where the mailbox lives on the same host. A built-in generator writes your _dmarc TXT record from a form, so tightening your policy does not mean hand-writing DNS syntax from memory. Twenty-eight Prometheus metrics and a shipped Grafana dashboard move the same data into the monitoring stack you already run. An MCP server lets an AI assistant query your reports directly, asking which sources failed DKIM this week in plain language. Everything stores in a single SQLite file inside one static Go binary, with dark mode for late-night incident reviews. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.