Comparison

SES is the engine. Truncus is the car.

Amazon SES gives you raw email sending at scale. Truncus gives you managed email infrastructure — failover, guarantees, governance, and a dashboard — without touching the AWS Console.

Truncus actually uses SES under the hood (eu-west-1 Ireland) as its primary provider, plus Brevo France as automatic failover. You get SES pricing benefits without SES management overhead.

What you don't have to build

With raw SES, you build and maintain all of this yourself. With Truncus, it's included.

Bounce handling

Automatic suppression list, no SNS/Lambda wiring

Retry queue

Durable retries with exponential backoff and dead letter

Failover routing

Circuit breaker switches to Brevo on SES failure

Delivery confirmation

Synchronous send_sync instead of async SNS

Reputation monitoring

Auto-throttle on high bounce/complaint rates

Deduplication

Content-based dedup prevents double sends

Feature comparison

Side-by-side comparison of managed Truncus vs raw Amazon SES. Where we don't have a feature, we say so.

FeatureTruncusAmazon SES
Setup complexity
Sign up, get API key, send
AWS account, IAM, SES sandbox exit, SNS topics
AWS account required
No
Yes
Data residency
EU default (Ireland + France)
Choose region (US default)
Multi-provider failover
SES Ireland + Brevo France (circuit breaker)
Single provider (SES only)
Delivery guarantees
best_effort / at_least_once / exactly_once
Best effort only
Synchronous delivery confirmation
Yes (send_sync — ~1s)
No (async SNS notifications)
Operations API (durable sends)
Yes
No
Pre-send validation
Confidence score, spam check, domain health
No
Bounce/complaint management
Automatic suppression + reputation engine
Manual (SNS → Lambda → your code)
Retry queue
Durable (30s/2m/8m/30m/2h) + dead letter
Build your own
Kill switch
Instant send suspension via API
Disable SES manually in console
Content-based deduplication
Automatic (10-min window)
Build your own
Stream isolation
Isolated transactional + outreach streams
Configuration sets (manual)
Dashboard
Logs, domains, API keys, usage
AWS Console (shared with 200+ services)
MCP server
197 tools (npm)
No
CLI
@vanmoose/truncus-cli
AWS CLI (generic)
Pricing model
$19/mo flat (50K emails)
~$0.10/1,000 emails (pay-per-use)
Free tier
3,000 emails/mo (forever)
3,000/mo (from EC2 only, 12 months)

Comparison based on publicly available information as of April 2026. Amazon SES is a trademark of Amazon.com, Inc.

When to choose Truncus

Truncus is the right pick when:

  • You don't want to manage AWS infrastructure for email
  • You need multi-provider failover — not just SES alone
  • You want EU data residency without region configuration
  • You need delivery guarantees beyond best-effort
  • You want bounce handling and retry queues out of the box
  • You're building AI agents that send email autonomously

When to choose SES

Amazon SES is the better choice when:

  • You need the absolute lowest cost per email at high volume
  • Your team has deep AWS expertise and existing infrastructure
  • You want full control over every aspect of email delivery
  • You're already sending millions of emails and have built your own tooling

Try Truncus free — 3,000 emails/month

No AWS account required. No IAM configuration. No SNS topics. Sign up, get your API key, and start sending in under a minute.

Create free account

Free tier includes 3,000 emails/month and 1 sending domain.

Truncus vs Amazon SES — Managed Email, No AWS