Does Notify replace raw SMTP providers for transactional email?

Yes. For modern SaaS and serverless apps, Notify is intended to replace raw SMTP as the way you send transactional email from your application. You don’t run or configure SMTP in your app; you call Notify’s HTTPS API and let it handle delivery, retries, and logging. notify

How Notify fits in the stack

• App → Notify: Your backend sends an HTTPS POST with the email payload and API key. No SMTP ports, no connection pooling, no SMTP libraries needed. notify
• Notify → inbox providers: Notify (like Resend, SES, Postmark, etc.) still uses SMTP under the hood to talk to Gmail, Outlook, and other mail servers, but that’s abstracted away from you. notify
• Observability: Delivery status, bounces, and (on paid plans) webhooks are provided by Notify, so you don’t need to parse SMTP responses or DSNs yourself. notify

When you might still use SMTP

• Legacy tools that only support SMTP (older CMS, frameworks, or on-prem systems). notify
• Deliberate relay setups where you choose a provider’s SMTP relay instead of their API. notify Even then, the recommendation is to prefer a provider’s SMTP relay over running raw SMTP on your own VPS, so reputation and bounces are handled professionally. notify

Practical takeaway

If your goal is “stop managing SMTP and just send reliable transactional email from code,” Notify is designed exactly for that: an HTTP-only transactional API with logs and webhooks, replacing the need to configure and maintain SMTP in your application. notify