Add SMTPedia as a preferred source on Google
Marketing platforms
Pricing reviews, feature comparisons, and category roundups for email marketing tools. From Mailchimp to Amazon SES, from cold email to transactional. We test with real accounts, we call out what fails.
Choosing an email platform is a five-year commitment disguised as a monthly bill. The wrong pick means migration cost, template rebuilds, deliverability rebuilds, and integration rework, usually right when you can least afford it. The right pick is the one that fits your actual sending pattern, not the one with the loudest marketing.
This hub covers the market from four angles: pricing reviews for the platforms most people are actually comparing, category roundups for verticalized needs (cold email, transactional, high-volume, SES-based), feature comparisons that go deeper than the marketing pages, and honest reviews that call out what breaks under load.
Editorial independence is not a slogan here. Some articles carry affiliate links; those partnerships do not change how platforms are categorized, described, or scored. Free-tier limits and weaknesses get documented the same way regardless of business relationship.
Pricing reviews
Cost per email, per contact, per feature: what platforms actually charge at 10k, 100k, 1M subscribers.
Read guides →Cold email tools
Outbound at scale: warmup, deliverability control, multi-inbox rotation, cost per lead.
Read guides →Transactional email
APIs and SMTP relays optimized for latency, event logs, and inbox placement on notifications.
Read guides →High-volume ESPs
Platforms built for throughput: SendX, SES-front-ends, Elastic Email, SendGrid, Ongage.
Read guides →Developer email APIs
APIs and SDKs for developers: SendGrid, Mailgun, Postmark, Resend, Mailtrap.
Read guides →SMTP relay services
Production-grade relays for transactional and marketing traffic at scale.
Read guides →Marketing email is sent to a list on a schedule and needs consent (opt-in). Transactional email is triggered by a user action (signup, password reset, purchase confirmation) and is sent one-to-one. Providers usually separate the two: marketing platforms optimize for campaigns and segmentation, transactional platforms optimize for latency and deliverability on trigger events. Mixing them on the same infrastructure hurts both.
When your monthly cost passes what a lean ESP would charge (usually around 25,000 to 50,000 subscribers), when you outgrow the segmentation limits, when you need advanced automation or API integration that Mailchimp does not expose, or when your deliverability starts drifting because of shared IP behavior. Migration is painful; the trigger should be significant recurring pain, not a one-off cost calculation.
Yes, at 100k+ emails per month, SES is dramatically cheaper than any packaged ESP. The trade-off: SES is infrastructure, not a product. You get a raw sending endpoint and pay per email. You handle bounces, complaints, suppression, warmup, and reputation yourself. Most SES users layer a front-end (SendX, mailbluster, MailWizz, custom app) on top; the savings still hold once you factor that in.
Only if you have the operational bandwidth. Self-hosting means running an MTA, managing IP reputation, handling bounces and complaints, patching security issues, and doing your own deliverability monitoring. The savings are real (mostly IP costs), but the total cost of ownership includes engineering time. Rule of thumb: send under 100k per month or lack ops staff, use a hosted provider; send over 1M per month with a small deliverability team, self-hosting starts to pay off.
Amazon SES at ~$10 raw, plus your front-end (mailbluster free tier or Elastic Email at ~$20 to $40). SendPulse and Sender.net offer free tiers up to 15k emails per month. For 100k specifically at packaged pricing: Elastic Email, Mailjet, and Sender.net Standard tier land in the $30 to $50 range with decent deliverability.
Warm up the new IP or domain gradually over 4 to 6 weeks: start with your most engaged 5 to 10 percent of subscribers, expand to the next engagement tier weekly. Keep sending from the old ESP in parallel during the ramp. Only cut over the full list after the new sending environment is stable and reputation is established. Skipping warmup means deliverability crashes for months.