technomancy-dev

00: Self-Host an AWS SES Email Dashboard

00 is a self-hosted dashboard and API for sending email through AWS SES and monitoring delivery events. It connects SES notifications through SNS and SQS, but has had no recent commits or releases.

InactiveElixirAGPL-3.0EmailSelf HostedDocker
View on GitHub Compare
Stars
1.2k
Forks
66
Stars, last 30 days
-2
Last commit
2 years ago
Contributors
4

Our take

Inactiveno commits in over a year

Health score

20/100

How it is scored
Activity
19
Community
21
Issues
21
Pull requests
20

-2 stars in the last 30 days

00 addresses a specific SES monitoring gap, but its inactive development and highly concentrated contributions make it a cautious choice for new production deployments.

Good fit if

  • You use AWS SES and want a self-hosted dashboard for email status and recipient-level tracking.
  • You can run a Docker container and configure AWS credentials, SES, and SQS.
  • You are comfortable with the AGPL-3.0 license and the project's current maintenance state.

Look elsewhere if

  • You need an actively maintained project, since there have been no commits or releases in over a year.
  • You need evidence of regular issue or pull request handling; none were closed or merged recently.
  • You need SST to deploy the application container, which the README says it does not currently do.
All health signals
Last commit2024-10-22 (2 years ago)
Commits, last 90 days0
Releases, last 12 months0
Contributors4 (top contributor: 93% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age2 years

Checked on 2026-10-13 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

1,244

Forks

65

Change since Nov 17, 2026: 0 stars·0 forks

Overview

00 helps developers send email through AWS SES and monitor what happens afterward. It provides an API for queuing email and a dashboard for searching messages, viewing email bodies, and tracking statuses, including per-recipient status.

It also includes an SST configuration step for setting up the SES-to-SNS-to-SQS pipeline. You run the application in a Docker container; SST configures the AWS pipeline but, according to the README, does not currently deploy the container.

Key Features

  • Send email through a POST /api/emails endpoint authenticated with a bearer API key.
  • Accept Markdown or HTML email bodies, multiple recipients, attachments, headers, and provider options.
  • Track email status, including separately for each recipient.
  • Search emails and recipient messages, and view email bodies in the dashboard.
  • Configure the AWS SES notification pipeline with SST, or follow the manual AWS setup guide.
  • Log requests and queue activity.

Use Cases

  • A developer building an email-heavy application can send messages through SES and inspect delivery events in one self-hosted service.
  • A small team can investigate bounces or other recipient-specific outcomes without building its own SES event dashboard.
  • An AWS operator familiar with SES can use the SST setup or manual configuration guide to connect SES events to the application.
  • A team that already runs Docker can host the dashboard alongside its application and call its email API.

What you need

Detected in the repository

  • Elixir (main language on GitHub)
  • A Dockerfile, so it can run in a container
  • A test suite

License in plain words

AGPL-3.0network copyleft

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license notice
  • Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Set EMAIL_IDENTITY and run sst deploy to configure the AWS pipeline, then run the published Docker image with the required environment variables. See the README for AWS setup, container configuration, and API details.

Considerations

The project is marked inactive, with no commits in over a year and no releases in the past year. Although it has several contributors, most of the code comes from one person, so ongoing maintenance depends heavily on a single contributor. Recent issue and pull request activity also shows no closures or merges.

Deployment requires AWS SES and SQS configuration, AWS credentials, and a Docker-hosted application. The documented setup uses a SQLite database path. The README describes planned Pro features such as teams and advanced analytics, so do not assume those capabilities are available in the described project. AGPL-3.0 terms may also affect how you distribute or offer modified versions of the software.

Found this useful?

Share it with someone who would like 00.

Comparisons