NextMail
Self-hosted · Multi-tenant · Open architecture

Email infrastructure
that doesn't lock you in.

Transactional API, SMTP relay, admin UI, and developer portal in one self-hostable codebase. Route through Resend, Postmark, or SES per tenant — keep your data, templates, and analytics on your own infrastructure.

No credit card. Free up to 3,000 emails/month on the shared instance.

send.ts
import { NextMail } from '@cybersquad/nextmail';

const mail = new NextMail({
  apiKey: process.env.NEXTMAIL_KEY,
});

await mail.send({
  from: 'noreply@headmanlaw.com',
  to: 'client@example.com',
  template: 'niw-eligibility-result',
  data: { name: 'Mr. Khan', verdict: 'qualified' },
});
98%
Inbox rate via providers
4
Send-adapter backends
1
Codebase to deploy

Everything email — under your control

One codebase. Multi-tenant from day one. Deploy as a shared instance or per-client container.

Transactional API

POST /v1/emails with JSON. TypeScript SDK, scoped API keys, sandbox mode. Idiomatic in any backend.

SMTP relay on port 587

Point any legacy app, WordPress plugin, or CI tool at smtp.yourdomain. API key is the password.

Multi-provider routing

Resend, Postmark, AWS SES, or any SMTP target — chosen per tenant per domain. Switch without code changes.

Normalized webhooks

Every provider event — delivered, bounced, opened, clicked — comes back in one shape. HMAC-signed.

Versioned templates

MJML source compiled to HTML + plaintext. Pin a version per send, edit safely, preview before deploy.

Automatic suppression

Bounces and complaints add the address to a tenant-wide list. Never send to it again — across every project.

From zero to first send in three steps

Designed so a non-technical client admin can onboard a domain in fifteen minutes, and a developer can integrate in ten.

01

Add a sending domain

Paste three DNS records into your registrar. NextMail verifies SPF, DKIM, and DMARC in real time. No CLI, no waiting.

02

Issue an API key

Scoped to emails:send or full admin. Shown once, hashed at rest. Use it in the SDK, REST API, or as your SMTP password.

03

Send and forget

NextMail picks the right provider for the domain, handles retries, captures events, fans webhooks to your app. You write product code.

Bring your own backend — switch providers per tenant without code changes.

Resend
Postmark
AWS SES
Mailgun
Self-hosted SMTP
The honest version

No email service can promise zero spam folder.

Not Gmail. Not Postmark. Not us. Inbox placement depends on DNS hygiene, IP reputation, recipient engagement, and provider trust — 80% infrastructure, 20% code.

What NextMail does: stack the deck. Provider routing borrows day-one reputation, automatic suppression keeps your sender score clean, SPF / DKIM / DMARC is verified per domain, and bounce / complaint feedback fans into your app in real time.

Realistic inbox rates

Via Postmark / Resend95-98%
Via SES with warmed IP92-96%
Self-hosted SMTP, cold IP60-75%
Self-hosted SMTP, mature80-90%

First four weeks of any new IP — provider or self-hosted — assume lower numbers while reputation builds.

Ready to own your email infrastructure?

Spin up a tenant in two minutes. Add a sending domain. Send the first email before the coffee cools.