Drip campaigns on your own Amazon SES
Email workflows that move customers forward.
Turn signups into customers with automated onboarding, cart recovery, and follow-ups. Build visually or with your AI agent. Send through Amazon SES in the AWS account you own.
Flat pricing. No success tax.
No per-contact or per-email SendOps charges. AWS usage billed separately.
Visual for your team. Readable by your agents.
Readable workflows you can version, review, and trace in Git.
Your AWS SES. Your control.
Low-cost delivery alongside your existing transactional email.
Start free. Connect your AWS account. Build your first workflow.
Not using drip campaigns? See what else SendOps can do.
One workflow. More possibilities.
Every next step, considered
The right follow-up starts with what they do.
A welcome series is only the start. Give every customer a path that adapts as they explore, convert, and come back. Combine email with webhook steps for SMS, push notifications, and actions in your own systems.
Journey explorer
Select any step
Meet them at their first milestone.
Wait for a first project, not just the clock. Celebrate progress, or offer help when the deadline passes. Finish with the right contact context.
Behavioral wait · Timeout path · Contact updates
Exit if the account closesChecked throughout the journey.
Project created
2 days, no project
The project-created signal comes from your app. A timed wait resumes when the condition is met or its deadline expires.
Welcome them aboard
A personalized template sent through your Amazon SES. Marketing topic preferences and your email frequency cap are checked before sending.
Your first small win starts here
lily@yourcompany.com
to Marcus
Hi, Marcus. Let’s get your first project up and running. Start with one thing, and we’ll help with the rest.
Create your first projectBuilt for the way you work
A workflow your team can see. A language your agents can read.
SendFlow turns your email journey into readable, versionable code. Let your agent build it, review the diff, and trace every change. The visual canvas keeps the same workflow open to the whole team.
Visual canvas, SendFlow source, API, or MCP. Your team works on the same workflow, whichever way they build.
Start with a signal
A signup, product event, segment change, or important date starts the conversation.
Respond with relevance
Personalize the message and choose the next step using what you know about each person.
Know when to stop
Exit on conversion, respect unsubscribes, and cap how often each contact hears from you.
Google Tag Manager integration
They came back. Give the moment a next step.
A second visit to pricing. A return to an abandoned cart. Connect website activity to email workflows that pick up the conversation, even without a fresh sign-in.
Recognize a contact you already know, check whether they converted, and start the right follow-up. Combine Google Tag Manager visit signals with cart, order, and product activity.
- 01A recognized contact returns to your site
- 02Google Tag Manager records the visit; your entry conditions match
- 03The workflow follows up and exits on conversion
Build visually. Go further when you want.
Your team’s workflow. Everyone’s way of working.
Build and edit your journey on the visual canvas, with no code required. When a developer or AI agent joins in, SendFlow gives them a readable version of that same workflow. Everyone stays part of the process.
More ways to work, when you want them.
Every visual workflow has a readable SendFlow definition. It gives your developers and agents another way to work on the same journey.
- Let your agent help
- Ask it to draft a journey or suggest a change. Your team can review the result on the visual canvas.
- Keep a history you can follow
- SendOps keeps version history. If your team uses Git, keep the definition there too, review changes, and trace how the journey evolved.
From account to automation
Connect once. Build what happens next.
Your AWS account is the starting point. Your customer journey is the destination.
- 01
Connect your AWS account
Use a guided, keyless connection to set up or connect SES. Verify your sending domain and get ready for production sending.
Explore the setup - 02
Bring your audience to life
Connect contacts and product activity. Choose who enters, what they receive, and when the journey should end.
Meet your audience - 03
Rehearse. Launch. Learn.
Test your workflow in shadow mode, review the emails, then activate. Follow each contact’s progress and improve the next version.
Build your first workflow
Room to grow
One flat fee. No success tax.
Build more workflows. Reach more customers. SendOps charges a flat subscription, with no per-contact fees and no per-email charge from us. AWS bills SES delivery separately at its low usage rates.
Your audience grows
Additional SendOps fees for storing more contacts
$0Free, Team at $29/month, or Business at $149/month. Your SendOps fee stays flat; AWS bills delivery separately.
Calculate your costsPowered by your Amazon SES
Ambitious workflows. Proven delivery.
Send from your own AWS account, alongside the transactional emails your product already sends. Keep the infrastructure, reputation, and sending costs under your control.
Your delivery foundation
Connect SES with a keyless AWS role. Manage domains, authentication, channels, and delivery health in SendOps.
Your transactional sending stays independent
Your application keeps sending directly through SES, independently of SendOps availability. SendOps handles the workflow orchestration and brings delivery events into view.
Your team gets the full toolkit
Message search, templates, broadcasts, inbound email, DMARC monitoring, alerts, and integrations support every journey.
Proven in email operations
4 million emails.
One clearer picture.
Cloud 66 connected SendOps to its existing SES account and replaced five custom tools with delivery analytics, message search, and team alerts. That operational foundation supports every workflow you build.
4M
emails per month
3
sending domains
5
tools replaced
The whole email picture
The full SendOps email toolkit.
Drip campaigns are our primary use case. You can also use SendOps for broadcasts, transactional email visibility, domain authentication, reputation monitoring, and receiving email without building a drip campaign.
Drip campaigns on AWS SES
Automate onboarding, cart recovery, and follow-ups. Build visually or in SendFlow; send through your own AWS SES.
Learn moreAudience & segments
Make each follow-up relevant with contact data, product activity, and consent.
Learn moreTemplates & assets
Create personal messages with reusable templates, previews, and version history.
Learn moreBroadcasts
Send or schedule newsletters, announcements, and one-off campaigns to lists and segments through your own SES.
Learn moreAnalytics & message search
See delivery, engagement, and the history behind an individual email.
Learn moreReputation monitoring & alerts
Monitor bounce and complaint rates, sending quotas, and delivery health. Get alerts when thresholds are crossed.
Learn moreDMARC monitoring
Identify services sending as your domain, inspect SPF and DKIM alignment, and assess readiness for stricter DMARC policies.
Learn moreAWS infrastructure
Domains, channels, tracking, and suppression on the SES account you own.
Learn moreAPI & integrations
Manage definitions and operational data through the API and MCP. Connect webhooks and push versioned definitions from CI.
Learn moreTemporary inboxes
Create short-lived receiving addresses through the API for agents, forwarded messages, and testing. Hosted by SendOps; inbox contents are deleted at expiry.
Learn moreInbound email
Receive email on a domain you own and deliver parsed messages to your application by webhook through your AWS receiving setup.
Learn moreWebsite Identity
Connect return visits from known contacts to follow-ups using Google Tag Manager. Combine website activity with product, cart, and conversion events.
Learn moreChoose your next move
Built for better customer journeys.
Explore the workflows, compare the options, and find a starting point for your team.
Lifecycle marketing
Launch onboarding and re-engagement journeys without handing every change to engineering.
Workflows for developers
Connect product events, version the logic, and build with the API or your coding agent.
Compare workflow platforms
Understand the differences in authoring, audience pricing, delivery, and control.
A few useful answers
Workflows first. The whole email toolkit behind them.
What is SendOps?
SendOps is an email workflow and drip campaign platform built on AWS SES. Build customer journeys visually or in SendFlow, with audiences, templates, broadcasts, analytics, DMARC monitoring, reputation alerts, temporary inboxes, and inbound email. Email delivery runs through your own AWS SES account.
Can I use SendOps without running drip campaigns?
Yes. Use broadcasts, delivery analytics, message search, reputation alerts, DMARC reporting, templates, inbound email, or temporary inboxes. Drip campaigns on AWS SES are the primary use case, but you do not need a workflow to use the broader email toolkit.
Can a workflow do more than send email?
Yes. Add webhook steps to call your own services for SMS, push notifications, CRM updates, or other actions. Your service handles delivery and channel consent; SendOps orchestrates the journey and can send an email fallback if a webhook fails.
Does SendOps charge per contact or per email?
Neither. SendOps charges a flat platform fee: Free, Team at $29 per month, or Business at $149 per month. AWS bills SES delivery and other AWS usage separately. SendOps plans set team and resource limits.
Why use SendFlow for email workflows?
SendFlow makes the journey readable by people and AI agents. Keep workflow definitions in version control, review diffs, and trace changes in SendOps history. The visual canvas and source editor show the same workflow.
Can a website visit start an email workflow?
Yes. With Website Identity and Google Tag Manager, a previously identified contact can trigger a workflow when returning without a fresh sign-in. Combine the visit with conversion or cart data to send a relevant follow-up.
Do I need an AWS account to send campaigns?
Yes. Connecting your AWS account is the first setup step. SendOps uses a keyless role to connect to SES and guides you through preparing your sending domain. Existing application email can continue sending directly through SES, independently of SendOps availability. Temporary inboxes run on SendOps infrastructure and can be used without connecting AWS.
Your next workflow starts here
Give every customer a next step.
Connect your AWS account. Build your first journey. Make the next email count.
Free plan available. No credit card required.