Comparison

Veil Mail vs Resend

Veil Mail is a drop-in alternative to Resend with built-in PII protection, CASL compliance, and a broader feature set for teams that need more than transactional sending.

Side-by-side: sending an email

Resend

import { Resend } from 'resend'

const resend = new Resend('re_xxxxxxxxxxxxx')

await resend.emails.send({
  from: 'hello@yourdomain.com',
  to: 'user@example.com',
  subject: 'Welcome!',
  html: '<h1>Welcome</h1>',
})

Veil Mail

import { VeilMail } from '@resonia/veilmail-sdk'

const client = new VeilMail('veil_live_xxxxx')

await client.emails.send({
  from: 'hello@yourdomain.com',
  to: 'user@example.com',
  subject: 'Welcome!',
  html: '<h1>Welcome</h1>',
})

Feature comparison

What Veil Mail offers that Resenddoesn't

• Automatic PII protection. Every outgoing email is scanned for SSNs, credit cards, medical records, and other sensitive data via Google Cloud DLP before delivery — blocked or redacted based on your policy.
• CASL & GDPR compliance. Built-in consent tracking with expiry management, subscription topics for granular preferences, and compliant unsubscribe pages out of the box.
• A/B testing for campaigns. Test subject lines, content variants, and send times with statistical significance tracking.
• Automation sequences. Drip campaigns with branching logic, delay steps, and audience-join triggers.
• RSS-to-email feeds. Automatic digest or single-item sends when your RSS feed updates.
• Fine-grained API scoping. 19 distinct scopes versus Resend's 2, for tighter security boundaries across multi-service deployments.
• Game engine SDKs. Official Unity, Unreal Engine, and TouchDesigner SDKs — not offered by any other email provider.

Where Resend leads

We believe in honest comparisons. Resend currently has the edge in a few areas:

• — Natural-language scheduling. Resend accepts "in 2 hours" as a scheduled-for value; Veil Mail requires ISO 8601.
• — Visual template editor. Resend's slash-command editor is slicker than our current builder.
• — Inbound email. Resend's inbound parsing is more mature; ours is newer.

Frequently asked questions