Compare
Notify vs SMTP / Nodemailer
SMTP is fine plumbing. For app email, an HTTPS API is usually simpler to deploy — no open ports, less credential sprawl, easier observability. Notify replaces the transport with one POST.
| Feature | Notify | SMTP / Nodemailer |
|---|---|---|
| Focus | Minimal transactional API: send, webhooks, logs | DIY transport (SMTP) + libraries like Nodemailer |
| Recommended client | One `fetch` — no mail library required | `nodemailer.createTransport` + `transporter.sendMail` |
| Protocol | HTTPS JSON | SMTP (often 587/465) to a relay you configure |
| Auth | `x-api-key` header | SMTP user/pass (or provider-specific SMTP creds) |
| Send body | `to`, `subject`, `message` | `html` / `text` on `sendMail` (or raw MIME) |
| Ops burden | Domain verify + API key; logs and webhooks built in | You assemble retries, reputation, logs, bounce handling |
| Entry paid pricing | Pro: $10/mo for 10,000 emails | Relay/VPS/IP costs + your engineering time |
Choose Notify if…
You want one HTTPS send call with logs and webhooks instead of owning SMTP ops.
Choose SMTP / Nodemailer if…
You already run dedicated mail infra and need full transport-level control.
Best for
Indie hackers and startups who want transactional mail without babysitting relays.
Not for
Teams that must stay on raw SMTP for compliance or existing MTA investments.
Transport vs send API
See the SMTP / Nodemailer migrate guide, why SMTP is no longer the default, and pricing.
Frequently asked questions
Is SMTP “cheaper”?
Raw SMTP can look cheaper on paper. You still pay in ops: credentials, ports, IP reputation, bounce handling, and observability. Notify prices the managed layer flatly.
Can I migrate from Nodemailer?
Yes. Replace transporter.sendMail with a small fetch wrapper to Notify, verify your domain, and use logs/webhooks instead of scraping SMTP transcripts.
Who should pick Notify?
App teams that want password resets, receipts, and notifications over HTTPS without running their own mail pipeline.