# Your whole email operation. One platform.

Type: Product
Canonical: https://sendops.dev/product/
Publisher: SendOps
Updated: 2026-10-04

Run campaigns on your own AWS SES, monitor delivery and reputation, understand domain authentication, and connect incoming email to your tools. SendOps brings workflows, broadcasts, DMARC reporting, temporary inboxes, and more into one platform.

## 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 more](https://sendops.dev/product/workflows/)

## Audience & segments

Make each follow-up relevant with contact data, product activity, and consent.

[Learn more](https://sendops.dev/product/audience/)

## Templates & assets

Create personal messages with reusable templates, previews, and version history.

[Learn more](https://sendops.dev/product/templates/)

## Broadcasts

Send or schedule newsletters, announcements, and one-off campaigns to lists and segments through your own SES.

[Learn more](https://sendops.dev/product/broadcasts/)

## Analytics & message search

See delivery, engagement, and the history behind an individual email.

[Learn more](https://sendops.dev/product/observability/)

## Reputation monitoring & alerts

Monitor bounce and complaint rates, sending quotas, and delivery health. Get alerts when thresholds are crossed.

[Learn more](https://sendops.dev/product/notifications/)

## DMARC monitoring

Identify services sending as your domain, inspect SPF and DKIM alignment, and assess readiness for stricter DMARC policies.

[Learn more](https://sendops.dev/product/dmarc-monitoring/)

## AWS infrastructure

Domains, channels, tracking, and suppression on the SES account you own.

[Learn more](https://sendops.dev/product/infrastructure/)

## API & integrations

Manage definitions and operational data through the API and MCP. Connect webhooks and push versioned definitions from CI.

[Learn more](https://sendops.dev/product/integrations/)

## Temporary 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 more](https://help.sendops.dev/ai-agents/temporary-inboxes)

## Inbound email

Receive email on a domain you own and deliver parsed messages to your application by webhook through your AWS receiving setup.

[Learn more](https://help.sendops.dev/inbound/inbound-receiving)

## Website Identity

Connect return visits from known contacts to follow-ups using Google Tag Manager. Combine website activity with product, cart, and conversion events.

[Learn more](https://sendops.dev/guides/website-triggered-email-workflows/)

## Not using drip campaigns? Start with the email you already run.

Connect your existing SES account for delivery analytics, message search, and reputation alerts. Send a newsletter, investigate domain authentication with DMARC reports, or connect inbound email to your application. Each solves an email operations problem in its own right.

## Your AWS SES for sending. SendOps for orchestration.

Campaigns send through SES in your AWS account. SendOps manages workflow orchestration, contacts, definitions, and analytics; AWS bills your SES and other AWS usage separately. Existing application email sent directly through SES remains independent of SendOps availability. Temporary inboxes are a separate receiving tool on SendOps infrastructure and can be used without connecting AWS.
