Email and newsletters decision
Bento
A capable engineer can build a usable replacement for core sending, transactional API, and simple automations in a week, but you lose Bento's AI features, deliverability operations, and SOC2/audited compliance — so keep paying if those matter.
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. All Bento alternatives, with the arithmetic →
Code Bento publishes itself
Not a way out of the subscription - these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Store subscribers and events, render/send templated emails via an email provider, run simple automations (trigger -> send), provide a transactional REST API and basic deliverability/auth (SPF/DKIM).
What it still won’t have
- AI-powered pre-flight checks and AI agents
- SOC 2 Type II compliance and third-party audit
- Managed deliverability guidance, migration assistance, and reputation monitoring
- Hosted shared inboxes / AI reply agents and chat add-on
What remains hard
- Compliance and regulation
SOC 2 Type II compliant · Audited by OneLeet 30-day unlimited trial · Cancel anytime · Migration quote
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 minimal self-hosted email platform using Postgres, Node.js (Express), a worker queue (BullMQ), and AWS SES for sending. In scope: subscriber storage + import endpoint, templating and campaign scheduling (MJML), transactional REST API with API key auth, basic automation runner (event -> send), SPF/DKIM guidance and DNS-checking endpoint, logging and webhooks for bounces. Out of scope: SOC2, AI pre-flight checks, shared inbox/chat, deliverability consultancy. Include error handling, retries, tests for API endpoints and worker behavior, and a README with deployment steps (Docker + Terraform for infra).
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Hard moats found in the evidence-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 productBento product home
- official pricingBento pricing
- official docsBento documentation
- open sourceknadh/listmonk
- open sourcemautic/mautic
Integrity checks
What held up, and what did not.
