DashForDevs Emails
Your domain.
Your mailboxes.
Connect a domain you own, publish the records we show you, and send and receive as test@yourdomain.com. HIPAA-minded from the first commit: encrypted at rest, audited on every read, carried only by AWS.
How it works
Three steps from a domain to an inbox
No mail server to run and no MX tutorial to follow. The dashboard tells you what to publish, checks it, and tells you when you can send.
Connect your domain
Type the domain you already own. We register it with Amazon SES and generate the exact DNS records it needs, nothing else.
Publish the DNS records
Copy each record into your DNS provider, or paste the whole set as a zone file. Notes for Cloudflare, GoDaddy, Namecheap and Route 53 are right beside them. Press Check DNS to see what is live.
Create addresses
Make test@yourdomain.com, support@, billing@ or a catch-all. Grant teammates access, read and reply in the browser, or send from your servers with an API key.
What you get
Mail for teams that handle sensitive mail
Built for clinics, agencies and products that send things people would rather keep private.
SES-backed sending
Mail goes out through Amazon SES with TLS required on every hop, DKIM on your domain, and a reputation kept separate for each workspace.
Encryption at rest
Subjects, bodies, headers and attachment names are encrypted field by field under a key used only by this service, on top of encrypted storage.
Audit logging
Every time a message is opened, listed or downloaded, the access is recorded by message id in an append-only, hash-chained log. Never the content.
API keys
Send from your own servers with scoped keys that are shown once, stored hashed, and revocable. Retried sends with the same idempotency key go out once.
Careful by default in the browser
Mail renders in a locked-down frame with scripts off and remote images blocked until you choose to load them, so opening a message does not tell the sender.
Access per mailbox
Your DashForDevs organization decides who is in the team. Each mailbox decides who on that team can read it and who can send from it.
For developers
Send from your servers with one request
Create a key in the dashboard, scope it to sending, and POST JSON. Attachments, replies and delivery status work the same way they do in the inbox.
curl https://tapi.dashfordevs.com/emails/v1/emails \
-H "Authorization: Bearer dfd_live_sk_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042-receipt" \
-d '{
"from": "test@yourdomain.com",
"to": ["customer@example.com"],
"subject": "Your order has shipped",
"text": "It should arrive on Tuesday."
}'Where it stands
Designed in HIPAA scope, and honest about it
Emails was designed for protected health information from its first commit, and every control in the table is running today. We do not yet sign a Business Associate Agreement for it, so please do not send protected health information through it until we do. The full picture is on our HIPAA page.
- Mail carried by
- Amazon SES only
- Outbound transport
- TLS required
- Content at rest
- Field-level encrypted
- Reads of a message
- Audit logged
- Business Associate Agreement
- Not yet available
Ready when your DNS is
Sign in with the DashForDevs account you already have. Your organization, your team and your roles come with you.