The European alternative to Resend

Where your data lives

Customer data is stored in the European Union. Our infrastructure runs in European data centres, in the French OVHcloud group.

Resend documents the other arrangement plainly: “All account data, including email metadata, logs, and API records, is stored in the United States regardless of the sending region you select.” Choosing its Ireland region moves the sending, and the records stay where they were.

The detail is in the data processing agreement.

What you pay

Both platforms price by monthly volume. The table takes seven volumes. Each row shows the cheapest plan on each side, in your region’s currency.

Dedicated IPs are included from the Elite plan. Elite carries one at 100,000 emails a month, and Volume carries six at 750,000. Each new one warms on a six-stage ladder, from 50 messages a day to 10,000. Resend sells a dedicated IP for $30 a month. The add-on is limited to its Scale plan and to senders above 3,000 emails a day.

Feature by feature

The rows below hold what each platform documents today. A docs link opens the mailkube page behind that row.

Two transports, headers included

POST to the REST API, or point the SMTP client you already run at smtp.mailkube.com. Everything the API takes as a JSON field, SMTP takes as a header. Those headers are stripped before the message reaches the recipient.

• X-Mailkube-Tags carries the same tag list as the REST tags field
• X-Mailkube-Topic attributes the send to a topic, so recipients who opted out are filtered
• X-Mailkube-Template-Id and X-Mailkube-Template-Version render a saved template server-side

An SMTP send is the same message as an API send. It lands in the same logs, counts against the same quota and fires the same webhook events. The SMTP reference(opens in a new tab) lists every header, reply code and rate limit.

Resend relays SMTP as well, on smtp.resend.com, and accepts custom headers on a message. Its documentation describes no header for a template, a tag or a topic.

Your stack, already covered

Official SDKs cover Node, Python, Go, Java, PHP and Ruby. Django, Laravel, Rails and Spring Boot each get a package of their own. It plugs into the framework’s own mail layer. Every client verifies your webhook signatures for you.

Resend ships nine official clients. Rust and .NET join the same six languages, alongside a Laravel package.

The CLI is one binary. It sends over either transport and manages scheduled sends. While you develop, it runs a local webhook receiver. It ships a skill file, so a coding assistant reads the real command surface. Start from the SDK documentation(opens in a new tab) or the CLI guide(opens in a new tab) .

Migrating from Resend

Install the client for your language, then swap the constructor and the key. The send call keeps its shape.

import { Resend } from "resend";

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

const { data, error } = await resend.emails.send({
  from: "Acme <hello@example.com>",
  to: ["customer@example.com"],
  subject: "Hello world",
  html: "<p>It works!</p>",
});

import { Mailkube } from "@mailkube/mailkube-node";

const client = new Mailkube({ apiKey: process.env.MAILKUBE_API_KEY });

const email = await client.emails.send({
  from: "Acme <hello@example.com>",
  to: "customer@example.com",
  subject: "Hello world",
  html: "<p>It works!</p>",
});

Migration is frictionless over SMTP as well. Change the host, the port and the credential in your mailer, and keep everything else as it is. The messages you already send go out unchanged, and tags, topics and templates ride along as headers when you want them. Nothing has to move on a set day: run both platforms side by side and switch one service at a time. The quickstart(opens in a new tab) covers the REST path and the SMTP guide(opens in a new tab) covers the relay.

When Resend is the better fit

Resend’s marketing product carries contacts, audiences and broadcasts. mailkube sends your application’s mail and tells you what happened to it. Audience building lives in your own database, and a topic on each send honours the opt-outs.

Its clients cover Rust and .NET. A message there carries up to 75 tags, against 20 here.

The pricing page has every plan in full. The REST API and SMTP relay pages go deeper on the two transports.