Mailflare
Mailflare is a self-hosted, open-source email inbox for custom domains. It offers shared inboxes, multiple accounts, security, backups, and deployment on Cloudflare or Docker, keeping data on infrastructure you control.
Visit hieunc229/mailflareOverview
Mailflare is a self-hosted, open-source email inbox for custom domains. It runs in your own Cloudflare account or as a Docker container, combining inbound routing, sending, storage, and a modern web interface. It supports send and receive from custom domains, shared team accounts, security features, and data portability.
Key Features
- Send and receive from custom domains with attachments, rich formatting, signatures, drafts, folders, search, stars, and snoozing.
- Create mailboxes and aliases across domains, including shared inboxes for team addresses.
- Manage routing rules to store, forward, reject, or categorize incoming messages.
- Protect accounts with spam filtering and two-factor authentication using TOTP and recovery codes.
- Schedule mailbox backups and import or export mail for portability.
- Connect email apps via JMAP, integrate through API keys and webhooks, and use the built-in AI assistant or MCP access.
Use Cases
- Professionals and teams that want custom-domain email without recurring subscription fees.
- Teams managing shared addresses such as hello@ or support@ without sharing passwords.
- Developers and self-hosters who want email running on infrastructure they control.
- Applications and workflows that need to connect mail delivery through APIs and webhooks.
Getting Started
- Deploy the app to Cloudflare and keep the app name as mailflare.
- Open the deployed app and follow /setup to check the installation and create your admin account.
- Connect a domain managed by the same Cloudflare account; Mailflare configures its email routing and helps create the first mailbox.
- For Docker self-hosting, copy .env.docker.example to .env.docker and run docker compose up -d --build.
Deployment & Requirements
- Cloudflare deployment uses Workers, D1, R2, and Email Routing; the app running under the Worker name mailflare.
- A scoped Cloudflare API token named CF_TOKEN is required during deployment with permissions for Email Sending, DNS Settings, Email Routing Addresses, Email Routing Rules, and Zone Settings.
- A paid Cloudflare Workers plan is required to send email and is recommended for a smooth experience.
- Docker self-hosting runs as one container with SQLite, local file storage, a built-in SMTP listener for inbound mail, and any SMTP relay or Cloudflare Email Sending for outbound.
Before You Adopt
- License: AGPL-3.0. Review its terms before using, modifying, or distributing the project.
- The Cloudflare Worker deployment must keep the app name mailflare.
- Cloudflare hosting is optional; Docker is supported as an alternative deployment.
- Data location depends on the chosen deployment and remains under the operator's control.
- Cloudflare usage may incur separate charges, although many personal installations fit within free allowances.