Email and newsletters decision
MailerLite
A single engineer can build a usable, narrow email-marketing replacement (capture, send via SMTP provider, simple automations, and basic reports), but reproducing MailerLite’s deliverability, templates, integrations, and polished UX is costly and ongoing—so keep paying for full product capabilities unless you only need a minimal workflow.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Collect subscribers via forms/landing pages → store contacts and segments → design and send campaigns (drag‑and‑drop or HTML) → run simple automations (time or event triggers) → track opens/clicks and manage bounces/unsubscribes.
What it still won’t have
- Deliverability optimization and dedicated IP management
- Built-in email verification and list hygiene
- Pre-built templates, editors and UX polish
- Integrations ecosystem (Shopify, WordPress, Zapier, etc.)
- 24/7 support and onboarding resources
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 3 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted minimal email-marketing service using Node.js + Express, Postgres, Redis, and a transactional SMTP provider (SendGrid or Mailgun). Include: (1) public landing page and embeddable signup form that writes subscribers to Postgres; (2) simple admin UI to create/edit HTML templates and schedule/send campaigns to a segment; (3) send worker that pulls jobs from Redis queue and posts to SMTP API with retry/backoff and rate limiting; (4) automation engine that triggers one-step follow-up emails by time or on subscribe; (5) tracking endpoints for opens/clicks, bounce/unsubscribe handling and basic reports. Out of scope: visual drag‑and‑drop editor, multi-tenant billing, advanced deliverability tooling (IP warmup/seedlist), and dozens of third-party integrations. Include input validation, error handling, unit tests for core modules (subscribe, send-worker, automation), and Dockerfiles + docker-compose for local deployment.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productMailerLite homepage
- official pricingMailerLite pricing
- official docsMailerLite email marketing features
- open sourceknadh/listmonk
- open sourcemautic/mautic
Integrity checks
What held up, and what did not.
