For SaaS teams
Tell your users what shipped. Reliably, every time.
Changelogs and release notes are a job of their own. day3 does that one job well, with deliverability and compliance built in and pricing that ignores list size.
Sound familiar?
- Your marketing platform is overkill for a changelog, and it bills by contact count.
- Updates have to land in the inbox every time, without anyone babysitting sender reputation.
- Compliance (unsubscribe, suppression, consent) has to be handled right, not bolted on.
- Your app already sends transactional mail through a second vendor, on a second domain, with a second reputation to watch.
How day3 fits
Built for the update use case
Write the release note, pick the audience, send. No campaign-builder maze in the way.
Deliverability & compliance, standard
Authenticated domains, one-click unsubscribe (RFC 8058), auto-suppression of bounces and complaints, and auto-pause on bad reputation.
Unlimited subscribers
Put your whole user base on the list. You're billed by sends, so list size never moves the price.
Sends once, never twice
A retried send never duplicates. Every update goes out once, to the right people, with live delivery stats.
What that costs, concretely
20,000 users. Your app sends 30,000 transactional emails a month, and you ship a product update to everyone twice.
$25/mo
70,000 emails a month fits the 100,000 plan. The 20,000 subscribers are free, on this plan and every other.
Split across two vendors that's two allowances, two DKIM setups, two reputations and two invoices, for the same 70,000 emails.
One domain, one reputation
The usual SaaS setup has transactional mail on one vendor because engineering picked it, and campaigns on another because marketing did. It works, but it splits the thing you can least afford to split: sender reputation. Two DKIM selectors on the same domain, or worse two domains, means two reputations that mailbox providers score separately, and a bad campaign can drag down the deliverability of your password resets.
Consolidating means one authenticated domain, one reputation to keep clean, and one dashboard when a customer says the reset never arrived. It also means the monthly volume is a single number against a single allowance rather than two subscriptions sized independently.
The behaviours that should differ still do. Campaigns respect unsubscribes; transactional ignores them, because leaving the newsletter shouldn't stop a receipt. Both refuse hard bounces and complaints, because those addresses damage you whatever you're sending. And if bounce or complaint rates climb toward the thresholds your provider cares about, sending pauses rather than continuing until someone external makes the decision for you.
For the compliance side: one-click unsubscribe is implemented to RFC 8058, which Gmail and Yahoo now expect from bulk senders rather than treat as a nicety. Consent timestamps and IPs are recorded for form signups. Your postal address is appended to campaign footers. None of that is a paid add-on.
When day3 is the wrong call
If a marketing team owns email and needs approval workflows, A/B testing, multi-touch attribution or a shared content calendar, day3 will feel thin, because it is: those are deliberate omissions rather than a roadmap. It's also the wrong fit for agencies managing client accounts, since there's no multi-account or white-label layer.
Questions
- What's the best way to send product update emails?
- Use a tool built for that one job. day3 sends changelogs and 'what's new' emails with deliverability and compliance built in, unlimited subscribers, and pricing by sends rather than contact count.
- Does day3 handle unsubscribes and compliance?
- Yes. Every email carries one-click unsubscribe, bounced and complained addresses are suppressed automatically, consent IP is stored for form signups, and your mailing address is appended to footers as required.
- Can we send transactional and marketing email from the same domain?
- Yes, and that's the point. Both leave the same verified domain against the same monthly allowance, so there's one reputation to keep clean instead of two. Unsubscribes apply to campaigns only; hard bounces and complaints are refused for both.
- Does day3 support subscription topics, so users choose what they hear about?
- Yes. Topics let a contact opt into some kinds of email and not others, which usually beats an all-or-nothing unsubscribe for a product list. Saved segments cover the other direction, targeting by custom field or status.
- What happens if our sending reputation degrades?
- Bounce and complaint gauges are scaled to your provider's own thresholds, and sending pauses automatically if reputation crosses into risky territory rather than continuing until someone else stops you. That's a guard, not a penalty: it protects the domain your transactional mail also depends on.
Keep reading
- APIOne REST API for your app's transactional email, your audiences, and your campaigns, plus an MCP server that turns your AI editor into a composer. Built so migrating from another provider is one script and staying in sync afterwards is a webhook handler.Read on
- DeliverabilityAuthenticated domains, one-click unsubscribe, and automatic suppression of bounces and complaints.Read on
- MetricsOne page for deliverability, reputation, and engagement across every campaign: opens, clicks, bounces, complaints, and unsubscribes, with a per-campaign breakdown.Read on
- SecurityEU-only hosting and data residency, an honest compliance posture, and every sub-processor named.Read on
- day3 vs ResendResend set the bar for what an email API should feel like, and day3 sends transactional in the same shape: one POST, an idempotency key, per-email delivery status.Read on
- GDPRHow day3 acts as your processor, the rights it upholds, and the agreements on offer.Read on