coss.com vs Amazon SES
coss.com sends through Amazon SES. SES is the lower-level, lower-cost building block; coss.com adds what SES leaves to you.
| Feature | coss.com | Amazon SES |
|---|---|---|
| Pricing model | $0.40 per 1,000 recipients, lower at volume in graduated bands; paid plans from $25/month | $0.10 per 1,000 emails plus attachment data, or fixed monthly plans per region |
| Getting started | Free plan: 3,000 email recipients a month, 3,000 received emails a month and 3 inboxes; sandbox keys, and nothing leaves coss.com | A sandbox per region, verified recipients only, until production access is granted |
| Transactional email | REST API and an SMTP relay (smtp.coss.com), batch and scheduled sends, idempotency keys, templates with versions and locales | SES API v2 and an SMTP interface, templates, configuration sets |
| Marketing email | Contacts, audiences, segments, topics, double opt-in and broadcasts on their own stream | One contact list per account with up to 20 topics and subscription management; you list contacts and call SendEmail yourself |
| Receiving email | An address per environment, or your domain with an MX record; a webhook, then the API | Receipt rules deliver raw MIME to S3 (up to 40 MB) or SNS (up to 150 KB), or invoke Lambda; only in some regions |
| Multi-tenant sending | Sub-accounts on Scale and Enterprise, each with its own domains, reputation and quotas | Tenants with their own identities and reputation policies; up to 10,000 per account by default |
| Dedicated IPs | An add-on on Scale and Enterprise: Amazon SES managed dedicated IPs, warmed up automatically | Standard $24.95/month per IP; managed $15/month plus a per-email fee; bring your own IPs |
| Events | Standard Webhooks signatures, automatic retries, test events and coss listen to forward events to localhost | Event publishing through configuration sets to SNS, EventBridge, Firehose, CloudWatch or Pinpoint |
Which to choose
Both are good at what they do. Here is where each one fits better.
Lowest cost at volume
SES's per-email price is hard to beat when you have the engineers to build bounce handling, tracking, list management and dashboards yourself.
You're deep in AWS
IAM, KMS-encrypted receiving to S3, Lambda receipt rules, EventBridge, Mail Manager and bring-your-own IPs fit an AWS-native stack.
You need full control of the pipeline
With SES you choose every configuration set, event destination and receipt rule. coss.com makes those choices for you.
SES without the plumbing
coss.com keeps the suppression list, does its own open and click tracking, stores received email and turns SES events into signed webhooks and per-recipient statuses.
Marketing email you don't have to build
Contacts, audiences, segments, topics with a hosted preference center, one-click unsubscribe, double opt-in and broadcasts.
Tenants, managed
Every organization and every sub-account gets its own SES tenant, with coss.com's own reputation checks, quotas and suppressions on top.
Sandbox environments
Test against the same API with coss_test_ keys and a mailbox simulator, with nothing sent and no recipient to verify.
Moving from Amazon SES
- 1
Add and verify your domains
Add each domain in coss.com and publish its DKIM and MAIL FROM records. Your SES identities keep working until you switch.
Read the guide - 2
Bring over suppressions and contacts
Export your SES suppression list and contact list and import them with coss.email.suppressions.import and coss.email.contacts.import.
Read the guide - 3
Replace SendEmail and your event pipeline
Call coss.email.send() or use SMTP at smtp.coss.com, and replace SNS or EventBridge consumers with one webhook endpoint for coss.com's events.
Read the guide
Questions
Sources
Amazon SES's facts were checked on . Their pages are the final word on their prices and features.
The coss.com side
Try coss.com next to Amazon SES.
A development key costs nothing and delivers nothing, so you can compare with real code.