relay vs 00
Self-hosted email sending and monitoring compared
relay and 00 both provide self-hosted tools for sending email and monitoring delivery. relay sends through SMTP infrastructure you operate, while 00 is built around AWS SES and its event pipeline.

relay: Send Email Through Your Own SMTP Infrastructure
Hyvor Relay is a self-hosted email API that sends and manages email through your own SMTP infrastructure. It suits teams that want delivery controls, logs, and multi-tenant project management without relying on a hosted email API.

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.
| relay | 00 | |
|---|---|---|
| Language | PHP | Elixir |
| License | AGPL-3.0 | AGPL-3.0 |
| Stars | 918 | 1.2k |
| Forks | 65 | 66 |
| Last analyzed | Oct 12, 2026 | Oct 13, 2026 |
Key differences
- relay uses your SMTP infrastructure; 00 requires AWS SES, an SQS queue, AWS credentials, and a verified sending identity.
- relay combines an API with tenant and project management, separate email queues, SMTP conversation logs, and operational monitoring; 00 focuses on an SES sending API and a dashboard for searching messages and recipient-level delivery status.
- relay is built with PHP, Go, and SvelteKit; 00 is built with Elixir.
- Both use the AGPL-3.0 license, but relay also points to commercial licensing for organizations that need it.
- relay supports Docker Compose or Swarm and uses PostgreSQL for its database and queue; 00's SST deployment configures the AWS email pipeline, while its application container needs separate deployment.
- relay is described as active with regular commits and releases; 00 was last pushed on 2024-10-22, so check its current maintenance and compatibility.
Choose relay if you…
- need to send through SMTP infrastructure you operate instead of AWS SES.
- want tenant and project separation, distinct email queues, and SMTP conversation visibility.
- need delivery controls and monitoring across a self-hosted, multi-service system.
Choose 00 if you…
- already use AWS SES and want an HTTP API with a dashboard for delivery events.
- need to investigate message status and activity for individual recipients.
- want SST to configure the SES notification pipeline, with the application deployed separately.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.