Wraps

Wraps sets up email infrastructure inside your own AWS account with one CLI command, then hands you a TypeScript SDK to send through it. The middleman disappears: you pay AWS directly for sending, and if the project vanished tomorrow the pipeline it built would keep working.

A single init run provisions the whole stack, namespaced under a common prefix and tagged as managed by the CLI, so it stays obvious what belongs to Wraps. Sending afterwards is a few lines of typed code, with visual templates, analytics and a dashboard on top.

That one command creates the pieces an email pipeline needs.

• SES: domain verification with DKIM, SPF and DMARC records handled for you.
• EventBridge and SQS: bounces, opens, clicks and deliveries arrive as real-time events.
• DynamoDB: email event history is retained for a configurable window.
• Lambda: event processing and webhook handling run as functions in your account.
• IAM: least-privilege roles with OIDC support for Vercel and AWS native workloads.

SMS has its own CLI and SDK, and CDK and Pulumi packages cover infrastructure as code. Node 20 or newer plus configured AWS credentials are the only prerequisites. The code is AGPL-3.0 with enterprise features under a commercial license, and the project publishes an agent-readable documentation bundle for people working through Claude Code or Cursor.