Integrations
SendOps fits into your stack. Your stack doesn't need to fit into SendOps.
No SDKs to install. No sending endpoints to swap out. SendOps connects to the services you already use — AWS SES, GitHub, Slack — pipes email data to your systems via webhooks, and exposes a public API for contacts, broadcasts, assets, and ingesting your own product's events. Your application code doesn't have to change.
The problem
Email tooling that forces you to rewire everything isn't tooling — it's a migration project
Most email platforms want you to send through their API. That means replacing your SES integration, updating every service that sends email, and trusting a third party with your delivery path. If you're already on SES, that's not an upgrade — it's a rewrite.
The alternative is building your own observability, alerting, and template management on top of SES. But that means wiring up EventBridge, CloudWatch, Lambda functions, and a UI for your team to use — all plumbing that has nothing to do with your actual product.
SendOps takes a different approach. It connects to the infrastructure you already have, reads the events SES is already producing, and gives your team a dashboard, alerts, and template workflows — without touching the way you send email.
How it connects
Four integration points. Zero changes to your sending code.
SendOps connects to your AWS account with a single click, your Git repository via GitHub, your team via Slack and webhooks, and everything else via a public API. Your application keeps sending through SES exactly the way it does today.
AWS SES
How it connects: A single CloudFormation template configures EventBridge rules that route every SES event — delivery, bounce, complaint, open, click — to SendOps automatically.
What flows: Event metadata — timestamps, statuses, engagement signals. The bodies of emails your application sends never pass through SendOps.
What you get: Real-time observability dashboard, message search, delivery metrics, alerting — all without writing a single CloudWatch query or Lambda function.
GitHub
How it connects: Connect your repository in the SendOps dashboard. SendOps watches for template changes on your branches.
What flows: Template source (React Email TSX, compiled to SES-native Handlebars on deploy) — and lists, segments, topics, and workflows, which can live as definitions in the same repo and sync the same way. SendOps validates, previews, and deploys on merge, reviews PR diffs on demand, and writes in-app edits back to your repo as pull requests.
What you get: Git-native template management. Pull requests, code review, rendered previews, automatic deployment. Marketing edits templates, engineering reviews — SendOps handles the rest.
Slack + Webhooks
How it connects: Add a Slack workspace or webhook URL in the SendOps dashboard. Choose which alerts go where.
What flows: Alert payloads — metric name, threshold, current value, affected domain or channel, and a link back to the SendOps dashboard.
What you get: Bounce rate spikes, complaint rate warnings, sending quota alerts, and domain verification events delivered to Slack, email, or any HTTP endpoint. Trigger PagerDuty, OpsGenie, or your own internal automation.
Public API
How it connects: Create an API key in the SendOps dashboard. API v1 is plain HTTPS and JSON — no SDK required.
What flows: Contacts, lists and memberships, broadcasts — create, send, test — assets, and undeliverable data. The Activity API ingests your product's events with durable deduplication.
What you get: Manage audiences from your backend, drive broadcasts from your own tooling, and turn product activity into signals that segments and workflows can act on.
0
SDKs to install
0
Lines of application code to change
0
sSeconds from SES event to SendOps dashboard
0
AWS keys stored by SendOps
Privacy
Your data. Your account. Your call.
The email your application sends stays between your application and SES — SendOps observes event metadata, not message bodies. The data you bring to the platform — contacts, lists, segments, templates, assets — is stored scoped to your organization, exportable at any time, and deleted with your account. And every email, yours or SendOps-authored, goes out through your own SES.
What SendOps stores
- Delivery, bounce, complaint, open, and click event data
- Contacts, lists, and segments you create or import
- Template source and uploaded assets
- Consent, topics, and suppression state
What SendOps never touches
- The bodies of emails your application sends
- Your application databases
- Long-lived AWS credentials — access is via short-lived STS tokens
- Shared sending infrastructure — every send uses your SES
Agent-ready
An integration surface coding agents can drive
SendQL segments, SendFlow workflows, and React Email template source are plain text files in your repository — the format coding agents already work in. The API covers the rest: contacts, broadcasts, assets, activity. When an agent proposes a change, it lands as a pull request that SendOps validates and previews — and a human merges.
- Segments, workflows, and templates are text in your repo — no UI to script against
- The API handles the rest: contacts, broadcasts, assets, and event ingestion
- Agent-authored changes arrive as PRs — validated by SendOps, reviewed by you
Integrations that match how each team works
SendOps doesn't require everyone to learn a new tool. It connects to the systems each team already uses — Git for developers, Slack for operations, the dashboard for marketing.
Developers
Templates live in GitHub. Infrastructure via CloudFormation. Events available as webhooks, everything else via the API — a surface your coding agent can drive too. Nothing changes about how your application sends email.
Marketing
No AWS console or Git required. The SendOps dashboard covers template previews, audiences, broadcasts, and campaign performance end to end.
Operations
Alerts go to Slack, email, or webhooks. Every alert includes the metric, threshold, current value, and a direct link to the relevant dashboard view.
Plug into your SES account in two minutes. Change nothing about how you send.
Free plan available. No SDK, no code changes, no migration.
