Deliver.
Sent isn't the same as delivered.
Mail can leave your application, hit the recipient's mail server, get accepted at the SMTP layer, and still end up in spam. The path from application to inbox runs through DNS records, sender reputation, content filters, authentication checks, and platform-specific quirks. Every link in that chain is a place mail can quietly fail. These are the DuoCircle products that handle the whole path.
Four products, four sending patterns
Outbound SMTP
DuoCircle's flagship SMTP relay since 2014. Reputation, throttling, and routing handled inside the platform. 1,000 emails per month free, no credit card required.
Developer Email API (unsent.dev)
HTTP-first email API for developers who want a clean interface instead of configuring SMTP servers. Built on the same delivery infrastructure as Outbound SMTP.
Inbox Placement Testing (InboxIssue)
Test against real corporate mailboxes (Microsoft 365 and Google Workspace business plans with full security stacks enabled), not consumer seed accounts. API-first.
Cold Email Outreach (NuReply)
Bring-your-own-mailbox cold outreach. Connect your existing Google Workspace, Microsoft 365, or SMTP accounts; NuReply orchestrates campaigns through your own mailboxes. Your domains, your reputation.
Different patterns, different architectures
Different sending patterns need different architectures. Transactional mail (password resets, receipts, system notifications) belongs on dedicated relay infrastructure where reputation, throttling, and routing are the platform's problem. That's Outbound SMTP and unsent.dev. Cold outreach belongs on the sender's own mailboxes so reputation builds on the sender's own domains. That's NuReply's bring-your-own-mailbox architecture, deliberately not a shared relay.
The connecting tissue across all of it is deliverability visibility. InboxIssue sits beside the others as the test layer: pre-flight your transactional templates, validate cold-outreach inboxing, gate your CI on placement regressions before customers see broken mail.
Same engineering team across the lineup. When an inbox-placement issue shows up that crosses two products, the team that owns one of them owns the other.
The audience
- Application developers sending transactional email at any volume, from indie SaaS to enterprise platforms
- Operations teams running their own SMTP infrastructure who want a relay that handles reputation and throttling without a six-figure contract
- Email-deliverability-conscious senders who have been bitten once by an inbox placement issue and aren't going to be bitten twice
- Sales teams running cold outreach who want a tool that respects their domain reputation rather than relaying through a shared pool
- Engineering teams wiring deliverability checks into CI to pre-flight transactional sends before they hit production
We're not the right answer if
You're a high-volume, dedicated cold-outreach organization with a stack already wired together (CRM, intent data, multi-channel orchestration). Specialist outreach platforms in that lane will fit your workflow better than NuReply.
You need a battle-hardened transactional API with a long public track record and a giant SDK matrix. The established names in transactional email have those; unsent.dev is earlier in its public arc.
Your traffic is purely consumer (Gmail/Yahoo) and you don't care about corporate placement. Simpler delivery and testing tools may fit your needs.
Talk to an expert about your delivery setup
Same-day response. Real expert on the call. We tell you which product fits the sending pattern.