Buttondown
Minimalist, indie-built newsletter platform.
Buttondown is run by a single developer and reflects that ethos: clean Markdown editor, transparent pricing, API-first architecture, no ad marketplace, no upsells. Beloved by technical writers.
A SaaS product sends on behalf of its customers, so the deciding factors are tenant isolation, whether suppressions can be scoped rather than global, and whether support can answer why one specific account did not receive one specific email. Lifecycle automation and transactional sending usually need to coexist.
Against trial expiry notices, dunning, onboarding sequences, and per-tenant transactional mail, Buttondown covers event stream, the suppressions API, scheduling, and webhook coverage, and does not cover multi-tenant support and operating track record. Whether that gap matters depends on how central those are to the build.
- Multi-tenant: No
- Event stream: Yes
- Suppressions API: Yes
- Operating since: 2017
- Scheduling: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Deliverability: Good for newsletter content; small operation but careful sending practices.
- Webhooks: Yes
- Starts at: $9/mo for 1,000 subscribers
Good for newsletter content; small operation but careful sending practices.
Developer-bloggers and indie writers who want a clean API and Markdown.
- › Markdown-first editor
- › API for everything
- › Indie-developer ethos
- › Single-developer team is a real risk
- › No marketing automation features
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node, python |
| Webhooks | Yes |
| Templates | basic |
| React Email | No |
| Batch send | Yes |
| Scheduled send | Yes |
| Suppressions | Yes |
| Multi-tenant | No |
| Inbound parsing | No |
| Event stream | Yes |
| Idempotency keys | No |
| Dedicated IP | No |