How We Send Emails For Free: Harnessing Resend and Cloudflare SMTP Proxies

Transactional emails—such as calendar booking confirmations, incoming lead alerts, and contact form submissions—are critical for local business operations. Yet legacy SMTP providers like SendGrid or Mailgun charge $15 to $35/month for basic transactional access. Here is a clean engineering blueprint to send authenticated, high-deliverability outbound emails for $0.00/month.

1. Outbound Messaging: Resend Free Tier Integration

For outbound notifications, we integrate the Resend API:

• Free Tier Allocation: Resend provides 3,000 emails per month (100 emails/day) for custom domains.
• DNS Authentication Alignment: Enforcing strict SPF, DKIM, and DMARC alignments on Cloudflare DNS guarantees 100% inbox placement and protects your domain reputation.

Without strict DNS alignment, automated server emails are frequently flagged as spam or rejected outright by corporate spam filters. Proper DKIM key signing verifies that outbound emails originate from your verified server domain.

2. Inbound Routing: Cloudflare Email Workers

Instead of paying $6/user/month for Google Workspace inboxes or Microsoft 365 seats, we deploy Cloudflare Email Routing:

• Inbound emails sent to hello@protoss.ca or admin@yourdomain.com are forwarded to a private personal email inbox in under 50 milliseconds.
• Zero server management, zero monthly fees, and 100% professional credibility.

========================================================================================================
                         DECOUPLED TRANSACTIONAL EMAIL FLOW
========================================================================================================

 [ INBOUND EMAIL ] ──► [ CLOUDFLARE EMAIL ROUTING ] ──► [ PERSONAL INBOX ] ($0.00/mo)

 [ FORM SUBMISSION ] ──► [ NEXT.JS API ROUTE ] ──► [ RESEND API (3,000/MO FREE) ] ──► [ CLIENT EMAIL ]
========================================================================================================

3. Production Resend Dispatch Handler Code

Here is the complete TypeScript API route used to dispatch lead alerts in Next.js:

import { Resend } from 'resend';
import { NextResponse } from 'next/server';

const resend = new Resend(process.env.RESEND_API_KEY);

export async function POST(req: Request) {
  try {
    const { name, email, message, phone } = await req.json();

    if (!email || !name) {
      return NextResponse.json({ error: 'Missing required fields' }, { status: 400 });
    }

    const data = await resend.emails.send({
      from: 'Protoss System <system@protoss.ca>',
      to: ['jared@protoss.ca'],
      subject: `⚡ New Technical Inquiry: ${name}`,
      html: `
        <div style="font-family: sans-serif; padding: 20px; background: #f9f9f9;">
          <h2 style="color: #0c0a09;">New Technical Lead Submission</h2>
          <p><strong>Name:</strong> ${name}</p>
          <p><strong>Email:</strong> ${email}</p>
          <p><strong>Phone:</strong> ${phone || 'Not provided'}</p>
          <p><strong>Message:</strong></p>
          <blockquote style="background: #fff; padding: 15px; border-left: 4px solid #0078d4;">
            ${message}
          </blockquote>
        </div>
      `
    });

    return NextResponse.json({ success: true, id: data.id });
  } catch (error: any) {
    return NextResponse.json({ error: error.message }, { status: 500 });
  }
}

4. Operational Cost Matrix

5. Step-by-Step Setup Guide

1. Add SPF Record: Create a TXT record on Cloudflare (v=spf1 include:amazonses.com ~all).
2. Add DKIM Records: Add the 3 CNAME records generated by Resend into Cloudflare DNS.
3. Configure Cloudflare Email Routing: Enable Email Routing in Cloudflare dashboard and map inbound aliases to your primary inbox.
4. Secure API Keys: Inject RESEND_API_KEY via environment variables in your serverless deployment.
5. Implement Rate Limiting: Add IP-based rate limiting on /api/contact using local memory tokens to prevent spam submission attacks.