Self-Hosted Postfix vs an Email API: The Real Cost in 2026
Self-Hosted Postfix vs an Email API: The Real Cost in 2026
Every few months a developer rediscovers that email is "just SMTP" and spins up Postfix on a $20 VPS. Six weeks later they're filing Spamhaus delisting requests at 2 AM. Here's the honest cost math — including the part that never shows up on any invoice.
The invoice lie: what you actually pay
| Cost | Self-hosted Postfix | Email API (MailAnvil) |
|---|---|---|
| Server / subscription | $20–40/mo VPS | Rp599k flat per 100k emails (~$40) |
| Setup | 10–20 hours one-time | ~15 minutes (API key + DNS) |
| Ongoing ops | 2–10 hours/month | ~0 |
| IP reputation | Yours, from zero | Pre-warmed shared pools |
| Bounce/complaint handling | You build it | Webhooks, managed suppression |
| One blacklisting incident | 4–8 hours + weeks of re-warm-up | Provider's problem |
Cash-wise, self-hosting wins on paper. The hidden line is operator time: patching, blocklist monitoring, feedback-loop review, DKIM rotation, log triage. At even a $50/hour blended developer rate, 3–6 hours/month is $150–300/month — more than the API bill it "replaces".
Three walls between you and the inbox
1. Port 25 is blocked by default. AWS EC2, DigitalOcean, Linode, Hetzner and Vultr all block outbound port 25 on new instances; Google Cloud blocks it indefinitely with no removal path. Every provider requires a written request to unblock, and some never approve.
2. Your IP is cold. Gmail, Microsoft and Yahoo greylist or reject unknown IPs. A fresh VPS IP with perfect SPF, DKIM, DMARC, PTR and TLS still lands 30–60% of mail in spam for the first 4–6 weeks while you ramp volume slowly. One overeager 50,000-send day on a stale list can torch the IP permanently.
3. The 2024+ sender requirements are your job now. Gmail and Yahoo's bulk-sender rules — SPF, DKIM, DMARC, RFC 8058 one-click List-Unsubscribe, valid PTR, TLS, spam complaint rate under 0.3% — are non-negotiable. An email API ships these as defaults. On Postfix, each one is a configuration project: OpenDKIM, OpenDMARC, a suppression database, FBL signups per provider.
What an email API actually charges for
The premium isn't a mystery. Compare effective per-thousand rates on entry plans (October 2026 list prices): Amazon SES is $0.16/1,000 on the new Essentials plan, SendGrid's $19.95 Essentials works out to ~$0.40/1,000, Resend $20 for 50k, Mailgun and Postmark ~$1.50/1,000 on entry tiers. You're paying for the management layer: template rendering, open/click tracking, bounce dashboards, suppression lists, support when deliverability dips.
The value of that layer depends entirely on who you are:
- Side project under ~200 emails/day to known recipients — direct SMTP from your VPS is fine. That's operational mail, not product mail.
- Product sending password resets, OTP codes, receipts — deliverability is the business. A 550 in the critical path costs more than months of API fees.
- Indonesian startup — add friction the tables above skip: USD billing, credit cards, exchange-rate swings. MailAnvil prices in IDR (Rp599k flat per 100k emails), takes QRIS/GoPay, and documents everything in Bahasa Indonesia.
The narrow cases where Postfix still wins
Self-hosting defends itself in exactly three scenarios: (1) an existing server with years of warm IP reputation sending low-volume notification mail — migrating it buys nothing; (2) data-residency constraints that cloud providers can't meet; (3) research setups where operator time is free. "I want to save money" is not on the list — the labor math says otherwise at any commercial volume.
The 5-minute test
Before committing to either path, send one real email through MailAnvil's free tier (500 emails/month, no credit card) and one through your VPS, then check placement with Gmail Postmaster Tools. The API mail arrives immediately. The VPS mail is a six-week project. That comparison — measured in hours, not dollars — is the real price tag.