tinyEmail and tinyRelay: every kind of email, one company.
tinyEmail runs the email your team sends: campaigns, newsletters and audiences, with its own REST API. tinyRelay sends the email your app triggers: password resets, receipts and alerts, over SMTP or a REST API. Use either on its own, or both together.
Illustrative messages.
Transactional vs marketing email, in one line each.
A transactional email is triggered by something a person did in your product, and they expect it. A marketing email is something your team decides to send to an audience. The difference shapes the product you send it with.
Sent by your app, one person at a time
- Password resets, sign-in codes, verification emails
- Order confirmations, shipping notices, invoices
- Security, billing and account alerts
- Sent over SMTP or POST /email/campaign
- Signed webhook events back for every email
Sent by your team, to an audience
- Campaigns, newsletters and announcements
- Audiences, segments and suppression lists
- Templates and sender identities
- Scheduled one-off and recurring campaigns
- Run from the app or the tinyEmail REST API
Three businesses. Two products. No overlap.
Pick a business to see which product handles which email.
An online store plans its promotions in tinyEmail, and its store platform sends every receipt and shipping notice through the tinyRelay SMTP relay.
tinyEmail handles
marketing- Seasonal sale campaigns to segments
- A weekly new-arrivals newsletter
- Suppression lists for people who opted out
- Per-domain campaign reports
tinyRelay handles
transactional- Order confirmations, over SMTP from the store platform
- Shipping notifications
- Invoice emails
- Account password resets
A SaaS product sends its in-app notifications through the tinyRelay API, and uses the tinyEmail API from inside the app to keep audiences in sync and run product-update campaigns.
tinyEmail handles
marketing- Contacts and attributes synced with PUT /account/customer
- Product-update campaigns created and started by API
- Onboarding newsletters on a recurring schedule
- Templates and sender identities managed in code
tinyRelay handles
transactional- Sign-in codes and verification emails
- Password resets
- Security and billing alerts
- Webhook events tied to user IDs by metadata
A publisher creates and schedules its newsletters through the tinyEmail API, and sends every subscriber account email through tinyRelay.
tinyEmail handles
marketing- Daily and weekly newsletters, scheduled by API
- Audience imports and list cleaning
- Suppression lists kept in sync
- Engagement reports pulled into their own dashboards
tinyRelay handles
transactional- Subscription confirmation emails
- Sign-in links and codes
- Payment receipts for paid subscriptions
- Account change notices
Illustrative stories, not customer case studies.
Which product for which email.
A quick rule: if your code sends it because a person did something, use tinyRelay. If your team plans it for an audience, use tinyEmail.
tinyRelay
tinyEmail
It depends
tinyRelaytinyEmailSame company. Same delivery infrastructure.
tinyRelay is a developer-friendly SMTP relay and transactional email service, powered by our email delivery infrastructure. It is run by the same team as tinyEmail, and it is available on its own or as a complementary product for tinyEmail customers.
CNAME → tec1.dkim.tinyemail.com
tinyRelay signs your mail with DKIM through a record that points at tinyEmail's infrastructure. More on deliverability.
The tinyRelay API docs and the tinyEmail API docs sit side by side. The tinyEmail API is available on Enterprise accounts.
tinyEmail customers can ask for a dashboard feature to be exposed in the public API, and the team will work to expose it.
tinyEmail and tinyRelay questions.
Ready to send transactional email? Start with the SMTP relay or the email API.
tinyEmail is an email marketing platform with a REST API for campaigns, audiences, senders, templates and reporting. tinyRelay is an SMTP relay and transactional email service for the email your app triggers, such as password resets, receipts and alerts.
No. tinyRelay is available as a standalone service. It is also available as a complementary product for tinyEmail customers.
Yes. tinyRelay runs on the same email delivery infrastructure and is run by the same team as tinyEmail. One sign of it: tinyRelay's DKIM record points to tec1.dkim.tinyemail.com.
Yes. tinyEmail has a REST API for contacts, audiences, campaigns, templates, senders, suppressions, segments and reporting. The docs say it is available on Enterprise accounts. tinyEmail customers can also ask for a dashboard feature to be exposed in the API.
If your app sends it the moment someone signs up, it is transactional and tinyRelay fits. If it is the first step of a campaign your team plans and schedules, tinyEmail fits.
Send transactional email with a service that reports back.
SMTP relay or REST API, standalone or alongside tinyEmail. Tell us what you send and our team sets you up.