One command or package (CDK & Pulumi) deploys production email infra to your AWS account: `npx @wraps.dev/cli email init`
~30 seconds to configure SES, DKIM/SPF, event tracking, and sandbox exit. You own everything—we just provide the tooling.
Key decisions: - BYOC: Deploys to your AWS, you pay AWS directly for sending - Zero credentials stored: OIDC federation only - Open source CLI/SDK: MIT licensed, free forever - No lock-in: Send emails and SMS from YOUR AWS account.
Dashboard with templates/analytics/broadcasts/automations is $10-149/month, tiered around the number of custom events you send. CLI and SDK are free.
Tradeoffs: You need an AWS account. If you want zero AWS involvement, the managed services are solid. Happy to discuss architecture decisions or answer questions.
jeffatzeal•46m ago
stewartjarod•33m ago
Consider:
- Welcome series (signup → 3 emails over a week)
- Cart abandonment (wait for purchase, timeout → reminder)
- Re-engagement (segment-based triggers)
- Multi-channel flows (email + SMS in one workflow)
You can trigger on events, segment changes, or schedules. Use delays, conditions (branch on contact properties), and wait-for-event (pause until X happens or timeout). There's also an AI designer. You describe what you want in plain english, and it generates the workflow.