maillab/cloud-mail

Cloud Mail is a self-hosted, multi-user email platform meant to be deployed on Cloudflare. Its main promise is turning one domain into many mailboxes without running a traditional mail server. It fits people who already control a domain and are comfortable configuring Cloudflare resources; the README does not document a non-Cloudflare path.

What you get

The user-facing side is a responsive webmail, with automatic layout adaptation to PC and most mobile browsers, that sends and receives mail and keeps attachments in R2 object storage README: features. Administrators get user and mail management with RBAC-style permissions to limit functions and resources, plus ECharts dashboards for system details and mail growth. Sending can use Cloudflare Email or Resend, including bulk sending; incoming mail can be forwarded to a Telegram bot or another provider's mailbox. A public API supports batch user creation and filtered mail queries, and Workers AI optionally recognizes verification codes in received mail README: features.

A representative setup: put your domain on Cloudflare, deploy the Worker backend and the Vue frontend, bind Workers KV, D1 and R2, configure email routing/handling and a sending path, then create users and mailboxes through the admin or API README: tech stack. Turnstile is available to block automated signups. Deployment steps and the demo are linked from the project docs rather than reproduced here deployment docs, online demo.

How it works

The worker backend uses Hono, Drizzle for the data layer, KV for caching and D1 for the database; the frontend is Vue 3 with Element Plus README: tech stack. Because storage, database, cache and compute are all Cloudflare services, the practical cost and dependency profile is shaped by those services rather than by managing servers — the README's stated rationale is lower server cost project overview. The trade-off is lock-in: the documented architecture assumes Workers, D1, R2 and KV, and there is no described alternative backend.

Requirements and constraints

You need a domain and a Cloudflare account with the relevant services enabled. Cloudflare Email is one sending option; Resend is documented as an alternative, so the sending path is not limited to a single provider. Verification-code recognition needs Workers AI, and Turnstile is needed only if you want the anti-bot check. Attachment handling depends on R2. The README offers no benchmark, capacity figures or compatibility matrix, and lists further features as still in development README: features.

The project is MIT-licensed, so modification and reuse are permitted under that licence MIT licence. Release history is listed separately releases.

HotRepo's take

The repository was recorded on the GitHub daily trending board once, on 2026-10-31, at 15,174 stars with +60 that day; the verified sample is too short to infer momentum repository. Judge fit by whether a Cloudflare-only mail stack matches your domain and operational preferences.