hyvor

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.

ActivePHPAGPL-3.0EmailAPISelf Hosted
View on GitHub Compare
Stars
918
Forks
65
Stars, last 30 days
+6
Last commit
19 days ago
Contributors
5

Our take

Activeregular commits and releases

Health score

49/100

How it is scored
Activity
65
Community
45
Issues
53
Pull requests
34

+6 stars in the last 30 days

  • Releases more often than 82% of the projects we track
  • Slower to merge pull requests than 89% of the projects we track

Hyvor Relay is an actively maintained, self-hosted email platform with a broad set of delivery-management features, but adopting it means operating its infrastructure and meeting AGPL-3.0 obligations.

Good fit if

  • You want to send email through infrastructure you manage and can deploy with Docker Compose or Swarm.
  • Your team needs tenant and project separation, delivery logs, retries, and event webhooks.
  • You are comfortable with AGPL-3.0 terms or have arranged an appropriate commercial license.

Look elsewhere if

  • You want a hosted email API and do not want to operate SMTP-related services and PostgreSQL.
  • Your organization cannot comply with AGPL-3.0 and does not want to pursue a commercial license.
  • You need a project with a longer track record: this repository is relatively young, despite regular releases and active issue and pull-request handling.
All health signals
Last commit2026-09-22 (19 days ago)
Commits, last 90 days11
Releases, last 12 months36 (latest 0.0.46, 2026-08-10)
Contributors5 (top contributor: 53% of commits)
Issues closed, last 90 days19 (typically closed in 39 days)
Pull requests merged, last 90 days11 (typically merged in 5 days)
Project age17 months

Checked on 2026-10-12 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

924

Forks

66

Change since Nov 14, 2026: +1 stars·0 forks

Overview

Hyvor Relay provides an API for sending email through SMTP using infrastructure you operate. It is aimed at developers who want to manage email delivery themselves rather than depend on a hosted provider, while still having an API, logs, and operational controls.

The project combines a PHP and Symfony API with Go services and a SvelteKit frontend. It supports Docker Compose or Swarm deployments and uses PostgreSQL for both its database and queue.

Key Features

  • Send email through a developer-facing API backed by SMTP.
  • Separate transactional and distributional email into queues.
  • Handle retries, greylisting, bounces, feedback loops, and suppressions.
  • Manage multiple tenants and isolated projects within each tenant.
  • Inspect send logs and SMTP conversations for up to 30 days.
  • Receive email-event callbacks through webhooks.
  • Monitor with Prometheus metrics, Grafana dashboards, and logs.
  • Delegate DNS management to its built-in DNS server.

Use Cases

  • A development team wants an API for sending application email while operating its own SMTP infrastructure.
  • An agency or organization needs separate tenants and projects for multiple customers or products.
  • An operator wants visibility into SMTP conversations, delivery events, and email-related health metrics.
  • A team sending both transactional and distributional email wants separate queues and automated bounce and retry handling.

What you need

Detected in the repository

  • PHP (main language on GitHub)
  • A Dockerfile, so it can run in a container; a Compose file sets up the related services
  • Automated checks on GitHub Actions

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

For local development, set up the HYVOR development environment, then run:

./run relay

For deployment, see the self-hosting documentation and the README.

Alternatives

  • useSend: useSend uses Amazon SES and also includes marketing campaigns and contact management, while Relay sends through your own SMTP infrastructure.
  • e2a: e2a adds inbound mailboxes and agent replies, and can be hosted or Docker-deployed; Relay focuses on sending through your SMTP infrastructure.
  • 00: 00 is tied to AWS SES and focuses on delivery-event tracking, while Relay sends through your own SMTP infrastructure.
ProjectLanguageLicenseStarsStatus
relayPHPAGPL-3.0918Active
useSendTypeScriptAGPL-3.04.7kActive
e2aGoApache-2.0194Active
00ElixirAGPL-3.01.2kInactive

Considerations

  • This is a self-hosted system, not just a standalone API library. Plan to operate its services and PostgreSQL, which it also uses for queues.
  • The repository is relatively young. Its measured health is active, with regular commits and releases, contributions from several people, and ongoing issue and pull-request handling. The contributor workload is not flagged as concentrated.
  • The README describes a multi-service architecture involving PHP, Go, and SvelteKit, which may mean more operational components than a single-process mail client.
  • The repository is licensed under AGPL-3.0. Review the license requirements for your deployment and distribution model; the project also points to commercial licensing for organizations that need it.
  • The README does not identify a test suite or list a dedicated-IP feature as available, so verify those needs against the current project and documentation before adoption.

Found this useful?

Share it with someone who would like relay.

Comparisons