An Amazon SES alternative, without building the rest.

What each one ships.

Moving from Amazon SES.

1. 01

   Add your domain and publish the DKIM and SPF records Samva generates next to the old provider's. Both can send while you switch.

2. 02

   Swap the send call.

   import { SESv2Client, SendEmailCommand } from "@aws-sdk/client-sesv2";
   
   const client = new SESv2Client({ region: "us-east-1" });
   await client.send(new SendEmailCommand({
     FromEmailAddress: "receipts@example.com",
     Destination: { ToAddresses: ["ada@example.com"] },
     Content: { Simple: {
       Subject: { Data: "Your receipt" },
       Body: { Html: { Data: "<p>Thanks for your order.</p>" } },
     } },
   }));
   

   await samva.messages.send({
     from: { email: "orders@example.com" },
     to: [{ email: "ada@example.com" }],
     channel: "email",
     email: {
       subject: "Your receipt",
       html: "<p>Thanks for your order.</p>",
     },
   });

3. 03

   Map webhooks. Samva sends signed events for sent, delivered, bounced, complained, failed, and received, with received going to the endpoint your domain's receiving route names. Opens and clicks arrive as message.opened and message.clicked, and unsubscribes as contact.unsubscribed.

   Amazon SES event	Samva event
   Send	message.sent
   Delivery	message.delivered
   Bounce	message.bounced
   Complaint	message.complained
   Open	message.opened
   Click	message.clicked
   Subscription	contact.unsubscribed and contact.resubscribed

4. 04

   Recreate templates as versioned templates, or send your existing HTML inline while you move.

5. 05

   Keep the old provider's suppression list in your app and filter against it. Samva cannot import it.

6. 06

   Turn on receiving if you want replies back.

What does not move: templates, the suppression list, and message history.

The full walkthrough: Replace an Amazon SES email stack without rebuilding delivery.