Hyvor Relay is a self-hosted email API for transactional and marketing mail, built for teams that want SendGrid-style sending on infrastructure they control. It pairs a sending API, SMTP relay, and SDKs with dedicated IPs, domain authentication, campaigns, contact management, and delivery analytics. The codebase is open source under AGPL-3.0, with Docker and Kubernetes self-hosting today and a managed cloud on the waitlist.[1][2]
Quick verdict
Teams that send product email from their own infrastructure benefit most from Hyvor Relay. The concrete capability behind that recommendation is domain-authenticated sending over API or SMTP with dedicated IPs, templates, webhooks, and analytics in one console. The material constraint is operational: self-hosting email means owning DNS, reputation, IP warmup, and bounce handling, so teams without anyone comfortable running infrastructure should choose a managed provider instead. If your team can run Docker and manage a domain's DNS, start with self-hosted Hyvor Relay; if you want someone else to own deliverability on day one, choose a managed service like SendGrid.[1][2]
Key features
API, SMTP, and SDK sending paths Transactional mail goes out from application code through a REST API, an SMTP relay, or official PHP, Node, and Python SDKs, with API keys managed per project.[1][2]
Dedicated IPs per project Each project sends from its own dedicated IP addresses, so a sender's reputation is isolated instead of pooled with strangers.[1]
Domain authentication with SPF, DKIM, and DMARC Domains are verified with SPF, DKIM, and DMARC before sending, and the console checks each domain's records so misconfiguration surfaces early.[1][2]
Campaign builder with lists and segments Marketing sends run from contact lists with segmentation, custom properties, and template-based composition in the same console.[1]
Contact management with imports Subscribers, custom fields, and list membership live in the same system that sends, with bulk import for migration.[1]
Delivery analytics with engagement tracking Sends, opens, clicks, bounces, and complaints are reported per message and per campaign for debugging and tuning.[1]
Webhooks for delivery events Send, delivery, bounce, and engagement events push to application endpoints so apps can react without polling.[1]
OIDC single sign-on Console access supports OpenID Connect with Entra ID and Google; LinkedIn, GitHub, and GitLab support is announced as coming soon.[1]
Who will love it
Product teams sending their own transactional mail Teams that send product email from their own stack get API and SMTP paths, templates, webhooks, and analytics without per-message vendor pricing.[1][2]
Small teams running campaigns on owned infrastructure Lists, segments, and campaigns live in the same console that sends, and subscriber data stays in the operator's own database.[1]
Teams with residency or control requirements EU or US region choice is documented for the planned cloud, and full self-hosting on PostgreSQL or MySQL is available today.[1]
Who should avoid it
Teams with nobody to run infrastructure Self-hosted email means owning DNS records, IP warmup, monitoring, and upgrades, which needs someone comfortable running infrastructure.[1][2]
Teams wanting managed deliverability on day one The managed cloud is still on the waitlist with no published price, so no SLA-backed hosted sending exists yet.[1]
Senders needing warmed high-volume scale immediately Dedicated IPs require warmup and volume ramp before inbox placement stabilizes, so instant high-volume scale is not the starting point.[1]
Alternatives and compatibility
SendGrid is the managed counterpart SendGrid covers the same transactional-sending workflow as a hosted service; Hyvor Relay explicitly positions itself as its self-hosted alternative. This comparison is editorial, not vendor-endorsed.[1][2]
Docker and Kubernetes self-hosting Self-hosting runs from Docker images with Kubernetes support on PostgreSQL or MySQL under AGPL-3.0.[1][2]
Flat seat pricing instead of usage billing Self-hosted seats cost $5 per user per month for support and updates as listed in October 2026, with no per-message charge documented.[1]
Questions worth asking
What is the best Hyvor Relay alternative for non-technical users?
Is Hyvor Relay really no-code?
How much does Hyvor Relay cost per month?
Self-hosting is free under AGPL-3.0, with console seats at $5 per user per month covering support and updates, as listed in October 2026. The managed cloud has no published price yet and remains on a waitlist, so hosted sending costs are currently unknown.[1]
Sources and editorial review
Source research. Reviewed on October 11, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Hyvor Relay: Email, minus the middleman
official · Observed October 11, 2026
Official product site: privacy-focused transactional plus marketing email on dedicated IPs, Console/API/SMTP/SDK sending, domain authentication, deliverability toolkit, campaigns, contacts, analytics, OIDC SSO, EU/US regions, Docker/Kubernetes self-hosting on Postgres/MySQL under AGPL, $5 per user per month self-host seat, managed cloud on waitlist.
- hyvor/relay repository
official · Observed October 11, 2026
hyvor/relay repository: self-hosted alternative to SES, Mailgun, and SendGrid; AGPL-3.0 license; about 1,700 stars with active 2026 development; API keys, webhooks, domain-authenticated sending, Docker-based setup.