A self-hosted SES monitoring dashboard and email API, honestly reviewed. No marketing fluff, just what you actually get when you own your email stack.

TL;DR

What it is: A self-hosted dashboard and REST API layer that wraps AWS Simple Email Service — it automates the SES→SNS→SQS pipeline wiring, gives you a UI to monitor delivery status and bounces, and exposes a clean API for sending transactional emails [1][2].
Who it’s for: Developers and technical founders paying real money to Resend, Postmark, or SendGrid who want to swap in AWS SES (which is dramatically cheaper) without losing monitoring and API convenience [1].
Cost savings: AWS SES charges $0.10 per 1,000 emails. Postmark charges $15/mo for 10,000. Resend charges $20/mo for 50,000. At any meaningful volume — say 100K emails/month — you’re looking at $10 on SES versus $50–90 on managed providers. DoubleZero itself is free (AGPL-3.0) for the core tier [1][2].
Key strength: Packages three things that SES itself doesn’t give you: one-command AWS infrastructure setup via SST, per-recipient delivery tracking, and a REST API wrapper with API-key auth [1].
Key weakness: AWS is a prerequisite, not an afterthought. You need an account, verified sending domain, IAM credentials, and familiarity with SES identity verification before the first email sends. Non-technical operators will hit walls fast [1]. The Pro tier (broadcasts, automations, contacts) is in presale but not yet shipped [2].

What is DoubleZero

DoubleZero, stylized as 00, is a self-hosted email API and monitoring dashboard built on top of AWS Simple Email Service. The project comes in three connected pieces: an SST configuration layer that automates standing up the SES/SNS/SQS event pipeline on AWS, a Docker container running a Phoenix/Elixir web app, and a REST API for sending emails from any application.

The README opens with the problem it’s solving: “SES is an incredibly affordable way to build an email heavy application. However monitoring the emails is a bit of a nightmare, and often requires custom infrastructure. Even setting up the SES → SNS → SQS pipeline is a headache for developers unfamiliar with AWS. And when that is done you’re still left with hooking in or building some custom dashboard for viewing bounces and all the vital information you care about.” [1]

That’s the entire pitch, and it’s more honest than most SaaS landing pages. The tool doesn’t try to be an email platform — it’s a thin, useful layer that makes SES approachable.

The project sits at 1,244 GitHub stars under AGPL-3.0 licensing, maintains a Docker image on Docker Hub (liltechnomancer/double-zero), and earned a Product Hunt “top post of the day” badge on launch, which suggests real developer interest rather than a project that shipped and sat [1][2]. The creator goes by liltechnomancer — this is indie software from a small team, not a funded startup.

One navigation note: searching “DoubleZero” turns up an unrelated blockchain infrastructure protocol in the Solana ecosystem that shares the name. The email tool lives at double-zero.cloud and github.com/technomancy-dev/00.

Why people choose it

Third-party reviews of this specific tool are sparse — it’s young enough that the community record is mostly the README, the Product Hunt comments, and a YouTube walkthrough from “Web Dev Cody” that the README links as recommended onboarding [1]. What the available sources reveal is the underlying rationale, which is straightforward.

The email provider markup problem. SES pricing is public and blunt: $0.10 per 1,000 emails. Resend, Postmark, and Mailgun all charge significantly more — typically $15–90/mo for volumes ranging from 10K to 500K emails. The margin exists because they add deliverability tooling, monitoring, and support that SES doesn’t provide. DoubleZero’s bet is that developers who already trust AWS don’t need to pay that margin — they just need the monitoring and API layer on top of SES, which is what 00 provides for free [1][2].

The SES plumbing problem. Even developers who know SES is cheaper often stay on Resend or Postmark because setting up SES bounce notifications requires manually configuring SES to publish events to SNS, then SNS to forward to SQS, then polling SQS from your own code. It’s documented but tedious. SST’s single-command deploy handles all of it. That specific workflow pain is DoubleZero’s strongest card [1].

Features

Based on the README and official website:

Sending:

REST API at /api/emails for transactional sends [1]
Markdown email with template variable substitution ({{email}}) [2]
HTML and plain-text body support [1]
API key authentication via Bearer token [1]
Official JavaScript client (00-js) for Node.js [2]

Monitoring dashboard:

Email send status tracking [1]
Multi-recipient tracking — a separate message record per recipient [1]
Email body viewing from dashboard [1]
Full-text email and message search [1]
Request and queue log tracking [1]

Infrastructure:

SST integration for one-command SES/SNS/SQS setup [1][2]
Docker image published to Docker Hub [1]
SQLite database (path configurable via env var) [1]
Runs on port 4000, Phoenix/Elixir app (inferred from PHX_HOST and mix phx.gen.secret references in README) [1]

Pro tier (presale, not yet shipping):

Contacts management
Broadcast campaigns
WYSIWYG email editor
SMTP endpoint
Teams
Feed / activity view
Automations [2]

The free AGPL-3.0 tier covers transactional sending and monitoring. The Pro tier adds the marketing-email capabilities — broadcasts, contact lists, automations — that you’d otherwise need Listmonk or Mautic for. Since Pro is currently presale rather than live, the honest answer is that feature is a roadmap commitment, not a shipped product [2].

Pricing: SaaS vs self-hosted math

DoubleZero:

Open-source core: $0 [1]
Pro presale: $175 (listed regular price: $250). Billing model — one-time vs. subscription — is not clearly documented on the website [2]

AWS SES underneath:

$0.10 per 1,000 emails sent (from EC2 the first 62,000/month are free)
SQS costs: fractions of a cent at typical notification volumes

What managed providers charge at 100,000 emails/month:

Resend: ~$90/mo
Postmark: ~$50/mo
SendGrid: ~$35–50/mo
Mailgun: ~$35/mo (pay-as-you-go)

SES + DoubleZero at 100,000 emails/month:

AWS SES: ~$10
VPS for the container (2GB RAM): ~$5–8/mo
DoubleZero software: $0
Total: ~$15–18/mo

That’s $20–75/mo in savings, compounding indefinitely. At 500,000 emails/month the gap widens further — SES costs ~$50, versus $90 on Resend or $150+ on Postmark for equivalent volume.

The math gets less interesting below 5,000 emails/month. Resend’s free tier covers 3,000/month without any infrastructure overhead. At low volume, the operational complexity of running your own stack isn’t worth it.

Deployment reality check

This is the honest part. DoubleZero’s README is upfront about the dependency chain, and it’s longer than most self-hosted tools [1]:

Before you touch DoubleZero, you need:

An AWS account
SES configured with a verified sending domain or email address
DKIM DNS records published (AWS warns this takes up to 72 hours — realistically under 12) [1]
SES→SNS→SQS pipeline (SST automates this if you use the SST path, otherwise manual)
A server or VPS running Docker
Eight environment variables: AWS_SECRET_ACCESS_KEY, AWS_ACCESS_KEY_ID, AWS_REGION, SQS_URL, SYSTEM_EMAIL, SECRET_KEY_BASE, DATABASE_PATH, PHX_HOST [1]

The SST path:

npx sst deploy --stage production

SST sets up SES/SNS/SQS, optionally hosts the container on EC2, creates S3-backed SQLite backups, and configures Route 53 DNS. However, the README is explicit: “Currently SST does NOT deploy the container for you. It just sets up the needed SES pipeline.” The container is a separate step [1]. That’s a footnote that first-timers miss.

What can go sideways:

DNS propagation for SES verification is the most common blocker — you’re waiting on your domain registrar and AWS, not on the software
IAM credentials need the right permissions for SES, SNS, SQS, and optionally EC2/S3/Route53 — it’s easy to under-scope these and get silent failures
SQLite is the only database option. Fine for transactional email tracking, but not ideal if you want concurrent write access from multiple services or horizontal scaling
The Pro features (SMTP endpoint, contacts, broadcasts) are not available yet. If your use case needs any of these, you’re waiting on a shipping date that isn’t publicly committed [2]

Realistic time estimate: A developer familiar with AWS: 1–2 hours to a working instance. A developer new to AWS: half a day, mostly spent on SES domain verification and IAM configuration. A non-technical operator without a developer: wrong tool — the AWS prerequisite is a genuine barrier, not something you can click through.

Pros and cons

Pros

Solves a specific, real problem. SES monitoring requires custom infrastructure. DoubleZero packages it [1].
SST automation. One-command AWS infrastructure setup replaces hours of manual console work [1][2].
Simple REST API. Markdown, variable substitution, JSON body, Bearer auth — integrates cleanly into any stack [1][2].
SQLite. No PostgreSQL to manage. Right call for email tracking — simpler backup, simpler ops [1].
Genuinely open source. AGPL-3.0, auditable, self-hostable, modifiable [1].
JavaScript SDK. Official 00-js client reduces boilerplate for Node.js apps [2].
Cheap to run. A 2GB VPS covers it. Hardware cost is not the bottleneck [1].

Cons

AWS is mandatory, not optional. No AWS, no DoubleZero. No workaround documented [1].
Pro is presale, not product. Broadcasts, contacts, automations, SMTP endpoint — all listed as “Coming Soon” [2]. Buying Pro is a bet on a roadmap.
Small, indie team. 1,244 stars is real traction, but no enterprise support, no SLA, no documented incident response. If the maintainer disappears, you’re holding the code.
SQLite ceiling. Not suitable for high-concurrency or multi-process write loads. No alternative DB option documented [1].
AGPL-3.0 copyleft. Embedding DoubleZero in a commercial product requires open-sourcing your changes. Read the license before building a business on top of it.
SST partial automation. SST sets up the AWS pipeline but not the container — a gap that surprises first-timers [1].
No built-in SMTP in free tier. Apps that send email via SMTP protocol rather than REST API need Pro — which isn’t shipped [2].

Who should use this / who shouldn’t

Use DoubleZero if:

You’re a developer or technical founder paying $20–90/mo for transactional email and willing to spend an afternoon on initial AWS setup to eliminate that recurring cost.
You already have an AWS account and basic SES familiarity.
Your email needs are transactional: notifications, password resets, order confirmations.
You want full ownership of delivery data and don’t want it sitting in a third-party SaaS.
You’re comfortable running and maintaining a Docker container.

Wait or skip if:

You need broadcasts, contact lists, or email automations — those features aren’t shipped yet.
You’re a non-technical founder without a developer to handle AWS setup. The prerequisite stack is real.
You send fewer than 5,000 emails/month — Resend’s free tier is simpler, cheaper in total, and requires no infrastructure.
You need SMTP (not REST API) — that’s Pro-only and coming soon.
You need team roles, audit logs, or user management — none of that is documented in the current release.

Alternatives worth considering

Cloud providers (zero infrastructure):

Resend — clean developer-first API, 3,000/mo free, $20/mo for 50K. Best default if you want no infrastructure.
Postmark — strong deliverability reputation, $15/mo for 10K, more expensive but mature.
SendGrid — market leader, large free tier (100/day), acquired by Twilio — lock-in and price history worth tracking.
Mailgun — pay-as-you-go option; ~$0.80 per 1,000 emails.

Self-hosted alternatives:

Listmonk — mature, open-source, PostgreSQL-backed newsletter and transactional email tool. More features than DoubleZero’s free tier (contacts, campaigns, analytics), active community, doesn’t require AWS. The more complete self-hosted email package today.
Postal — runs its own full SMTP server, no AWS dependency. Heavier operational overhead but completely independent of cloud providers.
Mautic — open-source marketing automation with email. Broader scope, heavier to operate, built for marketing teams rather than developers.
Stalwart Mail Server — full inbound+outbound email stack for operators who want to own the whole pipeline.

For a developer already on AWS who just wants to replace a managed transactional email provider, the realistic comparison is DoubleZero vs. direct SES with your own monitoring code. DoubleZero wins that comparison by saving you the build time. For everyone else, Listmonk or Resend is the simpler path.

Bottom line

DoubleZero solves a real, narrow problem: AWS SES is the cheapest transactional email infrastructure available, but it ships without a monitoring dashboard, without bounce tracking UI, and with a manual event pipeline that’s easy to get wrong. DoubleZero automates the pipeline with SST and adds the dashboard and REST API that SES itself doesn’t provide. For a developer paying $30–90/mo to an email vendor, the savings math is genuine — $10/mo on SES versus $50–90 on Resend or Postmark at comparable volumes.

The honest limitations: this is early-stage indie software with an AWS prerequisite, a Pro tier that’s currently presale rather than live, and no documented path for non-technical operators. If you need broadcasts and automations now, Listmonk is more complete today. If you want zero infrastructure complexity, Resend’s free tier beats the math at low volume. But for a technical founder who lives in AWS and wants to cut a recurring email vendor bill with an afternoon of setup, DoubleZero is the most direct tool for that specific job.

Sources

DoubleZero GitHub Repository and README — technomancy-dev/00, AGPL-3.0, 1,244 stars. https://github.com/technomancy-dev/00
DoubleZero Official Website — pricing, feature comparison, Pro roadmap, SST deployment docs. https://double-zero.cloud