Comparison
tinysend vs Customer.io
Keep the workflow layer, send from your own Amazon SES account, and run the software on infrastructure you control.
Read the setup guide →What this open-source release covers
Your SES account
tinysend assumes a least-privilege IAM role and never stores long-lived AWS access keys.
The essential workflow
Transactional API, contacts, versioned templates, broadcasts, suppressions and optional tracking.
Agent-ready by design
Use the REST API, typed npm SDK, OpenAPI document, llms.txt and MCP server from the same installation.
Feature comparison
A direct feature-by-feature breakdown
| Feature | tinysend | Customer.io |
|---|---|---|
| Usage-based pricing | Open source + AWS | |
| Bring Your Own Key (BYOK) | Amazon SES | |
| Sequences as code (CLI) | ||
| Email automation / sequences | ||
| REST API | ||
| Transactional email | ||
| Contact segmentation | ||
| Webhooks | ||
| Free tier | ||
| No seat-based limits | ||
| Agent-native (AI automation) |
Pricing comparison
Software cost only; AWS and hosting are billed by their providers
tinysendMIT-licensed software
- Self-host on any Docker host
- Send through your own Amazon SES account
- No tinysend message or contact markup
per month
- Flat-rate plans — pay whether you use it or not
- No BYOK option
- Seat limits on lower tiers
Who should use tinysend?
Teams that want to replace a managed transactional email bill with their own Amazon SES account.
Developers who need a small REST API, typed npm SDK, templates and delivery status without a large marketing suite.
Organizations prepared to operate PostgreSQL, a Docker deployment and their own AWS and DNS configuration.
AI agent builders who need explicit schemas, idempotent writes, dry runs and an MCP interface.
Exploring all your options?
See the best Customer.io alternatives →Please bring your own sender...
from: tinysend
to: you
with: love
Ready to start sending?
Self-host free. Connect your SES account. Keep your sending cost at AWS rates.