Email and newsletters decision

Keplars

A capable developer can build a usable transactional email substitute for core sending, templating, and basic tracking, but reproducing Keplars' deliverability, warmup, multi-region SLA, SDK ecosystem, and polished integrations would be difficult and time-consuming.

Visit website
You pay

$1/mo

$12/yr

Read off the official pricing page.

You’d pay instead

$100one-off80 h to build

$20/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 29 seats.

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 Keplars alternatives, with the arithmetic →

What a replacement has to do

  • Accept send requests (API/SMTP) → render template → enqueue/send via an SMTP/relay provider → record delivery events/webhooks (bounces/opens/clicks) → surface basic delivery analytics in a dashboard

What it still won’t have

  • Enterprise-grade deliverability tuning and warmup orchestration
  • Multi-region failover and SLA-backed infrastructure
  • Built-in OAuth sending via Gmail/Outlook with polished UX
  • 24/7 expert support and migration help
  • 100+ native integrations and official SDKs across many languages

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 29 seats.

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 minimal transactional email service using Node.js (Express) backend, Postgres for templates/events, React for a small admin UI, and AWS SES as the SMTP/relay provider. In scope: REST API to accept send requests, SMTP/SES sending with retry/backoff, template storage and rendering with variable substitution and preview sandbox, webhook ingestion to record bounces/deliveries/opens, a suppression list, and a simple dashboard that lists sends and basic metrics. Out of scope: multi-region failover, automated mailbox warmup, advanced deliverability tooling, extensive third-party integrations, and mobile apps. Include authentication for the dashboard, structured error handling, request validation, end-to-end tests for the API, and unit tests for template rendering and webhook processing.
How we checked4 sources · 2/3 runs agreed · evidence score 63

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • Evidence score63

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! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded