# Why Wraps — the evaluation guide you can forward Source: https://wraps.dev/why-wraps ![Wraps Logo](https://wraps.dev/wraps-light-logo.png)![Wraps Logo](https://wraps.dev/wraps-dark-logo.png) ](https://wraps.dev/) [](https://github.com/wraps-team/wraps)[Log in](https://app.wraps.dev/auth?mode=signin)[Sign up](https://app.wraps.dev/auth?mode=signup) Toggle menu Wraps · Evaluation guide Written to be forwarded. If you are the person being asked to approve this, the sections below are the risk it reduces, what it costs in total, what happens to your infrastructure if we disappear, and the questions your review will raise — including the ones where our answer is no. Copy link to share 01 ## What you are actually buying down Not a cheaper send. The failure mode that costs a company real money is Amazon switching the account off, and every number in the second column is AWS's, not ours. | Risk | AWS's line | What Wraps does | What it cannot do | | --- | --- | --- | --- | | Bounce rate climbs | AWS can open a manual review above 5% and pause sending at 10% | Bounces are suppressed on the way in from the first send. The rate is drawn against both lines on the dashboard and swept hourly. | Reverse a pause AWS has already applied. | | Complaint rate climbs | Review above 0.1%, sending can be paused at 0.5% | Complaints feed the same suppression path, and the rate carries the same two lines and the same hourly sweep. | Stop recipients marking mail as spam. | | The account cannot send at all | New accounts reach verified recipients only, until AWS approves | Sandbox is detected at the end of a deploy and explained, with the request linked, rather than discovered from a failed send. | Approve the request. Only AWS can, from your account. | | The daily quota runs out mid-campaign | AWS sets a rolling 24-hour send quota per account | Usage is shown against the quota with a warning line at 80%. | Raise the quota. | | Domain authentication drifts and mail lands in spam | No AWS alert — you find out from a customer | An on-demand audit covers DKIM, SPF, DMARC, MX and TLS, BIMI, and public blacklists. | Guarantee inbox placement. Nobody can. | 02 ## What it costs, all in Two lines on two invoices. A flat platform fee from us, and AWS billing you directly for the sending at **$0.10 per 1,000 emails** on à la carte, or $0.16 on the Essentials plan new AWS accounts default to. There is no per-seat, per-contact or per-send meter on any tier. Free$0 One AWS account, 30 days of history. Most first deploys. Pro$29/mo One AWS account, 90 days of history, email support. Business$199/mo Unlimited AWS accounts, 365 days of history, SSO and SCIM, audit log with CSV export, priority SLA. Where the money actually moves: against a contact-priced marketing platform the gap is large immediately and widens with the list. Against a hosted sending API it is small under roughly 100,000 emails a month and grows from there. Either way the platform fee stays flat while theirs scales, which is the part that compounds. 03 ## What happens if Wraps goes away The question a careful reviewer asks about any vendor in the send path. Here it has a mechanical answer rather than a reassuring one. ### The infrastructure is already yours SES identities, Lambdas, EventBridge rules and DynamoDB tables are created in your AWS account, namespaced wraps-email-\*, and none of them call us to keep working. Stop paying and mail keeps sending. ### Our access is a role you delete Wraps assumes an IAM role with an external ID. No access keys exist on our side, so revoking access is a change you make in your own account without involving us. ### The code outlives the company The platform is AGPL-3.0, with an enterprise kernel under a separate licence, and the SDKs are MIT. If Wraps disappears, the thing you deployed is still a fork you can run. ### What you would lose, stated plainly The dashboard, and everything that lives in our database rather than yours: contacts, templates, broadcasts, workflows, and the per-message send records that drive the dashboard list and analytics. Export them before you go. The SES infrastructure and the event history in your own DynamoDB stay where they are. ## Questions your team will ask The answers we would give in the room, in the words we would use. ### Are you SOC 2 certified? ### Will we get stuck in the SES sandbox? ### Where does our data actually live? ### What access does Wraps have to our AWS account? ### What is the support commitment? ### What happens if we stop paying, or you go away? ### Isn't this just a wrapper around SES? There are free ones. ### How disruptive is the migration? 05 ## When the answer is no If one of these describes your team, a decision against Wraps is the correct one, and this page is a faster way to reach it than a trial. - You have no AWS account and no appetite for one. Everything on this page depends on holding one, so a hosted sending API is the right shape for you. - Your review requires SOC 2, HIPAA or a BAA today. We have none of them. - You expect to be refused SES production access. Wraps cannot change that outcome, and a sandboxed account sends to nobody. - Your stack is not TypeScript or Python. Those are the SDKs that exist. - A non-engineer needs to own email day to day. A marketing platform will fit their hands better than ours will. - You are shopping purely on price below about 100,000 emails a month. The gap at that volume is small enough that it should not be the deciding factor. Still deciding which category you belong in? [The four approaches](https://wraps.dev/approaches) lays out every option, including the ones that are not us. ## Try it against a real AWS account One command, about two minutes, non-destructive. Nothing existing in the account is modified, so a trial deploy is reversible. [Read the quickstart](https://wraps.dev/docs/quickstart/email)