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.
Judged purely as an API. What the request contract guarantees on retry, how complete the webhook event coverage is, whether suppressions are readable and writable programmatically, and how much the message log retains when something needs debugging in production.
Against high-frequency programmatic sends where a missed delivery is a product failure, Buttondown covers webhook coverage, event stream, the suppressions API, batch sending, and SDK breadth, and does not cover idempotency keys and operating track record. Whether that gap matters depends on how central those are to the build.
- Idempotency keys: No
- Webhooks: Yes
- Event stream: Yes
- Operating since: 2017
- Suppressions API: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: Yes
- SDKs: node, python
- Deliverability: Good for newsletter content; small operation but careful sending practices.
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 |