What does "email marketing stack" actually mean in 2026?
A stack is the combination of (1) an ESP or marketing app for list management + campaign authoring, (2) a sending pipeline (MTA, relay-as-a-service, or both), (3) deliverability tooling (SPF / DKIM / DMARC monitoring, FBL, postmaster dashboards), (4) analytics and attribution (UTM, link tracking, downstream revenue ties), and (5) consent + identity management (opt-in source, preference center, suppression list). A 2026 stack mixes SaaS pieces with self-hosted pieces — the question is which layer you own.
Should I use a single all-in-one SaaS or compose my own stack?
All-in-one (Mailchimp, Brevo, Klaviyo) is fastest to ship and right for under ~5,000 contacts. Above that the per-subscriber pricing starts compounding. Composed stacks (self-hosted marketing app + cloud SMTP) tend to cross break-even somewhere between 5,000 and 50,000 contacts depending on send frequency. See the cost math on
our cost-savings guide.
What is an MTA and why does it matter?
A Mail Transfer Agent (Postfix, Postal, Haraka, exim) is the software that speaks SMTP to recipient mail servers. Most teams DO NOT run their own MTA — they hand the message to a cloud relay (Amazon SES, SendGrid, Mailgun, Postmark, SparkPost) that maintains the IP reputation. Running your own MTA at scale requires IP warmup, abuse-handling, and FBL processing — significant operational lift. The marketing app + cloud relay split is the dominant 2026 pattern.
How do open-source platforms compare to legacy SaaS?
Open-source marketing apps (AcelleMail, Listmonk, Mautic, Sendy, postal) cover the same use cases as Mailchimp / Brevo / Klaviyo at a one-time license cost (AcelleMail / Sendy) or zero cost (Listmonk / Mautic) — you supply server + sending relay. Each open-source app makes different tradeoffs on UI polish, automation depth, and integration catalog. See the
side-by-side comparisons.
What about deliverability — does the platform matter?
Deliverability is overwhelmingly a function of (1) sender reputation on the IP / domain doing the actual sending, and (2) list hygiene + engagement. The marketing app on top barely moves the needle. AcelleMail, Mailchimp, or anyone forwarding through Amazon SES gets the same inbox-placement profile from SES — the IP reputation is owned by SES, not by the app. The exception is self-managed MTAs, where the platform IS the reputation.
Where does AI fit into the 2026 stack?
Three real-world use cases settled in 2026: (1) subject-line and copy generation with brand-tone constraints, (2) send-time optimization per recipient based on engagement history, and (3) anomaly detection on bounce / complaint spikes. AI doesn't replace the marketing app, the sending pipeline, or the deliverability discipline — it accelerates content production and surfaces patterns operators used to find by hand. See
Aurius.
How long does it take to assemble a self-hosted stack?
For someone who has done it before: ~2 hours (VPS provision, install the marketing app, configure DNS for sending domain, paste SES API keys, send a test). First-timer: a weekend with the documentation in front of you. The time-consuming part isn't the stack — it's migrating an existing list, rebuilding automations, and warming up sending reputation on a new IP if you go that route.
Is build-vs-buy still a real question in 2026?
Yes — but the framing shifted. Building your OWN ESP from scratch is rare and rarely sensible (you're rebuilding AcelleMail / Mailchimp). Buying a SaaS subscription is still the path for under 5K contacts and low engineering capacity. The interesting middle is "buy the app, host it yourself" — one-time license, full source, own infrastructure. That's where the modern self-hosted ecosystem sits.
