A developer-friendly SMTP relay and transactional email service, powered by our email delivery infrastructure. Send password resets, sign-in codes, receipts and alerts over SMTP or a REST API, and hear back about every one.
TRY IT · PICK A MESSAGE
All figures come from the tinyRelay docs, not marketing estimates.
Point existing software at the SMTP relay with the credentials we issue, or send with one HTTP request. Same infrastructure, same sending domains.
Send to many recipients in a single request, each with their own merge attributes and their own metadata.
Add one CNAME for DKIM. An API endpoint checks your DKIM and SPF records before you send.
tinyRelay sends on our email delivery infrastructure, run by the same company and team behind tinyEmail.
SEND, DELIVERED, OPEN and CLICK, plus BOUNCED, UNSUBSCRIBE and SPAM. Signed, retried, de-duplicated for 24 hours, replayable for 5 days.
Every BOUNCED event carries one of 19 documented categories, so your app knows whether to retry, investigate or stop sending.
Credentials issued at onboarding. Any SMTP client.
POST /email/campaign with X-RELAY-ACCESS-TOKEN.
Metadata merges per recipient; the recipient's keys win. Up to 10 keys.
Example email · illustrative
svix-id · svix-timestamp · svix-signature on every request · metadata { user_id: u_1042 }
The recipient's mailbox or quota is full.
Send the reset link the moment it is requested. If the address is dead you get a BOUNCED event, so your app can say so instead of leaving the user waiting.
Example email · illustrative
Sign-up confirmations and login codes need to land now. DKIM signing and a DNS check endpoint help them get there; DELIVERED tells you when they did.
Example email · illustrative
Send order confirmations straight from your backend. The order ID you attach comes back on every delivery event, so support can see what happened to each one.
Example email · illustrative
New sign-ins, failed payments and plan changes. Send them over SMTP or the API and keep a signed record of every delivery event.
Example email · illustrative
Flip the switches. Every behaviour below is in the tinyRelay docs.
Call the REST API from your code. Give each recipient their own merge attributes and metadata in one request.
Connect existing software with the SMTP credentials issued at onboarding. Nothing to integrate.
Attach metadata; it comes back on every webhook.
10 keys is the documented maximum per send.
Add one CNAME, then check it with the API.
One switch per request. Optional link wrapping.
Keys in a header, callers allowlisted, webhooks signed.
Tap through one event's life. Delivery semantics, written down.
Every request carries svix-id, svix-timestamp and svix-signature headers. Delivery is at least once.
Every retry of an event repeats the same svix-id, so deduplicate your processing on it.
A repeat of an event you were already sent is dropped. A genuine second open or click is a new event and still reaches you.
Our duplicate suppression lasts 24 hours. Beyond it, a re-processed event could reach you again.
Event payloads are kept for 5 days, so a missed event can be redelivered. After that it is gone.
Allowlisting an IP isn't authentication. Here's the check, step by step.
Each BOUNCED event carries one of 19 documented categories. They come down to four answers. Pick one to see the categories behind it.
Every BOUNCED event also carries bounceDescription and bounceStatus: the receiving server's own words and DSN code.
Full bounce code reference →Both run on the same infrastructure. It depends on how your app sends today.
Use tinyRelay on its own for the email your app triggers, or alongside tinyEmail, which runs your campaigns and newsletters with its own REST API. Same company, same delivery infrastructure.
How tinyEmail and tinyRelay fit together →Resets, codes, receipts, shipping and billing notices, alerts.
Campaigns, newsletters, segments and automations.
Pick what applies and we'll prepare a quote.
Request pricingShort answers. The docs have the long ones.
A developer-friendly SMTP relay and transactional email service, powered by tinyCo's email delivery infrastructure. You send transactional and application-generated email using SMTP or a REST API, on its own or alongside tinyEmail.
Both run on the same infrastructure. Use SMTP when existing software already sends email; use the REST API when you want one request to send to many recipients, each with their own merge attributes and metadata.
There are no packages to install. Anything that can make an HTTP request works, and the docs include examples for Node.js, Python, PHP, Ruby, Go and cURL.
Seven event types come back to your endpoint as signed webhooks: SEND, DELIVERED, BOUNCED, OPEN, CLICK, UNSUBSCRIBE and SPAM. Your metadata is on every one.
Pricing is based on your monthly sending volume. Tell us what you send and we prepare a quote.
Submit the Get started form. Our team sets up your sending domains with you and sends your SMTP credentials and API key.
SMTP relay or REST API, standalone or alongside tinyEmail. Tell us what you send and our team sets you up.