Your domain. Your identity.
Send from an address you own. Guided DNS setup helps you connect the domain while keeping your existing inbox and receiving mail in place.
Transactional email · Invitation-only alpha
The email your
app depends on.
The invitation that lets someone in. The reset that gets them back. The receipt they were waiting for.
Send these messages from your own domain, through API or SMTP. Follow what happened without guessing what “sent” means.
Already invited? Open your workspace.
Made for application email
Send it. Know what happened.
Connection settings are only the start. You need a useful answer when a message matters.
Fit the application you have.
Use the API for a new integration, or SMTP with an existing mailer. Both follow the same sending checks and appear in the same message history.
A result you can act on.
See queued messages, receiving-server acceptance, bounces and unknown outcomes. Webhooks can bring recorded email events back to your application.
From invitation to integration
A clear path to your first message.
01 / Connect
Add your sending domain.
Create a project and follow the DNS instructions to verify your domain. Signing and bounce handling are prepared automatically for eligible invited accounts.
02 / Set up
Connect with API or SMTP.
Create an API key or SMTP login for your sending address. Save its secret when it appears, then use the examples or connection settings in your application.
03 / Check
Send your first message.
Send a message to an address you can check, then follow its progress in Messages. Your workspace shows your sending limits and anything that still needs attention.
Clear about the limits
“Accepted” is a step.
It is not an inbox promise.
Accepting your request means we have saved it. Acceptance by the recipient’s mail server means that server took the email. Neither confirms that someone found it in their inbox or read it.
If we cannot confirm an outcome, we say so. A message may already have arrived. Check its history before sending it again, so the recipient does not get it twice.
Sending limits, paused messages and setup issues are visible in your workspace. When a safety hold needs review, contact us.
Before you connect
A few useful answers.
Can I keep my current inbox?
Yes. This service sends your application’s email. It does not host your inbox or replace receiving mail. Keep your existing mail settings and follow the domain setup instructions.
Is this for newsletters or campaigns?
The current alpha is for transactional email: invitations, password resets, receipts and similar messages triggered by your service. Campaigns and promotional sending are outside this alpha.
Who can use the service?
We are testing with a small group of invited friends and family. Public registration is closed.
Closed alpha
Already invited?
Sign in to set up your application and start testing.