Infrastructure
Your entire SES setup, managed from one place
Domain identities, configuration sets, tracking domains, suppression lists, sending channels — SES has the building blocks, but they're spread across a dozen console pages with no obvious way to connect them. SendOps brings them into a single dashboard, provisioned automatically, and accessible to your whole team without AWS credentials.
The problem
SES is powerful infrastructure with a terrible control panel
Setting up SES properly means touching half a dozen AWS services. You need domain identities with DKIM and DMARC. Configuration sets with event destinations. Tracking domains pointed at the right endpoints. Suppression lists. IAM roles scoped to the right permissions. And all of this needs to be done before you send a single email.
The AWS console lets you do all of it — if you know where to look. Configuration sets are in one tab. Domain identities are in another. Tracking domains require DNS changes that the console can't verify for you. And if you have multiple environments — staging, production, different teams — you're repeating the setup for each one.
Most teams either build CloudFormation templates themselves or configure everything manually and hope nobody changes it. Both approaches work until someone needs to add a new domain, or a new team member needs access, or you realise you forgot to set up event destinations on one of your configuration sets six months ago.
Already on SES?
No migrations. No rip-and-replace. Just plug in.
If you're already sending with SES, you have domain identities, configuration sets, maybe tracking domains and suppression lists. That's your infrastructure — and it stays exactly where it is.
When you deploy the SendOps CloudFormation template, it connects to your existing SES setup. Your domains, your configuration sets, your sending reputation — nothing changes. What you gain is visibility: a dashboard that shows you everything in one place, metrics you've never had without CloudWatch, and the ability to hand that view to anyone on your team without giving them AWS credentials.
Then, when you're ready, layer on the rest: Git-based templates, sending channels, automated infrastructure management. There's no big-bang migration. You adopt what's useful at your own pace.
What stays the same
- Your SES account
- Your domains
- Your configuration sets
- Your sending reputation
- Your application code
What you gain immediately
- Unified dashboard
- Message search
- Delivery metrics
- Team access without AWS credentials
- Alerting
What you can add later
- Git-based templates
- Sending channels
- Infrastructure automation
- Tracking domains
0
minMinutes from signup to fully configured SES stack
0
CloudFormation template to set up everything
0
AWS console pages your team needs to visit
0
IAM credentials to hand out
What's included
One CloudFormation template. Everything configured.
When you connect your AWS account, SendOps deploys a single CloudFormation template that provisions your entire email infrastructure. Every resource is pre-configured, connected, and managed through the SendOps dashboard from that point forward.
Verified sending domains with DKIM signing and DMARC alignment configured automatically. Add a new domain in the dashboard — SendOps generates the DNS records and verifies them for you.
One configuration set per sending channel, with event destinations already wired. Every delivery, bounce, complaint, open, and click is captured automatically. No manual event destination setup.
Logical separation for different email types — transactional, marketing, notifications. Each channel has its own configuration set, its own quotas, and its own reputation. A bad marketing campaign doesn't take down your transactional email.
Custom tracking domains for opens and clicks, served from your own domain. No shared subdomains in your links. Better deliverability, better brand consistency.
Every SES event is routed to SendOps via EventBridge — automatically configured, no manual rule creation. This is how SendOps gets real-time visibility into your email flow without sitting in the delivery path.
Least-privilege IAM roles scoped to exactly what SendOps needs. No broad admin access. Provisioned by CloudFormation, auditable, and revocable at any time.
Account-level suppression managed in one place. Bounced addresses and complaint-generating recipients are automatically suppressed across all channels.
Before and after
What changes when SendOps manages your infrastructure
Today
Configure SES manually across multiple console pages
Set up event destinations by hand for each configuration set
Create IAM credentials for anyone who needs to manage email settings
Repeat the setup for staging, production, and every new environment
DNS changes for domain verification with no feedback until propagation completes
No clear picture of which domains, channels, and configuration sets are connected to what
With SendOps
One CloudFormation deploy, everything configured
Event routing pre-configured for every channel
Team members use the SendOps dashboard — no AWS credentials needed
Provision a new environment by deploying the same template
Dashboard shows DNS verification status in real time
Full infrastructure map in a single view — every resource and how they connect
Channels
Separate your email by type, team, and risk
Each channel gets its own configuration set, tracking, metrics, and reputation. Why this matters: a spike in marketing bounces won't touch your transactional deliverability. Bad campaigns can't take down password resets and order confirmations.
Transactional
Password resets, order confirmations, account alerts. High deliverability, low volume, zero tolerance for delays.
~500
Sends/day
0.1%
Bounce rate
0.0%
Complaint rate
Marketing
Campaigns, newsletters, promotions. Higher volume, higher bounce tolerance, separate reputation from transactional.
~12k
Sends/day
1.2%
Bounce rate
0.05%
Complaint rate
Notifications
System alerts, usage reports, billing reminders. Internal or semi-internal, different tracking and suppression rules.
~200
Sends/day
0.3%
Bounce rate
0.0%
Complaint rate
Infrastructure everyone can manage — with controls only engineering can change
SES infrastructure is usually engineering's problem because the AWS console is the only way to manage it. SendOps moves day-to-day operations into a dashboard the whole team can use, while keeping provisioning and permissions under engineering's control.
For Developers
Infrastructure is provisioned via CloudFormation — review it, version it, deploy it like everything else. The API covers everything the dashboard does, so you can plug infrastructure management into your CI/CD pipeline.
For Marketing
See which domains are verified, which channels are active, and what tracking domains are in use — no AWS access needed. Request changes through the dashboard; engineering approves, SendOps provisions.
For Operations
One view of every SES resource: domains, configuration sets, channels, suppression lists. Know what's configured, what's connected, and what's changed — without digging through CloudFormation outputs.
Setup
Two minutes to get started — whether you're new to SES or not
Deploy the CloudFormation template
Click the link in the SendOps dashboard. It opens the CloudFormation console with the template pre-filled. Review the resources, click deploy. Takes about 90 seconds.
Done.
SendOps picks up your existing domains, configuration sets, and sending reputation automatically. Your dashboard is live. Metrics, message search, and alerting work immediately — no domain verification, no DNS changes, no reconfiguration.
Optional next steps
- Set up sending channels to separate transactional from marketing
- Connect your template repository for Git-based deployment
- Invite team members to the dashboard
Set up your SES infrastructure in two minutes, not two sprints
Free plan available. Connects to your SES account with a single CloudFormation template.