Skip to main contentSendbase uses your AWS account to store and manage all email resources.
Architecture
- Sending Email: All email sending operations are executed directly through AWS SES using your credentials. Sending quotas and limits are based on your AWS account’s SES configuration.
- Contact List: Contacts are stored and retrieved directly through AWS SES, not in our database. Your contact data never leaves your AWS account.
- Email Templates: Email templates are stored in AWS SES.
- Email Identity: Verified domains are configured and stored in AWS SES, determining which addresses you can send from.
- S3: Assets like images and contacts to import are stored in your S3 bucket.
- SNS: SES configuration sets publish email events (sends, deliveries, bounces, complaints, opens, clicks) to SNS topics, which then send webhooks to the application for message logs.
- Metrics: Email analytics (delivery rates, bounces, complaints, opens, clicks) are collected from AWS CloudWatch in your account.
Benefits of This Architecture
- Cost Efficiency: Pay only AWS SES rates (100x cheaper than traditional email services).
- Data Ownership: All your data stays in your AWS account with no platform lock-in.
- Dedicated Email Reputation: Your sending reputation is isolated to your AWS account.
- Scalability: Leverage AWS’s infrastructure and your SES sending limits.
- Security: Your data remain under your control.