Temporary email on your own domains, with expiring mailboxes, webhooks and an API, running on Cloudflare Pages, D1 and Email Workers
- Deploy
- CLI
- License
- MIT
- GitHub stars
- 2.8k stars
- Last commit
Self-hosted alternatives to Mailinator
Mailinator offers public disposable inboxes and, on paid plans, private domains, an API and webhooks for teams that test email and SMS flows. One listed app does its main job and runs in your own Cloudflare account.
Each answer comes from the app’s README and source code, compared with the features Mailinator describes on its own site.
Mailinator features, app by app
| Feature | MoeMail |
|---|---|
| Public disposable inboxes for any address | Partly |
| Private testing domains | Yes |
| API and webhooks | Yes |
| SMS testing | No |
| Rules that act on incoming mail | No |
| Use from test frameworks such as Playwright and Cypress | Partly |
Temporary email on your own domains, with expiring mailboxes, webhooks and an API, running on Cloudflare Pages, D1 and Email Workers
- What a Mailinator user would miss
- Mail to addresses that were not created is dropped, and there is no SMS testing or rule engine.
- What it adds
- MIT and runs in your own Cloudflare account on your own domains, with roles for several users, webhooks and share links for mailboxes and messages.
- Partly Public disposable inboxes for any address. Only addresses created in MoeMail receive mail; messages to other addresses are dropped. The API creates addresses on demand.
- Yes Private testing domains. Runs on your own domains.
- Yes API and webhooks. OpenAPI with API keys, and a webhook that posts each new message.
- No SMS testing. Email only.
- No Rules that act on incoming mail. No rules; a webhook can hand messages to another tool.
- Partly Use from test frameworks such as Playwright and Cypress. Tests can call the API or the CLI, which can wait for a message and read it; there are no framework plugins.
Sources:github.com/beilunyang/moemail#readmedocs.moemail.app/www.mailinator.com/