Email and newsletters decision
SMTPkit
A single competent developer can build a useful lightweight SMTP-sending replacement in ~34 hours; production-grade deliverability, scaling, and reputation management are the main reasons some teams will keep paying.
Visit website↗Built by Ezzaky Abd, who ships 7 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-off34 h to build
$20/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 SMTPkit alternatives, with the arithmetic →
What a replacement has to do
- Accept SMTP or HTTP send requests, queue messages, perform outbound SMTP delivery with retries, handle bounces/DSNs, and store/send logs for deliverability monitoring.
What it still won’t have
- IP reputation and warmup history
- High-volume deliverability tuning and deliverability analytics
- Managed scaling and SLA-backed support
- Built-in suppression lists and advanced spam feedback handling
What remains hard
- Brand trust
Reliable Email Sending Service
First-year cost
No published price
SMTPkit 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 lightweight SMTP sending service in Go, containerized with Docker, using Postgres for message storage and Redis for work queue. Core features in scope: SMTP listener (TLS, AUTH), REST API to submit messages, queued outbound delivery worker with MX resolution and retry/backoff, bounce/DSN processing, basic delivery logs stored in Postgres, health checks and Prometheus metrics. Out of scope: multi-tenant UI, advanced analytics, paid billing, and IP warmup automation. Include TLS cert setup docs, error handling for network and DNS failures, tests for delivery and retry logic, and docker-compose and Kubernetes manifests for deployment.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- Evidence score86
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 · 3
Every page the run actually retrieved.
- official productSMTPKit - Cheap SMTP Server | Reliable Email Sending Service
- open sourceNotifuse/notifuse
- open sourceBillionmail/BillionMail
Integrity checks
What held up, and what did not.
