Skip to content
Compare

Comparison · Updated

Stamp0 vs the Amazon SES console: same SES, none of the plumbing

Amazon SES is the cheapest reliable way to send email. It is also a kit of parts: you wire up DNS, configuration sets, SNS or EventBridge, storage for inbound mail, and your own dashboards. Stamp0 is that wiring, done once, with an API and a UI on top.

Side by side

SES console compared with Stamp0
TaskSES consoleStamp0
Domain setupCopy DKIM CNAMEs and MAIL FROM records into your DNS by handRecords applied on Route 53 (other DNS: a copy-paste list), then polled until verified
Delivery eventsConfiguration set, event destination, SNS or EventBridge, plus your own consumerCreated by the stack and streamed into a searchable activity log
Looking up one emailNo message history in the consoleTimeline per email: queued, sent, delivered, opened, bounced
Inbound mailReceipt rule sets, an S3 action, and your own parserInboxes, threads and messages over an API
Bounce and complaint healthAccount-level reputation metricsPer domain and per project, against SES review thresholds
Sandbox exitA form, then waitingGuided checklist so the request is ready to approve
APISES v2 API (AWS SigV4)Resend-compatible REST API with API keys
AgentsSample MCP server that wraps raw API callsRemote MCP with task-level tools

What the setup actually involves

Getting SES production-ready from the console takes a list of steps that each live in a different part of AWS:

  1. Create a domain identity and publish three DKIM CNAME records.
  2. Configure a custom MAIL FROM domain (MX and SPF TXT) for alignment.
  3. Publish a DMARC record.
  4. Create a configuration set and an event destination, then something to consume the events and store them.
  5. Set up receipt rules, an S3 bucket and a parser if you receive mail.
  6. Request production access to leave the sandbox.

Stamp0 does steps 1 to 5 from one CloudFormation Quick Create link and a domain name, and prepares step 6.

Cost

You keep paying AWS for SES exactly as before. Stamp0 adds a flat monthly price, free up to 50,000 emails a month, and its stack costs about $0.40 a month in your account. Because Stamp0 provides deliverability insights, most teams can use SES à la carte at $0.10 per 1,000 rather than the Essentials plan at $0.16; see SES pricing explained.

You stay in control

Everything Stamp0 creates is a normal AWS resource in your account, tagged and visible in the console. Delete the CloudFormation stack and Stamp0 loses access; your identities, suppression list and sending reputation remain yours.

Frequently asked

01

Does Stamp0 replace Amazon SES?

No. Stamp0 runs on top of SES in your own account. SES still sends and receives every email and AWS still bills you for it; Stamp0 replaces the console, the setup work and the glue code around it.
02

Can I keep using the SES API directly?

Yes. Stamp0 only adds a configuration set, an event destination, a bucket and receipt rules through its CloudFormation stack. Code that already calls SES keeps working, and you can move it to the Stamp0 API at your own pace.
03

What does Stamp0 need access to?

A cross-account IAM role with an external ID that allows SES actions, access to the bucket the stack creates, and EventBridge. It cannot read other buckets or touch other services, and you can delete the stack at any time to revoke it.

Send through SES without the SES console.

Resend-compatible API, automatic DNS and an event log, on your own AWS account.