Email and newsletters decision
Loops
A basic lifecycle email service (contacts, events, workflows, template rendering, and delivery) is realistic for a small technical team to build and run, but you will lose deliverability polish, integration depth, and compliance attestation (SOC2) that the hosted product advertises.
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
- Accept subscribed contacts and events from the app, evaluate workflow triggers/branches, render an email from a stored theme/template, and deliver the message via an email delivery service while recording opens/clicks and updating contact state.
What it still won’t have
- Deliverability expertise and dedicated sending infrastructure/tuning
- Polish of the visual editor and theme management
- Built-in integrations catalog and one-click product SDKs
- SOC2 / compliance attestation and associated assurances
What remains hard
- Compliance and regulation
Trust (SOC2) DPA DPF
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
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 lifecycle email service using Node.js + Express, PostgreSQL, and a simple frontend (React). In scope: REST API to ingest contacts and events, contacts DB schema with subscribed/unsubscribed state, a workflow engine that supports triggers, timers, and branching, a template/theme system (MJML/Handlebars) with a theme token store, integration with Amazon SES (or Postmark) for delivery including handling bounces and open/click webhooks, and basic analytics (sends, opens, clicks). Out of scope: SOC2 certification, an advanced WYSIWYG email editor, and a public integrations marketplace. Include error handling, retries for delivery failures, unit tests for API and workflow logic, and a README with deployment instructions (Docker + docker-compose).
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
- Hard moats found in the evidence-3
- Evidence score61
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 productLoops | Email Marketing Software for SaaS Teams
- official pricingPricing: Free Plan and Contact-Based Plans | Loops
- official productProduct & Lifecycle Email | Loops
- open sourcemautic/mautic
- open sourceknadh/listmonk
Integrity checks
What held up, and what did not.
