What happens if my bounce or complaint rate crosses an AWS threshold?

Wraps sweeps your SES reputation metrics hourly. Past AWS's review line (5% bounce, 0.1% complaint), owners and admins are notified. At the pause line (10% bounce, 0.5% complaint), scheduled broadcasts are held instead of queueing behind a paused account. Bounces and complaints are also suppressed automatically to keep rates down.

Is Wraps open source?

Yes. Wraps is licensed under AGPL-3.0, and the code is available on GitHub so you can review what touches your AWS account before it does.

Can Wraps get me SES production access (out of the sandbox)?

No. Wraps is explicit that nobody in its category can grant SES production access — it's an AWS decision made from your own account. Wraps detects the sandbox and explains it, but that's the extent of what anyone can do.

Can I try it without installing anything?

Yes. Run `npx @wraps.dev/cli email check yourdomain.com` to audit a domain's SPF, DKIM, DMARC, MX, TLS, BIMI, and blacklist status. It reads public DNS records and blacklists only — nothing is deployed and no AWS account is needed.

Wraps — The email platform for Amazon SES

Wraps is an operations layer for Amazon SES that deploys a complete email sending stack directly into your own AWS account with one command. Instead of routing mail through a third-party service, Wraps stands up SES, DynamoDB, Lambda, and EventBridge in your account, then monitors bounce and complaint rates against AWS's own review and suspension thresholds, audits deliverability (SPF, DKIM, DMARC, MX, TLS, BIMI, blacklists), and handles suppression, templates, workflows, broadcasts, and analytics. Your sending costs go straight to AWS, and the code is open source (AGPL-3.0).

Key Features

Account survival monitoring

Tracks bounce and complaint rates against AWS's review lines (5% bounce, 0.1% complaint) and pause lines (10% bounce, 0.5% complaint), sweeping SES reputation metrics hourly and notifying owners and admins before an account gets paused. Scheduled broadcasts are held at the pause line instead of queu

One-command infrastructure deploy

Running `npx @wraps.dev/cli email init` stands up SES, DynamoDB, Lambda, EventBridge, and scoped IAM roles in your AWS account in about two minutes. Every resource is new and prefixed with wraps-email-, leaving existing account resources untouched.

Deliverability audit

A single command checks DKIM, SPF, DMARC, MX records, mail server TLS, BIMI, and 50+ public blacklists, then outputs a scored report with a fix list. A standalone `email check` command works on any domain with no deployment or AWS account required.

Automatic bounce and complaint suppression

Bounces and complaints are suppressed at the account level from the first send, putting a floor under your rates rather than just reporting them. Suppression is browsable and clearable in the dashboard, and every message has an event log.

Event data you own

Sends, deliveries, opens, and clicks stream into a DynamoDB table (wraps-email-history) in your own account. Query the data yourself or view it in the Wraps dashboard.

TypeScript-first SDK with templates as code

A typed SDK (email.send()) with type inference for React-based templates and workflows. Templates and workflows live in your repo, so a bad send can be rolled back in a pull request. The SDK talks directly to SES, and can be swapped for the AWS SDK, boto3, or plain SMTP with events still landing.

Broadcasts, segments, and workflows

Compose once and send to thousands via broadcasts, with audience segments and automated workflows managed through the dashboard or code.

Agent-friendly

Everything is TypeScript, so AI agents can write templates and open PRs alongside your team, shipping through the same pipeline.

How It Works

Deploy the stack into your AWS account

Run `npx @wraps.dev/cli email init` to deploy SES configuration, DynamoDB, Lambda, and EventBridge into your AWS account in about two minutes.

Send from your app

Use the TypeScript SDK (email.send()) or the AWS SDK, boto3, or plain SMTP. Wraps binds a configuration set to the domain identity so events land regardless of how you send.

Events are processed in your account

SES events are caught by an EventBridge rule, processed by a Lambda function, and written to a wraps-email-history DynamoDB table you own. The same event streams to Wraps to power suppression and analytics.

Wraps monitors and audits

Hourly, Wraps assumes a revocable IAM role to read your SES reputation metrics. When rates cross AWS review lines it notifies owners and admins, and the deliverability audit diagnoses what's behind rate climbs.

Pros & Cons

Pros

Monitors bounce and complaint rates against AWS's actual review and pause thresholds with hourly sweeps and alerts, going beyond what typical SES wrappers do
All infrastructure and email event data live in your own AWS account — no vendor lock-in; if you stop paying, the infrastructure keeps sending
No AWS credentials stored; access is through an IAM role you create and can revoke
Proactive account-level suppression of bounces and complaints, not just webhook reporting
Comprehensive deliverability auditing (SPF, DKIM, DMARC, MX, TLS, BIMI, 50+ blacklists) with a free standalone domain check command

Who It's For

Best for

Developers and engineering teams already on AWS who want SES without the operational risk of account suspension
Teams that want email templates and workflows as code, reviewable in pull requests and shippable by AI agents
Startups that want ownership of their sending reputation, data, and infrastructure instead of renting a sending API
Cost-conscious teams for whom AWS's ~$0.10–$0.16 per 1,000 emails plus a flat platform fee beats contact-based pricing of marketing platform

Not ideal for

Teams with no AWS account and no willingness to hold one — a hosted sending API like Resend, Postmark, SendGrid, or Mailgun is a better fit

Use Cases

Teams running application email on Amazon SES who want to avoid AWS suspending their account over bounce or complaint rates

Engineering teams that want templates, workflows, and email infrastructure as reviewable code in their repository

Startups and indie hackers who want a Resend/Postmark-style developer experience but with their own AWS reputation and data

Organizations building AI agent-driven email pipelines, since agents can ship TypeScript templates and PRs

Anyone who wants email event data (sends, opens, clicks, bounces) stored in their own DynamoDB rather than a vendor's database

Pricing

Free forever plan to start (no credit card), with paid Pro and Business tiers. All plans include unlimited sends, domains, contacts, templates, and team members. AWS sending and infrastructure costs are billed separately and paid directly to AWS.

Free

Try the platform with your AWS account. Unlimited sends, domains & contacts, unlimited team members, 5,000 custom events/mo, 1 AWS account, 2 workflows, 30-day history. You pay AWS directly for sending.

Pro

$29/month

For indie hackers and side projects. Everything in Free, plus unlimited workflows, unlimited custom events, topics, segments, batch & campaigns, 250 AI generations/mo, 90-day history.

Business

$199/month

For scaling companies. Everything in Pro, plus unlimited AWS accounts, 1,000 AI generations/mo, 1-year history, SSO + SCIM, audit log + CSV export, and priority support.

Enterprise

Custom

Custom limits or on-prem deployment — contact the team.

FAQ

What does Wraps actually deploy and where does it run?

Running `npx @wraps.dev/cli email init` deploys SES, DynamoDB, Lambda, EventBridge, and scoped IAM roles into your own AWS account in about two minutes. Everything is prefixed wraps-email- and nothing existing in your account is touched. Your email sends through your AWS account, not through Wraps.

How is Wraps different from using AWS SES directly?

Raw SES gives you sending but nothing else — you'd build event tracking, bounce handling, suppression, templates, workflows, and monitoring yourself. Wraps deploys that entire operational layer into your account, and critically, it watches your bounce and complaint rates against AWS's review and pause lines hourly so your account doesn't get suspended without warning.

Does Wraps store my AWS credentials?

No. Wraps accesses your account through an IAM role that you create and can revoke at any time. The site states that zero credentials are stored.

What are the total costs?

Wraps