Email infrastructure
Email your product can rely on
An HTTP API and an SMTP endpoint for the mail your application has to send. Requests match Resend's format, so code you already have, including code an assistant wrote for you, works after changing one URL.
A thousand messages a month free, no card. Enough to run a small app on.
- Resend-compatible
- HTTP API and SMTP
- Your own DKIM key
curl -X POST https://pigeonatlas.com/v1/emails \
-H "Authorization: Bearer $PIGEONATLAS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": "Acme <hello@mail.acme.com>",
"to": ["customer@example.com"],
"subject": "Order #4471 confirmed",
"html": "<p>Thanks for your order.</p>",
"text": "Thanks for your order."
}'
Two lanes, never shared
Built around the parts that actually decide whether mail arrives
Your DKIM key, not ours
We generate a key for your domain and sign under our own selector. Your DNS points only at us, so changing what runs underneath never asks your customers to edit a record.
Newsletters cannot delay a password reset
Bulk and transactional mail are dispatched by separate processes that never read each other's work. A broadcast to fifty thousand people does not put a single reset behind it.
Dead addresses stop at the door
A hard bounce or a spam complaint suppresses an address permanently, and the check runs when you submit rather than before delivery, so it never enters the queue at all.
You can see exactly what was sent
Every message is archived as the bytes that actually went out, searchable by recipient, with its full delivery history beside it.
For creators
Followers come and go. Subscribers stay.
One link for your bio: a page with your photo, your socials and a signup form. Followers confirm by email and land on a list you own, so the next algorithm change can't take them with it.
- Four layouts, switch anytime
- Every subscriber confirms from their inbox
- Your page and your list are free
Already using something else?
Moving from Resend is a base URL and a key. The guide covers the one step people skip: bringing your suppression list, which is also the step that costs them.
On deliverability
All posts-
Password reset emails going to spam: the five checks that usually fix it
A password reset that lands in spam is a support ticket and a lost user. Five checks, in the order they most often turn out to be the cause, and how to run each one in a minute.
-
Why Gmail shows 'via' next to your sender name, and how to make it go away
The 'via' label means the From domain and the domain that signed the message disagree. It is not a penalty, but it costs trust and opens, and one DKIM key on your own domain removes it.
-
We got SES production access. Here is exactly what AWS asked.
Amazon granted PigeonAtlas production access on the first request: 50,000 a day, 14 a second. The full text of the request, what the reviewers actually check, and a checklist you can copy.
Verify a domain, get a key, send
The free allowance is there to prove it works for you before anything is decided.
Create an account