Amazon SES vs Bulko: SMTP Relay Pricing and Features Compared (2026)

Amazon SES is much cheaper per email ($0.10 per 1,000 on its à la carte pricing, so 20,000 emails cost about $2) and is the right choice if you already run on AWS and are comfortable with IAM, regions and the sandbox review. Bulko costs more per email ($15 for 20,000, paid once) but skips the AWS account, the sandbox and the production access request, accepts crypto, and gives you working SMTP credentials right after payment.

This is not a close race on price, and we will not pretend it is. The real question is whether the AWS setup and billing model fit you. Figures below come from the official SES pricing page and AWS documentation, checked in October 2026.

Quick comparison

Pricing

SES now has two ways to pay for outbound email. À la carte pricing is $0.10 per 1,000 emails with no minimum. Plans are tiered: Essentials is $0.16 per 1,000 for the first 10 million emails a month with no account fee, while Pro ($0.22 per 1,000) and Enterprise ($0.23 per 1,000) add a fee of $105 and $500 per account, per region, per month. According to the pricing page, new accounts start on Essentials from July 21, 2026 and can switch to à la carte at any time. Attachments add $0.12 per GB, and a standard dedicated IP is $24.95 per month.

SES wins on unit price at every volume, before attachment data. If price per email is your only criterion and you can get production access, use SES. Bulko's case is about the rest of the experience: a fixed, prepaid cost, no cloud account, and no review step before your first real email. Bulko's default limit is 2,000 emails per day per SMTP account, which support can raise on request.

Prices checked October 2026, see the Amazon SES pricing page for current rates in your region.

Setup and deliverability

Every new SES account starts in the SES sandbox, separately in each AWS region. In the sandbox you can only send to verified addresses and domains, at most 200 messages per 24 hours and 1 message per second. To leave it, you submit a production access request describing your use case, website and how you handle bounces and complaints. AWS says it gives an initial response within 24 hours, and may ask for more information before deciding. Even in production you must verify every identity you use as From, Sender or Return-Path.

SMTP access also takes a few steps: SES SMTP credentials are created through IAM, they differ from your AWS secret access key, and they are unique to each region. The SMTP endpoint has the form email-smtp.<region>.amazonaws.com. Bounce and complaint handling is your job, usually through SNS notifications.

Bulko works differently. There is no account review before you can send: you pay for a package and the SMTP credentials are shown in the dashboard and emailed to you immediately. You can send from any address on a domain you control. Verifying the domain is optional but recommended: Bulko gives you a DKIM TXT record (selector bk1) and a CNAME bnc.yourdomain.com for the return path, which lets SPF, DKIM and DMARC align. Without verification, mail still sends.

Mail goes out through Bulko's own MTA, which throttles warm-up per mailbox provider, processes bounces and monitors blocklists. Every message also passes an AI content filter (rules plus AI) that looks for phishing, malware, brand impersonation and scams. Messages that fail are rejected with 554 5.7.1 and are not delivered, so you see the problem immediately instead of finding it later in a reputation report. The default limit is 2,000 emails per day per SMTP account, and [email protected] can raise it on request.

No provider can promise inbox placement, and Bulko does not publish delivery-rate numbers. What decides the result is the same everywhere: authenticated domains, clean lists and content people asked for. The SPF, DKIM and DMARC setup guide and the blacklist checker help with the first two.

For a deeper SES walkthrough, see how to use Amazon SES for email marketing.

When Amazon SES is the better choice

• Price per email matters most. At $0.10 to $0.16 per 1,000, SES is several times cheaper than Bulko at every volume.
• You already live in AWS. SES fits with IAM, SNS, Lambda and CloudWatch, and the bill lands on the account you already pay.
• You need an API and event data. SES has an HTTP API, SDKs, configuration sets and event publishing. Bulko SMTP Relay is SMTP only, without webhooks.
• You need receiving, dedicated IPs or deliverability tooling. SES offers inbound processing, standard and managed dedicated IPs and the Virtual Deliverability Manager. Bulko offers none of these.
• You send millions of emails and want volume tiers down to $0.11 per 1,000 on plans.

When Bulko is the better choice

• You do not want an AWS account. No IAM users, no regions, no sandbox, no production access form.
• You want a fixed cost. A Bulko package is prepaid, so spending cannot grow past what you bought. Unused emails never expire, and an unused package can be refunded within 14 days.
• You want to pay with crypto. Bulko accepts USDT, BTC and other coins as well as Visa and Mastercard. AWS does not list crypto among its payment methods.
• You need to send today. Credentials arrive right after payment, so a new project can send without waiting for a review.
• Your software only needs SMTP. Any plugin, CRM or server that accepts host, port, username and password works.

See also the cheapest SMTP relay services in 2026.

How to switch to Bulko SMTP

1. Buy a package on the Bulko SMTP Relay page with a card or crypto. Your SMTP username and password appear in Dashboard > SMTP Access and are also emailed to you right after payment.
2. In your app, plugin or server config, replace the SES endpoint (email-smtp.<region>.amazonaws.com) with smtp.bulko.io.
3. Pick a port: 587 with STARTTLS (many apps label it "TLS"), 465 with implicit SSL/TLS (often labeled "SSL"), or 2525 with STARTTLS if your hosting provider blocks 587 and 465. Port 25 is not offered for submission.
4. Paste the Bulko username (it looks like smtp_xxxxxxxxxxxxxxxx) and password into the SMTP username and password fields. Authentication is AUTH LOGIN or PLAIN, which every common SMTP library supports.
5. Use a From address on a domain you control. Optionally verify the domain under Sending Domains: Bulko gives you a DKIM TXT record (selector bk1) and a CNAME bnc.yourdomain.com for the return path, so SPF, DKIM and DMARC align.
6. Send a test message before moving all traffic. A 535 reply means the credentials are wrong; see SMTP error 535.

SMTP host: smtp.bulko.io
Port: 587 (STARTTLS) or 465 (SSL/TLS) or 2525 (STARTTLS)
Username: smtp_xxxxxxxxxxxxxxxx
Password: from Dashboard > SMTP Access

If you are unsure which port your software expects, the SMTP ports guide explains the difference between 465, 587 and 2525.

FAQ

Is Amazon SES cheaper than Bulko?

Yes. SES costs $0.10 per 1,000 emails on à la carte pricing ($0.16 on the default Essentials plan), so 20,000 emails cost $2 to $3.20, against $15 for Bulko's 20K package. Bulko is chosen for simpler setup, prepaid billing and crypto payment, not for a lower unit price.

What are the Amazon SES sandbox limits?

In the sandbox you can only send to verified addresses or domains, up to 200 messages per 24 hours and 1 message per second. You leave it by submitting a production access request, which AWS reviews.

Does Bulko have a sandbox or approval step?

No approval step before sending. Every message does pass Bulko's AI content filter, which rejects phishing, malware, impersonation and scams with a 554 5.7.1 error, and use must follow the acceptable use policy.

Does SES still have a free tier?

New AWS customers receive up to $200 in Free Tier credits that can be used on eligible services, including SES. Bulko has no free SMTP trial.

Can I use the same SMTP code for SES and Bulko?

Yes, if your code uses SMTP. Change the host to smtp.bulko.io, keep port 587 or 465, and replace the SES SMTP username and password with your Bulko credentials.