Email infrastructure for applications and support systems.
Authenticated SMTP relays with DKIM and DMARC alignment, an HTTP API for sending from applications, inbound processing that turns replies into webhooks — the same mail path that carries Joy's own verification codes, invoices and help-desk threads.
Mail from a fresh server rarely arrives. Outbound port 25 is closed on new accounts across the industry, including on Joy, because one compromised VPS can burn the reputation of a whole prefix. Joy Email is the answer we built for ourselves first: every verification code, invoice and ticket reply from the console already travels through it, and every reply a customer sends from their inbox comes back through its inbound processing into the help desk.
For customers it becomes two things. An authenticated relay — SMTP with TLS and per-application credentials, plus an HTTP API — that signs your mail with DKIM, aligns it with your SPF and DMARC records and sends it from IP space with a maintained reputation, with delivery, bounce and complaint events posted to your webhook. And inbound processing: mailboxes or catch-all addresses on your domain that turn incoming messages into structured webhooks so replies land in your application, your CRM or a Joy-hosted help desk.
Email is in build. Today, transactional mail from Joy servers goes through your own provider or a relay you run; port 25 is opened by ticket for accounts in good standing with a documented SPF/DKIM/rDNS setup.
E1 · E2 · E3
The three things this product line is built around — the same three boxes you see on the tile.
Business email handling
Inbound processing for support systems and automated workflows: replies become webhooks with parsed headers, body and attachments, threaded by reference so conversations stay together.
End-to-end systems for modern infrastructure
One relay for every server and hosting site on your account, with per-application credentials, rate limits and suppression lists, and delivery events flowing back to your application.
Email infrastructure platform
DKIM keys generated per domain, DMARC reports summarised in the console, maintained sending reputation on Joy IP space, and an HTTP API for teams that would rather not run SMTP at all.
Specification
| Outbound | SMTP submission over TLS (587/465) and an HTTPS send API; per-application credentials with separate limits |
|---|---|
| Authentication | DKIM signing with keys per domain, SPF include, DMARC alignment guidance and report summaries; rDNS on sending addresses |
| Deliverability | Dedicated or pooled sending addresses on Joy IP space with maintained reputation; bounce and complaint handling; suppression lists |
| Inbound | Mailboxes and catch-all on your domain; messages parsed (headers, text/HTML, attachments) and posted to your webhook; threading by reference |
| Events | Delivered, deferred, bounced, complained and opened events by webhook and in the console |
| Templates | Optional server-side templates with variables for transactional mail; plain SMTP works with any framework |
| Limits | Volume per credential and per account; bulk marketing mail is not the product — see the Acceptable Use Policy |
| Today | Port 25 opened by ticket for accounts in good standing with SPF/DKIM/rDNS; console mail already runs on this platform |
Three steps
Verify a domain
Add the DKIM and SPF records shown in the console; DMARC guidance is generated for your policy.
Create credentials or an API key
One per application or server, each with its own limits, so a leaked key is revoked without touching the rest.
Send, receive, react
Point your framework at the relay or call the API; configure inbound webhooks for replies; watch delivery events in the console.
Where Email fits.
Questions about Email.
Can I send from my VPS today?
Is this for newsletters or marketing?
How does inbound work?
What about DMARC reports?
More answers in the full FAQ — billing, network, DDoS, backups, support and legal.
Per message, published at launch
Early-access customers are quoted by ticket. Until then, relay through your provider on port 587 or ask for port 25 on a server with SPF, DKIM and rDNS in place.
Works with
Build Email into your stack.
Create an account and deploy in under ninety seconds, or talk to sales about a design for your workload — regions, sizes, timelines and a quote within one business day.