Email and newsletters decision
Mail Layer
A competent developer can build a useful self-hosted newsletter sender and transactional API (the core workflows) using existing open-source projects; reproducing the vendor polish, installers, license distribution, and support is more work, so keeping the paid product is reasonable for non-developers or teams wanting turnkey delivery.
Visit website↗Built by Mohd Danish, who ships 3 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off160 h to build
$10/mo6 h/mo upkeep
No published price to break even against.
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 Mail Layer alternatives, with the arithmetic →
What a replacement has to do
- Store contacts and tags, compose a campaign or template, schedule/send via an SMTP/API provider, track opens/clicks and process bounces/unsubscribes.
What it still won’t have
- One-time licensed binary / official Docker image and lifetime updates
- Polished, prebuilt UI and bundled React Email Editor
- One-click Railway/Docker install scripts and official support
- Built-in domain warmup, license management, and priority support
- Pre-tested provider integrations and ongoing product bugfixes from vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Mail Layer does not publish a price we could read, so there is nothing to compare against. What building costs is below.
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 single-container self-hosted email marketing service using Next.js (React) for the dashboard, a Node.js server process, better-sqlite3 for a single-file SQLite DB, and Docker. In scope: user sign-in (simple email token or basic auth), contact import (CSV), tag-based segmentation, HTML/template editor integration (embed React Email Editor), campaign create/schedule/send, an in-process scheduler/worker for batching sends, integrations for SMTP + Amazon SES/SendGrid/Mailgun APIs, bounce/unsubscribe handling, basic open/click tracking, public transactional API endpoint, and Docker Compose deployment. Out of scope: license/key management, hosted billing, multi-tenant license limits, and advanced deliverability tooling (domain warmup UI). Provide error handling, retries for provider failures, configurable rate limiting, nightly DB snapshot to a mounted volume, health checks, and automated tests (unit and integration for sending and webhook handling).
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
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 productMaillayer — Self-hosted Mailchimp alternative
- official pricingMaillayer Pricing
- official docsMaillayer Documentation
- open sourcelistmonk (prior art)
- open sourceMailtrain (prior art)
Integrity checks
What held up, and what did not.
