AWS SES Cold Email Tools Compared (2026)

Wed, 22 Jul 2026 06:12:11 +0000

Amazon SES is the cheapest way to send cold email at scale, $0.10 per 1,000 emails, but SES on its own has no campaign builder, no sequences, and no reply tracking. You need a tool on top of it. Here's how the main options actually differ.

Quick comparison

EmailQo connects your own AWS SES account natively. Flat monthly pricing, $19 to $89. Built-in warmup on every plan. Best for founders and small teams who want full control of their own sending infrastructure.

Instantly does not connect your own SES account, it uses managed sending pools instead. Volume and contact-tiered pricing. Built-in warmup. Best for teams that want a fully managed platform and don't want to touch AWS.

Smartlead uses the same managed-pool model as Instantly. Per-seat plus volume pricing. Built-in warmup. Best for agencies running many client accounts through one dashboard.

Mailforge connects your own AWS SES account, but infrastructure only, with no campaign layer. Flat pricing. Built-in warmup. Best for teams that want SES-based infrastructure but plan to use a separate tool for campaigns.

Mailgun and SMTP2Go connect to your own SES setup, but as a raw SMTP relay only, with no campaign or sequence features. Usage-based pricing, no warmup. Best for developers who want raw SMTP delivery, not a campaign tool.

Which cold email tools let you connect your own AWS SES account?

Most well-known cold email platforms, Instantly and Smartlead included, route your campaigns through infrastructure they manage. You don't configure your own AWS account, and your domain's reputation sits alongside other users on the same shared pools. That's a reasonable tradeoff if you want the lowest setup effort, but it means your deliverability partly depends on how well other customers on the platform are behaving.

A smaller group of tools take the opposite approach: you bring your own AWS SES account, and the platform only handles campaign logic, sequences, warmup, and reply detection, on top of it. EmailQo and Mailforge both work this way. The difference between them is scope: Mailforge is infrastructure-only, so you'd still need a separate campaign tool. EmailQo includes the campaign layer, sequences, AI reply classification, pre-send deliverability checks, on top of your own SES connection, so it's the full stack rather than half of it.

Why does the sending infrastructure choice matter for deliverability?

Your sender reputation is tracked by receiving mail servers against the domain and IP you send from. On a shared platform, your reputation exists alongside every other customer using the same pool. If another sender on that pool triggers spam complaints, mailbox providers can associate that behavior with the shared infrastructure, which can affect your inbox placement even if your own sending is clean.

Connecting your own AWS SES account removes that shared-pool variable entirely. Your domain's reputation reflects only your own sending history. The tradeoff is setup: you need to verify a domain, configure SPF, DKIM, and DMARC records, and request SES production access before you can send freely, none of which is required on a fully managed platform like Instantly.

What does Amazon SES actually cost for cold email?

AWS bills $0.10 per 1,000 emails sent through SES, with no monthly minimum and no per-contact fee. Sending 50,000 emails a month costs about $5 in AWS charges. Compare that to Instantly's Hypergrowth plan at $97/month for 100,000 sends, or Smartlead's per-seat pricing, and the gap widens the more volume you send. The catch is that SES pricing only covers the sending itself; whichever campaign tool you use on top (EmailQo, Mailforge, or a self-built solution) is billed separately.

Do I need SES production access before I can send cold email?

Yes. Every new SES account starts in a sandbox that only allows sending to email addresses you've manually verified, capped at 200 messages per day. You request production access from the SES console, describing your use case, expected volume, and how you handle bounces and complaints. AWS typically responds within one to three business days. EmailQo has a full walkthrough of this process, including the exact form fields AWS asks for.

How does EmailQo compare on pre-send deliverability checks?

Before sending a campaign, EmailQo checks SPF, DKIM, and DMARC record validity, scans the message for spam-trigger words, and checks the sending domain against major blacklists, all automatically, before the first email goes out. This runs whether you've connected Gmail, Outlook, Zoho, or Amazon SES. Instantly and Smartlead don't run this kind of check as a built-in step; catching a bad DNS record or a blacklisted domain generally means testing it yourself first.

The honest tradeoffs

Choose a managed platform like Instantly or Smartlead if you want the lowest setup effort and don't want to configure AWS, DNS records, or SMTP credentials yourself, or if you need a built-in lead database, which EmailQo does not offer.

Choose EmailQo if you want your domain reputation fully isolated from other senders, you're already using or open to using Amazon SES, and you want flat pricing that doesn't scale with contact count. EmailQo's plans start at $19/month with a 7-day free trial.

FAQ

Can I use Amazon SES directly for cold email without another tool? Technically yes, but SES has no campaign builder, sequence logic, or reply tracking on its own. Most cold email senders use SES as the delivery layer underneath a separate campaign tool.

Is Amazon SES cheaper than Instantly or Smartlead? The sending cost is cheaper, $0.10 per 1,000 emails versus tiered platform pricing, but you pay separately for whatever campaign tool sits on top of SES.

Which tools connect directly to my own AWS SES account? EmailQo and Mailforge both connect to a user's own SES account. Instantly and Smartlead manage their own sending infrastructure instead.

Does using my own AWS SES account improve deliverability? It removes the shared-pool risk, where another user's bad sending behavior on the same platform can affect your inbox placement. It does not automatically guarantee better deliverability; you still need proper authentication, warmup, and list hygiene.

Last updated July 2026.

Why Your First Cold Email Through Amazon SES Didn't Send

Wed, 15 Jul 2026 11:22:04 +0000

If you just set up Amazon SES to send cold email and your first test message never showed up, you didn't break anything. This happens to almost everyone. It's called the sandbox, and every new SES account starts inside it.

What the sandbox actually is

When you create a new Amazon SES account, AWS doesn't let you send freely right away. You're placed in a sandbox with three rules:

You can only send to email addresses you've manually verified in the SES console. You're capped at 200 messages in a 24 hour period. You can send at most 1 message per second.

For cold email, the verified addresses rule is the one that trips people up. Cold email means reaching people who haven't given you their address ahead of time. But the sandbox only lets you send to addresses you've already added and confirmed yourself. So your first real cold email, to a prospect who never verified anything with AWS, just won't go out. No dramatic error, it simply won't deliver.

Why AWS does this

This isn't AWS being difficult. New accounts with no sending history are the most common source of spam on any email platform. The sandbox is AWS's way of making sure new accounts prove they send legitimate mail with real bounce and complaint handling before they're allowed to send widely. It protects their own sending reputation, which in turn protects everyone using SES.

How to get out of it

You request production access from the SES console. Go to your Account Dashboard, then "Get set up," then "Request production access." AWS asks for a few specific things:

Your mail type, marketing or transactional. For cold email, marketing is usually the right answer. A website URL, so AWS can see that what you're describing matches what your site actually does. Up to four additional contact emails. Your preferred contact language. A checkbox confirming you only send to people who've asked to hear from you, and that you have a process for handling bounces and complaints.

AWS says they typically respond within 24 hours. Sometimes they'll ask a follow up question before approving, which adds time.

One thing worth doing before you even request access: verify a full domain, not just a single email address. AWS calls this out directly as something that helps your request move faster.

What changes once you're approved

The verified recipients restriction goes away, so you can send to anyone. The 200 message and 1 per second caps lift too, though your new limits start modest and rise automatically as you build a clean sending history with low bounces and complaints. You can request a higher limit directly once you need it.

One thing that doesn't change: you still have to verify whatever address or domain you're sending from. Production access removes the restriction on who you can send to, not the requirement to prove you own what you're sending from.

If you want the full walkthrough, from creating the AWS account through your first real campaign, EmailQo has a step by step guide for setting up cold email on Amazon SES.

Coder Legion - Recent posts tagged amazonses

AWS SES Cold Email Tools Compared (2026)

Why Your First Cold Email Through Amazon SES Didn't Send