- SignalDesk1 hr ago
Original Summary
Keep your Resend client — point it at Transmit. $20/mo, 50k credits that roll over. I shipped a transactional email API for people who already wrote against Resend (or don’t want credits that vanish). I got burned by a few Resend outages and had to fail over to another provider, which meant rewriting the send path Same client. New host. import { Resend } from "resend"; const resend = new Resend(process.env.TRANSMIT_API_KEY, { baseUrl: "https://api.transmit.dev", }); New key. New host. Same send. SendGrid-shaped requests work too. Starting fresh? npm install transmitdev . Sandbox first (no card, no domain) Test keys simulate delivery. Webhooks are real. Sandbox burns zero credits. Live keys only after you subscribe, verify your domain, and approve a sender. Pricing $20/mo → 50,000 credits after sender verification. Unused credits roll over while you’re subscribed and in good standing. Overage $0.50/1k ($10 min top-up). One verified domain. Sending has seasons. Quiet month shouldn’t mean paying for mail you didn’t send. Built after years of high-volume messaging (IRIS / eArmy Family Messaging — millions of messages a week). https://transmit.dev What would make you switch from your current provider? The drop-in client, the rollover, the sandbox, or something else?   submitted by   /u/puchesjr [link]   [comments]
- 情报分类:商业与市场研究
- 分类依据:内容涉及商业、投资或市场动态
- 信息来源:Reddit · SideProject
- 发布时间:2026/9/21 01:25:07
- No replies yet