# Free custom domain email: Cloudflare Email Routing + your favorite inbox + Brevo or Resend

Ben Morin, 2026-08-05. https://bemorin.com/writing/free-custom-domain-email-cloudflare-routing-brevo-resend

> Yes, you can run a pro email setup on your domain without paying for full mailbox seats. This guide shows the clean architecture: Cloudflare routing for inbound aliases, any UI client you prefer, and Brevo or Resend for reliable outbound sending.

<h2>1) What this setup solves</h2>
<ul>
  <li>you own <code>hello@yourdomain.com</code> style addresses</li>
  <li>you avoid expensive per-user mailbox plans at the beginning</li>
  <li>you keep deliverability options open as you scale</li>
</ul>

<h2>2) Architecture in one line</h2>
<p>
  <strong>Inbound:</strong> Cloudflare Email Routing -> destination inbox of your choice.
  <strong>Outbound:</strong> Brevo or Resend using your domain authentication records.
</p>

<h2>3) Buy domain first, then configure DNS</h2>
<p>
  Register your domain and add it to Cloudflare DNS. Keep nameservers stable before touching email so you avoid partial propagation issues.
</p>

<h2>4) Configure Cloudflare Email Routing</h2>
<ol>
  <li>Enable Email Routing in your domain dashboard.</li>
  <li>Create aliases like <code>hello@</code>, <code>support@</code>, <code>billing@</code>.</li>
  <li>Set destination inbox addresses (Gmail, Outlook, Fastmail, etc.).</li>
  <li>Verify forwarding destinations when prompted.</li>
</ol>

<h2>5) Pick your preferred interface</h2>
<p>Cloudflare handles routing, not mailbox UI. Use the interface you like most:</p>
<ul>
  <li>Gmail for team familiarity</li>
  <li>Outlook for Microsoft stack</li>
  <li>Fastmail or Proton for privacy-oriented workflows</li>
</ul>

<h2>6) Send emails with Brevo or Resend</h2>
<p>
  For transactional or campaign sending, add your domain to Brevo or Resend and configure SPF, DKIM, and return-path as requested by provider docs.
</p>
<ul>
  <li><strong>Brevo:</strong> useful for mixed marketing + transactional workflows.</li>
  <li><strong>Resend:</strong> excellent developer-first API for app-triggered emails.</li>
</ul>

<h2>7) Minimum DNS records to get right</h2>
<ul>
  <li><code>MX</code> for inbound routing target</li>
  <li><code>TXT SPF</code> authorizing your sender service</li>
  <li><code>DKIM CNAME/TXT</code> from Brevo or Resend</li>
  <li><code>DMARC TXT</code> to define spoofing policy</li>
</ul>

<h2>8) Recommended starter setup</h2>
<ul>
  <li>Aliases via Cloudflare: <code>hello@</code>, <code>contact@</code>, <code>support@</code></li>
  <li>One shared inbox destination at first</li>
  <li>Resend for app emails, Brevo for newsletter if needed</li>
  <li>DMARC in monitoring mode first, then tighten policy</li>
</ul>

<h2>Final takeaway</h2>
<p>
  This stack gives you brand-level email identity with near-zero recurring cost at launch. The key is to separate inbound routing from outbound
  delivery and lock down authentication records from day one.
</p>