Deploy EmailFlare
EmailFlare is a self-hosted email sending platform built around Cloudflare
EmailFlare
Just deployed
/data
Deploy and Host EmailFlare on Railway
EmailFlare is an open-source, self-hosted email sending platform built on the Cloudflare Email Sending API. It ships an admin UI for managing domains, API keys, templates, and send logs — packaged as a single Docker container with embedded SQLite storage.
About Hosting EmailFlare
EmailFlare is built for minimum infrastructure. A single container bundles the Hono API backend, React admin UI, and embedded SQLite storage via mesahub-core. There are no external databases or message queues to provision. The Railway template pre-configures everything — generated secrets, embedded storage, and a persistent /data volume. All you need to bring are your Cloudflare credentials.
Common Use Cases
- Transactional email for SaaS apps — Send password resets, magic links, order confirmations, and notifications via a simple REST API
- Multi-domain email platform — Manage multiple Cloudflare sending domains and scoped API keys from a single admin dashboard
- Team email infrastructure — Issue per-team or per-service API keys with domain-level scoping; inspect every send in the logs UI
Dependencies for EmailFlare Hosting
- Cloudflare account with Email Sending enabled
- Cloudflare API token scoped to Email Routing (Edit) + Email Sending (Edit)
> Everything else — secrets, storage, volume — is handled by the Railway template automatically.
Deployment Dependencies
- Cloudflare Email Sending — outbound email delivery provider
- EmailFlare Cloudflare token guide — step-by-step token creation with required permissions
- mesahub-core — embedded SQLite storage engine
Implementation Details
The Railway template pre-sets ADMIN_TOKEN, SESSION_SECRET, and MESAHUB_URL with secure generated values and configures a persistent volume at /data. You only need to supply two variables:
CF_API_TOKEN=
CF_ACCOUNT_ID=
Testing without Cloudflare credentials: Create a test API key in the admin UI. Test keys route sends through SMTP (SMTP_HOST / SMTP_PORT) instead of Cloudflare — point them at any SMTP catcher such as Mailpit for safe staging tests.
Why Deploy EmailFlare on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying EmailFlare on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
EmailFlare
ghcr.io/0xdps/emailflare:latestCF_API_TOKEN
Required for production email sending via the Cloudflare Email Sending API. Guide: https://emailflare.dev/cloudflare-token
CF_ACCOUNT_ID
Your Cloudflare account ID — found in the Cloudflare dashboard sidebar.