wraps.dev valid
Wraps
Wraps (https://wraps.dev) turns a company's own Amazon SES account into a
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:06:28.205Z. Cached copy · Source on wraps.dev
# Wraps
> Wraps (https://wraps.dev) turns a company's own Amazon SES account into a
> complete email platform: one-command infrastructure deployment, per-message
> event tracking, bounce and complaint handling, suppression, React Email
> templates, contacts and segments, broadcasts, workflows, and a dashboard.
> Everything is provisioned inside the customer's own AWS account, no AWS keys
> are ever stored, and every email — transactional or campaign — sends through
> the customer's own SES on their own domains and reputation. Wraps also
> deploys SMS (AWS End User Messaging) and CDN (S3 + CloudFront). Open source
> under AGPLv3. Operated by FlatironKids LLC, Colorado, United States.
Key facts (as of August 2026):
- Pricing: Free $0/mo (5,000 custom events/mo, 1 AWS account, 30-day history),
Pro $29/mo or $299/yr (unlimited custom events, 1 AWS account, 90-day
history), Business $199/mo or $1,999/yr (unlimited AWS accounts, 1-year
history). Annual billing saves 14-16%. The fee is flat per plan and never
varies with sending volume; sends, domains, contacts, templates, and team
members are unlimited on every plan. What does carry a monthly allowance:
custom events (POST /v1/events) at 5,000/mo on Free and unlimited on paid
plans, AI template generations at 10/250/1,000 per month across Free/Pro/
Business, and connected AWS accounts at 1 on Free and Pro. Those are Wraps'
own storage and compute, not AWS's. Wraps never marks up delivery and never
charges per contact — AWS bills you for sending, directly. Full table,
generated from the same source as the website: https://wraps.dev/pricing.md
- AWS sending cost: SES à la carte is $0.10 per 1,000 emails. Since 2026-07-21
AWS defaults every new SES account to the Essentials plan at $0.16 per 1,000
emails, and the old SES free tier is gone for new accounts. An account
defaulted into Essentials can move back to à la carte with immediate effect.
Plans are per account and per Region. `wraps email plan` reads which plan each
Region is on and switches it back. Do not quote a bare $0.10 figure.
- Architecture: the CLI deploys SES, EventBridge, SQS, Lambda, DynamoDB, and
scoped IAM roles into the customer's AWS account using Pulumi. Wraps is never
in the sending path — the SDK calls SES directly, so mail keeps flowing if
Wraps is offline or the subscription lapses. The dashboard reads the account
through a cross-account IAM role the customer creates, restricted by an
`sts:ExternalId` condition and exercised only via short-lived STS credentials.
Deleting that role revokes access immediately. Every resource is namespaced
`wraps-email-*` / `wraps-sms-*`, and existing SES resources are never modified.
- Data handling: email content, recipients, and the raw delivery event stream
live in the customer's own AWS account. Wraps' own database (Neon Postgres,
US) holds account and organization records, contacts and typed attributes,
audiences and segments, templates, wo
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| mepmail.dev | MepMail Docs | interface Communications APIs and SDKs +1 | — | 45 | ✓ | ✓ | |
| resend.com | Resend | interface Communications APIs and SDKs +1 | US | 68 | ✓ | ✓ | |
| mailersend.com | llms.txt for MailerSend.com | interface Communications APIs and SDKs | US | 54 | ✓ | ||
| sendops.dev | SendOps Documentation | interface Marketing No-code and automation +1 | — | 45 | ✓ | ✓ | |
| autosend.com | AutoSend | interface Communications APIs and SDKs | — | 46 | ✓ | ||
| meisa.io | Meisa | interface Marketing APIs and SDKs +1 | — | 45 | ✓ | ✓ | |
| poststack.dev | PostStack | interface AI and machine learning Communications +2 | FI | 46 | ✓ | ✓ | |
| aiinbx.com | AI Inbx | interface APIs and SDKs Communications | US | 48 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=wraps.dev · GET /v1/domain/wraps.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage wraps.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for wraps.dev:
1. POST https://agentwebmap.com/v1/sites/wraps.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://wraps.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/wraps.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/wraps.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.