Built as a developer-first alternative to SendGrid, Mailgun, and Postmark, Posta delivers a complete self-hosted email infrastructure platform handling both outbound delivery and inbound reception through a single HTTP API with official SDKs for Go, PHP, and Java. The Go backend processes email through Redis and Asynq with automatic retries, priority queues, and async delivery while PostgreSQL stores templates, contacts, campaigns, and delivery analytics. Outbound features include versioned multi-language templates with variable substitution and stylesheet inlining, bulk campaigns with subscriber targeting and A/B testing per-variant metrics, scheduled timezone-aware delivery with draft/paused/cancelled lifecycle states, email address verification checking syntax, MX records, disposable domains, and role accounts, plus web view links with signed expiring URLs and one-click unsubscribe headers. The built-in SMTP receiver with TLS handles inbound email at your domains, parses messages and attachments, scores spam, and forwards structured payloads to your application via HMAC-verified webhooks with real-time SSE notification streams. The Vue-based dashboard manages templates, SMTP server pools, domains, contacts, API keys, campaigns, and email logs with dark and light mode support while admin-level platform metrics expose delivery rate trends, bounce rate graphs, and latency percentiles alongside Prometheus integration and daily health reports. Deploy via Docker with PostgreSQL and Redis. 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.

Plunk consolidates transactional emails, marketing campaigns, and drip automation into one platform riding AWS SES at roughly one-tenth of a cent per message, with zero per-contact charges regardless of list size. The Turborepo monorepo architecture separates the Express.js API server (handling REST requests with Prisma ORM against PostgreSQL) from a dedicated BullMQ worker process that consumes email, campaign, and workflow jobs independently for fault isolation and horizontal scaling. Transactional emails support HTML bodies, template variable substitution via React Email components, attachments, and custom headers with dedicated SMTP relay on ports 465 and 587 for integration with existing frameworks. The campaign system sends newsletters and product updates to full contact lists or dynamically segmented audiences based on contact properties and behavioral events, with scheduling, A/B testing, and performance tracking for opens, clicks, and bounces. The workflow automation builder creates event-triggered sequences with delays, conditional branches, and webhook steps for lifecycle campaigns like onboarding drip sequences and re-engagement flows. Contact management stores unlimited contacts with custom data fields, CSV import, full activity history, and dynamic segmentation. Custom domain verification with DKIM and SPF ensures deliverability, while inbound email processing handles incoming messages with custom routing rules. Docker Compose deployment runs five containers including PostgreSQL, Redis, MinIO for S3-compatible storage, and ntfy for notifications. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Product teams get a visual home for the transactional and lifecycle emails their application sends with Senlo, which sits on top of the delivery provider they already use instead of replacing it. A drag-and-drop editor builds responsive templates without hand-written HTML, exports to MJML or plain HTML when needed, and keeps templates versioned so edits can be reviewed and rolled back safely. Event-triggered automations turn product activity into onboarding sequences, trial reminders, and win-back flows: your app feeds contact events through the API, and Senlo decides which message goes out next. The transactional API sends a rendered template in one call, so receipts, password resets, and alerts stop living as scattered strings in your codebase. Delivery stops being a black box, with sends, deliveries, bounces, and engagement tracked per workspace, a live feed of failures, and suppressions that block bad addresses before they damage sender reputation. Because sending stays with Resend, Postmark, SES, Mailgun, or your own SMTP server, switching providers never means rebuilding a template. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

MillionSend is an open-source email platform you run yourself that sends transactional and marketing mail through your own AWS SES account behind a Resend-compatible API. Every message you send becomes a row in the dashboard, and every row opens into a timeline of SES events with the raw payload and the SMTP diagnostic when something bounces. Daily metrics chart sent, delivered, opened, clicked, bounced, and complained volumes against SES thresholds, and broadcasts stop on their own at five percent bounces or 0.1 percent complaints before Amazon can pause your account. Contacts live once for the whole team with custom properties and subscribe state, while segments and topics decide exactly who receives each broadcast. You compose broadcasts from reusable templates with per-contact merge fields, schedule them ahead, and cancel them while they wait. Applications that only speak SMTP send through the relay on port 2587 with an API key as the password, and HTTP integrations use idempotency keys, request logs with secrets redacted, and signed webhooks with a delivery history. Guided domain setup handles DKIM records, hard bounces and complaints are suppressed automatically, and every recipient gets an RFC 8058 one-click unsubscribe. Receiving and agent-ready inboxes are included in beta for mail sent to your verified domains. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.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.

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.

Your scanner still emails PDFs, your backup scripts still send nightly reports, and none of them will ever learn OAuth 2.0: Email OAuth 2.0 Proxy learns it on their behalf. It listens on local IMAP, POP, and SMTP ports on your server, and when a client logs in the old-fashioned way with a username and password, the proxy swaps that exchange for a modern SASL XOAUTH2 token before the connection ever reaches the provider. The client never knows anything changed, so ancient mail apps, embedded devices, monitoring tools, and hand-rolled scripts keep sending and fetching mail through Outlook, Office 365, Gmail, Google Workspace, Fastmail, Yahoo, AOL, and any other provider that demands OAuth 2.0. The hop from your client to the proxy stays simple, while the proxy opens a fully encrypted TLS connection upstream, including STARTTLS negotiation for SMTP relays that require it. One proxy instance serves many accounts at once, with each mailbox mapped to its own local port and its tokens cached under a password you control. Optional plugins can even rewrite traffic in flight: strip Microsoft Defender Safe Links back to their real URLs, stop duplicate sent messages, or swallow test mail into a black hole. Setup is a single configuration file covering server ports, per-account scopes, and token endpoints, and the proxy then runs quietly as a headless service. 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.

Every email your app sends while you build and test it lands in OwlMail's browser inbox instead of a customer's mailbox. Point any application's SMTP settings at OwlMail and every message is ready to open as rendered HTML, plain text, headers, or raw source. Attachments and inline images sit beside the body, and seven preset preview widths show how the message lays out on phones, tablets, and desktops before anyone real sees it. A Verify panel checks subject, body, and link hosts against expectations, while CI pipelines use the REST API with delivery cursors to wait for exactly the messages their test run produced, assert on them, and clean up afterwards. Coding agents get the same inbox read-only over MCP, so an assistant can confirm a signup email arrived without touching your mail server. When a message proves itself, relay it onwards to a real SMTP server, by hand or automatically under filtering rules, or fire webhooks with HMAC signatures and retry queues into the rest of your automation. Everything stores as plain .eml files on disk, with optional SQLite indexing, S3 attachment storage, and ZIP exports for archiving. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Mailflow gathers every mailbox you own, the work account, the personal one, and the address stranded at a provider you left years ago, into one unified inbox hosted on your own server. All accounts merge into a single stream sorted by date, then sort themselves into Primary, Newsletters, Social, Notifications, and Other tabs, with a reclassify button for the ones that land wrong. Conversations group into threads, one click unsubscribes from detected newsletters, and full-text search reaches across every connected account at once. Writing mail gets a proper editor with formatting, tables, emoji, attachments, and smart address completion that learns from what you send, while inbox rules and a block list quietly move, archive, star, or trash messages by sender, subject, or content before you ever see them. New mail arrives with real-time toasts and push notifications, the interface installs as an app, speaks eleven languages, and can be reshaped with layouts, themes, and your own CSS. Accounts stay protected with two-factor authentication and single sign-on, contacts sync out over CardDAV, and an optional AI assistant can summarize a thread or draft the reply you are avoiding. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Marketing campaigns and transactional mail from one open-source platform: Notifuse is a modern, self-hosted alternative to Mailchimp, Brevo, and Klaviyo without per-email or per-contact pricing. Built with Go and React on PostgreSQL, it separates concerns cleanly: a drag-and-drop visual builder composes responsive templates from MJML components with Liquid variables like {{ contact.first_name }} and per-template version history; campaigns add A/B testing across subject lines, content, and send times; and a REST transactional API serves application-triggered mail. Delivery routes through your choice of provider - Amazon SES, Mailgun, Postmark, SendGrid, SparkPost, Mailjet, or plain SMTP - with multi-provider failover. Contacts carry custom fields and a full activity timeline (messages, profile changes, webhook events), and real-time segmentation builds dynamic rules over properties, activity, and subscriptions. Event-driven automations create behavioral sequences, a notification center gives recipients self-service preference management, and an S3-compatible file manager handles images with CDN delivery. Multi-tenant workspaces with isolated databases and custom domains suit agencies. Open and click tracking report engagement in real time.

Mox offers a complete mail server stack in a single Go binary requiring no external dependencies. The quickstart command configures a working mail server with SMTP, IMAP4, webmail, and full DNS authentication in under ten minutes. SMTP handling includes a delivery server on port 25, a submission server for authenticated clients, and a queue with automatic retries and DKIM signing. IMAP4rev2 implementation provides full mailbox synchronization with CONDSTORE and QRESYNC for efficient offline clients, NOTIFY for multi-mailbox monitoring, MULTISEARCH across mailboxes, and TLS client certificate authentication via the EXTERNAL SASL mechanism. The built-in webmail provides browser-based reading and composing with message threading, attachments, and HTML rendering without requiring a separate web client. Email authentication implements SPF validation, DKIM signing and verification with automatic key rotation, DMARC policy enforcement with aggregate and failure reporting, DANE with DNSSEC-protected TLSA records, and MTA-STS for certificate verification. Junk filtering combines reputation-based sender scoring with Bayesian content analysis trained per account. The web administration interface manages domains, accounts, DNS records, TLS certificates, delivery queue, and real-time log viewing. Internationalized email addresses with EAI and IDNA support handle non-ASCII domains and mailboxes. Account autoconfiguration publishes settings for Thunderbird autoconfig and Outlook autodiscover. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Stalwart replaces the traditional Postfix + Dovecot + SpamAssassin + calendar-server stack with one Rust binary that speaks every standard mail and collaboration protocol natively. JMAP, IMAP4rev2, POP3, SMTP, CalDAV, CardDAV, and WebDAV all run inside the same process — no glue scripts, no sidecar daemons, no version conflicts between components. The pluggable storage architecture lets operators choose RocksDB for single-node deployments, FoundationDB for distributed clusters, PostgreSQL, MySQL/MariaDB, or SQLite for the data store, S3/MinIO/Azure Blob for message blobs, and Elasticsearch or Meilisearch for full-text search, with Redis or the internal engine backing rate limiters and session state. Security features include S/MIME and OpenPGP encryption at rest, automated DKIM key generation with DNS publication, DANE and MTA-STS transport security, automatic ACME TLS provisioning, granular ACLs, rate limiting, and IP banning. The browser-based admin console manages accounts, domains, groups, mailing lists, SMTP queues, DMARC/TLS-RPT/ARF reports, and every configuration object without touching a config file, while the self-service portal at /account gives end users password reset and encryption key management. Multi-tenant support with per-tenant quotas enables hosting-platform deployments, and coordinator-less clustering via Zenoh or NATS scales horizontally by adding nodes. Deploy via Docker or the standalone binary. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL v3 licensed.

With over 7,100 GitHub stars and 200 contributors since 2016, Mailu has become one of the most popular self-hosted email solutions, delivering a complete production-ready mail server stack as pre-configured Docker containers that eliminate weeks of manual setup. The platform bundles Postfix for SMTP and Submission with auto-configuration profiles for Thunderbird, Outlook, and mobile clients, Dovecot for IMAP and POP3 with full-text search across email attachments, Rspamd for intelligent spam filtering with auto-learn Bayesian classification, greylisting, SPF and DMARC validation, and ClamAV for antivirus scanning of attachments with configurable malicious file blocking. The web administration interface provides global admin controls, per-domain delegation, user quota management, domain aliases, custom routing rules, and announcement capabilities. Users access self-service features including aliases, auto-reply, auto-forward, fetched accounts from external mailboxes via fetchmail, and Sieve filter management through ManageSieve. Security features include enforced TLS on all connections, automatic Let's Encrypt certificate provisioning, outgoing DKIM signing, DANE and MTA-STS support for transport security, and Snuffleupagus PHP hardening for the web interface. The setup wizard at setup.mailu.io generates complete Docker Compose configurations tailored to specific deployment requirements. All components are free and open-source software with zero proprietary dependencies and no tracking. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Your Gmail, Google Workspace, or Outlook inbox, worked by an AI assistant: Inbox Zero sits on top of the account you already have. Its core idea is rules written in plain English - tell the assistant "label invoices and file the PDF to Drive" or "archive cold outreach unless they mention my company" - and it executes against every incoming message. Emails that need a response arrive with a pre-drafted reply written in your tone, learned from your email history and calendar context. Reply Zero tracks what you owe responses to and what you're waiting on; the Bulk Unsubscriber surfaces newsletters you never read (with read-rate analytics) for one-click unsubscribe-and-archive; the Cold Email Blocker auto-archives unsolicited pitches based on your own definition of "cold." Smart Filing routes attachments - receipts, contracts, PDFs - into the right Google Drive or OneDrive folder, and Slack/Telegram integration lets you read, draft, and triage without opening a mail client. Email analytics show top senders and volume trends. It is not a new email client: everything happens in your real mailbox using native filters. Self-hosting means your mail content and the LLM calls that process it run on infrastructure you control.

DispatchMail is an SuperHuman alternative and delivers a self-hosted AI email assistant that processes your Gmail inbox through configurable OpenAI prompts without sending data to third-party cloud services beyond the LLM API itself. The Flask backend connects to Gmail via IMAP, retrieves new messages according to your schedule, and routes them through customizable whitelist rules based on sender address, subject keywords, or natural language descriptions before AI processing begins. Two distinct prompt configurations control behavior — the Reading Prompt instructs how the AI should analyze and classify incoming messages, while the Draft Prompt defines how responses should be composed, letting you maintain consistent tone and policy across all automated replies. Whitelist filtering ensures the AI only processes messages you explicitly authorize, preventing unnecessary API costs and keeping sensitive emails out of the LLM pipeline entirely. The React web interface provides inbox management with message previews, AI-generated summaries, draft editing with human-in-the-loop approval before sending, and configuration panels for prompts and rules. Automatic labeling and archival organize processed messages into categories without manual intervention. The sender research feature uses LLM-powered deep analysis to build background profiles of email contacts. All email content, credentials, and processing results persist in a local SQLite database with zero cloud storage dependencies. 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.

Webhooks, cron schedules, and app events trigger chains of nodes that fetch, transform, and route data: n8n is a workflow automation platform built around a visual, node-based editor. It ships with 400+ built-in integrations covering databases like Postgres, SaaS tools like Slack and HubSpot, and every major AI provider. When a pre-built node does not exist, the HTTP Request node calls any REST API, and the Code node runs JavaScript or Python inline, so you are never blocked by a missing connector. Workflows execute as directed graphs with branching, loops, error handling, and sub-workflows, and every run is logged for inspection and replay during debugging. It also includes LangChain-based nodes for building AI agents with tool calling and memory. Self-hosting on RepoCloud gives you unlimited workflow executions with no per-task pricing, and all data stays on your instance. Runs on Node.js with SQLite by default; add Postgres and Redis queue mode when you need to scale workers horizontally.