Your account. Your reputation. Your list price.
AeroCampaign operates no sending infrastructure. Every message goes out through credentials you own, on an IP reputation you control, billed by your provider at their rate. We handle the machinery that keeps that reputation intact.
Verified on connect, not on first failure
Connecting a provider is not just storing a key. AeroCampaign checks the things that break sends before you discover them at 09:00 on launch day.
- SendGrid: API scopes checked for mail.send, verified senders listed
- SES: send quota, max send rate, and 24-hour usage read from the account
- SES sandbox detected on connect — broadcasts blocked until production access is granted
- Only DKIM-verified identities are offered as From addresses
- Event pipeline provisioned automatically: webhook registration, or Configuration Set plus SNS topic
- Credentials sealed with AES-256-GCM; IAM role assumption supported instead of long-lived keys
A rolling 30-day bounce and complaint rate, overall and per provider. The thresholds are not ours — they mirror the levels at which Amazon places SES accounts under review and mailbox providers start throttling.
You see the warning at the same moment your provider does — not after the suspension email.
One list, both providers, enforced in SQL
Bounces and complaints from SendGrid and SES land in a single account-level suppression set. Enforcement runs as an anti-join when recipients are materialized — never in application memory — so it holds at any list size.
| Reason | Trigger | Duration |
|---|---|---|
| Hard bounce | SES Permanent, or SendGrid 5xx / blocked | Permanent |
| Soft bounce | 3 transient bounces within 30 days | 90 days, then expires |
| Complaint | Spam report from either provider | Permanent, cannot be removed |
| Unsubscribe | Link click or RFC 8058 one-click POST | Permanent |
| Manual | Added by you | Until you remove it |
| Provider import | Pulled from SES or SendGrid on connect | Permanent |
Two-way sync
On connect we import your existing suppressions from SES and from SendGrid’s bounce, spam-report, and unsubscribe endpoints. When AeroCampaign suppresses an address for a bounce or complaint, it is mirrored back to AWS so the two lists never drift.
Complaints are immutable
Complaint suppressions cannot be deleted through the UI or the API. Resending to someone who marked you as spam is the single fastest way to get a domain blocklisted, so the product refuses to let you do it. Every other removal is audit-logged.
Bulk-sender rules, handled on every send
Gmail and Yahoo require these of anyone sending 5,000 or more messages a day. They are not a premium tier here — they are on every message that leaves the platform.
- List-Unsubscribe and List-Unsubscribe-Post headers per RFC 8058
- One-click unsubscribe endpoint writing straight to the suppression engine
- Unsubscribe link and physical postal address enforced in the composer
- GDPR data export and deletion for any contact
- Normalized event log across both providers, with idempotent ingestion
- Webhook signatures verified: Ed25519 for SendGrid, Amazon certificate for SNS
Both paths converge on one event stream — sent, delivered, open, click, bounce, complaint, reject, unsubscribe — attributed back to the campaign and the contact.
Connect a provider and see your real numbers.
Import your suppression list, check your rolling bounce and complaint rate, and find out where your domain actually stands.
No credit card. Bring your own SendGrid or Amazon SES account.