1) What this setup solves

  • you own hello@yourdomain.com style addresses
  • you avoid expensive per-user mailbox plans at the beginning
  • you keep deliverability options open as you scale

2) Architecture in one line

Inbound: Cloudflare Email Routing -> destination inbox of your choice. Outbound: Brevo or Resend using your domain authentication records.

3) Buy domain first, then configure DNS

Register your domain and add it to Cloudflare DNS. Keep nameservers stable before touching email so you avoid partial propagation issues.

4) Configure Cloudflare Email Routing

  1. Enable Email Routing in your domain dashboard.
  2. Create aliases like hello@, support@, billing@.
  3. Set destination inbox addresses (Gmail, Outlook, Fastmail, etc.).
  4. Verify forwarding destinations when prompted.

5) Pick your preferred interface

Cloudflare handles routing, not mailbox UI. Use the interface you like most:

  • Gmail for team familiarity
  • Outlook for Microsoft stack
  • Fastmail or Proton for privacy-oriented workflows

6) Send emails with Brevo or Resend

For transactional or campaign sending, add your domain to Brevo or Resend and configure SPF, DKIM, and return-path as requested by provider docs.

  • Brevo: useful for mixed marketing + transactional workflows.
  • Resend: excellent developer-first API for app-triggered emails.

7) Minimum DNS records to get right

  • MX for inbound routing target
  • TXT SPF authorizing your sender service
  • DKIM CNAME/TXT from Brevo or Resend
  • DMARC TXT to define spoofing policy

8) Recommended starter setup

  • Aliases via Cloudflare: hello@, contact@, support@
  • One shared inbox destination at first
  • Resend for app emails, Brevo for newsletter if needed
  • DMARC in monitoring mode first, then tighten policy

Final takeaway

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.