Resend alternatives, and when to stay.

The short answer: Resend is an excellent developer-first email API, and many teams should stay on it. Teams look elsewhere when marketing and lifecycle email enter the picture, because Resend prices marketing on contacts, separately from sends. Linnet is for developers who want transactional, lifecycle and broadcast email in one place, with a Resend-compatible API and no contact-count fee. It is early access and email only.

Who Resend is best for

Developers who want a clean transactional email API with a modern developer experience and React Email. If transactional is all you send, Resend is a good home.

Why some teams consider switching

• Two meters. Transactional email is priced on sends; marketing email is priced on contacts, with plans that start at 1,000 contacts and rise with the list.
• Marketing is a separate job. Journeys started by product events and broadcasts to a cohort have to be built and operated.
• You want one consent model and one log for receipts, onboarding and announcements.

First-hand: Linnet's founder replaced Resend in their own products. The API is Resend-compatible, so moving is a change of base URL and key rather than a rewrite. We make no claim about cost, speed or deliverability from that move.

How the pricing models differ

What switching looks like in code

From the SaaS page and docs: the API accepts Resend-style requests, so the move is two settings.

# .env
RESEND_API_KEY=lnt_live_…
RESEND_BASE_URL=https://app.linnet.run

# Your code, unchanged
await resend.emails.send({ from: "billing@northstar.app", to: user.email, subject: "Your receipt", html });

Same request and response shapes; batch and cancel work the same way. Test in a test project before you switch production traffic.

A shortlist, honestly

We make Linnet, so we list ourselves first and say plainly where we are the wrong choice. Descriptions of other tools come from each vendor's own site on 2026-11-07; check them before you decide.

When Linnet is a good replacement

• You send transactional email and want onboarding journeys and broadcasts in the same place.
• You want your product events to start journeys without a second system.
• You want your own AI agent, such as Claude or Codex, to work with email through MCP, with approval kept in your hands.
• Your contact list is large and the marketing contact bill is the pain.

When Linnet is not a suitable replacement

• You only send transactional email and you are happy. Staying is cheaper than moving.
• You depend on an SDK or feature we have not matched. Tell us which, before you move.
• You need SMS or WhatsApp now. Linnet does not offer them yet.
• You need a published self-serve price and a service-level agreement today. Linnet is in early access.

What moving involves

1. Create a project and verify your sending domain. The quickstart walks through it.
2. Change your API key and base URL in a test project and send a test.
3. Export your Resend contacts and bring them over with consent attached; we can do this with you.
4. Rebuild the journeys you use. Switch production traffic when you are happy.

Full scope and procedure are on the free migration page.

Questions

Sources, read 2026-11-07: Resend pricing; Loops; Postmark; Amazon SES. Linnet is not affiliated with any of these companies.