Email and newsletters decision

Astonish Email Limited

A competent developer can build and operate a functional one-account replacement in about a week; you trade away vendor deliverability, support, and polish but not core sending capabilities.

Visit website
You pay

$25/mo

$300/yr

Read off the official pricing page.

You’d pay instead

$50one-off30 h to build

$5/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 1 seat.

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. All Astonish Email Limited alternatives, with the arithmetic →

What a replacement has to do

  • Send marketing/newsletter campaigns by importing/storing subscribers, designing a template, scheduling a send that uses an SMTP/Email provider API, and report opens/clicks.

What it still won’t have

  • Vendor-managed deliverability tuning and ISP relationships
  • Built-in templates, analytics polish, and vendor support
  • Volume discounts and integrated billing/ UX
  • SLA, invoice/enterprise billing flows

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a self-hosted small newsletter/marketing sender using Node.js (Express) + Postgres + React. Include: subscriber management with CSV import and segmentation; a template editor integrating react-email-editor for composing and saving templates; a campaign scheduler UI that enqueues sends; a sender worker that delivers via AWS SES (or SendGrid) with retries and logs; open/click tracking endpoints that update analytics in Postgres and a simple dashboard showing sends, opens, clicks and bounces. Out of scope: enterprise invoicing, multi-tenant billing, advanced deliverability services and ISP relationships. Include sensible error handling, unit/integration tests for critical flows, Dockerfiles and a deploy script for a single small VPS.
How we checked4 sources · 3/3 runs agreed · evidence score 93

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score93

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 · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded