Your own mail server
Send through your own MTA on your own IPs. MailForge signs each message with a 2048-bit DKIM key generated per domain.
MailForge sends through your own mail server and switches to AWS SES, Postmark or any SMTP relay when a provider fails. One API, one dashboard, on your own server.
import { Mailforge } from "@mailforge/node";
const mailforge = new Mailforge(process.env.MAILFORGE_API_KEY, {
baseUrl: "https://mail.example.com"
});
const { data, error } = await mailforge.emails.send({
from: "Acme <orders@acme.com>",
to: "customer@example.com",
subject: "Order 94821 confirmed",
html: "<p>Thanks for your order.</p>"
});Most email APIs give you a single sending path. MailForge keeps an ordered chain of providers and works through it for every message.
What MailForge does today, without the marketing gloss.
Send through your own MTA on your own IPs. MailForge signs each message with a 2048-bit DKIM key generated per domain.
Add AWS SES, Postmark or any SMTP relay as a backup. When a provider fails, the next one in line takes the message.
Assign providers to transactional mail, marketing mail or both, so a campaign never touches the IPs your receipts depend on.
Give each service only what it needs, from emails:send to domains:write. Keys are stored as hashes and shown once.
Every accepted email is stored in PostgreSQL before the API answers. Idempotency keys stop double sends, failed deliveries are retried, and hard bounces are suppressed for you.
Your server is told when an email is sent, bounces or fails. Every request is signed, retried for hours if you are down, and visible in a delivery log.
Send now or up to 30 days ahead, and cancel until the last moment. One request takes up to 100 emails, all or nothing.
Keys starting with mf_test_ run the whole pipeline, webhooks included, without sending anything. Simulator addresses let you rehearse bounces.
Store an email once and send it by name with your data. Variables, defaults, if and each, with a live preview in the dashboard.
See opens, clicks and your most clicked links per domain and per email. Switch it off per domain, and exclude single links.
Typed clients with automatic retries and idempotency keys built in. The Node.js SDK renders React Email components for you.
Add a domain and get the exact DKIM, SPF and DMARC records to publish. One call verifies them against live DNS.
Resend is a hosted service: it runs the servers and you rent access. MailForge runs on your server, so the mail path, the data and the costs are yours to control.
| Resend | MailForge | |
|---|---|---|
| Where it runs | Hosted service | Your own server, in the region you choose |
| Sending infrastructure | Resend's infrastructure | Your own MTA and IPs, plus any provider you connect |
| When a provider fails | You depend on one platform | Mail moves to the next provider automatically |
| Where your email log lives | In Resend's cloud | In your own PostgreSQL database |
| API key permissions | Full access or sending access | Granular permissions per area, with wildcards such as emails:* |
| Cost model | Monthly plans by email volume | No per-email fee. You pay for your server and the providers you add. |
The honest part: running your own mail server means you look after it, including IP reputation. Resend also offers things MailForge does not have yet, such as attachments, broadcasts to audiences and SDK packages published on npm and PyPI. The docs list exactly what is available today.
Read the quickstart and send your first email in a few minutes.