Buttondown

1. 1

   You sign up, verify a sending domain, and write. The editor supports both markdown and rich text, built on Tiptap, with LaTeX and footnote support that Duke's team open-sourced as standalone extensions. Custom domain sending and hosted archives are included in the base price rather than sold as upgrades.

2. 2

   Subscribers arrive by form, import, or API. Every new newsletter that imports subscribers from an external source goes through a manual approval process, typically 8 to 24 hours, which is unusually strict and is why Buttondown's deliverability reputation holds up. Imported subscribers do not have to re-confirm and Buttondown does not automatically email them, though imports from sources without clear opt-in such as a CRM may be asked to send confirmations first.

3. 3

   You choose what to pay for. The base plan by subscriber count covers the editor, custom domain sending, hosted archives, and privacy-first infrastructure. Then you add what you actually need: tagging and segmentation, paid subscriptions, comments and surveys, analytics, RSS-to-email, sponsorships, or attachments at $9 each; archives on a custom domain, multiple newsletters, or automations at $29 each; whitelabeling or teams at $79 each.

4. 4

   Everything the web app does is available through the public REST API, because the app is built on the same API. There are no official client libraries by deliberate choice, and Buttondown tells you to generate your own from the published OpenAPI spec. There is a CLI, webhooks, an official Zapier integration, and since February 2026 multiple API keys per account with granular per-key permissions.

A base price by active subscriber count, plus features bought individually as $9, $29, or $79 monthly add-ons. Only active subscribers are billed, so unsubscribed and bounced contacts cost nothing, and Buttondown takes 0 percent of paid subscription and sponsorship revenue.

Value assessment: Buttondown is the best value in this category for the specific writer it is designed for: someone sending a newsletter to a list under 20,000 who wants two or three capabilities rather than thirty. At 1,000 subscribers, $9 a month for sending from your own domain with a hosted archive and a full REST API is straightforwardly cheaper than anything comparable, and the active-subscriber billing means a churny list never accumulates dead weight on the invoice. Taking 0 percent of paid subscriptions makes it dramatically cheaper than Substack for any newsletter earning real money. The value case breaks in two places. If you want most of the add-ons, the à la carte total climbs past what a bundled competitor charges. And if your list exceeds 20,000 there is no published price at all, which makes budgeting impossible and is a genuine obstacle for a growing publication trying to plan.

Setup time

Under an hour to a first send, with one caveat: if you are importing an existing list from another platform, every new newsletter goes through a manual approval process that typically takes 8 to 24 hours. Domain verification is automatic once DNS records are in place, and there is no template building step if you write in markdown.

Learning curve

Very low for writing and sending, and pleasantly low for developers, since the API is the same one the web app uses so anything you can click you can script. The only genuinely confusing part is the pricing model itself, because working out which add-ons you need takes more thought than picking a bundled tier.

Onboarding

Entirely self-serve, with free done-for-you migration available regardless of list size through concierge@buttondown.com. Support is by email and through public GitHub Discussions, and the roadmap and bug tracker are public repositories.

Migration notes

Buttondown has first-class importers for Kit, Mailchimp, and Substack, plus a generic importer that accepts a ZIP of markdown files with frontmatter in Jekyll or Hugo format, and a dedicated TinyLetter path from the February 2024 shutdown wave. They will do the import for you at no charge whatever the list size. Imported subscribers do not have to re-confirm and Buttondown does not automatically email them, though imports from sources without clear opt-in such as a CRM may be asked to send confirmations first, and Buttondown checks with you before requiring it. Budget for the 8 to 24 hour manual approval on any external import.

Platforms

Web applicationCommand-line interfacePublic REST APIHosted archive on your own domain

API

A public REST API that the entire web application is built on, documented at docs.buttondown.com with a published API changelog, plus webhooks, an official TypeScript CLI, an open-source OpenAPI spec on GitHub, and granular multi-key permissions since February 2026. Buttondown deliberately ships no official client libraries and instructs you to generate your own from the spec. An official Zapier integration exists; there is no first-party MCP server, though a third-party one is published on GitHub.

Compliance

GDPR rights acknowledged in the privacy policy with a 72-hour breach notification commitmentTracking disabled by default

Data residency

No evidence of an EU data region; assume US hosting unless confirmed otherwise. The privacy policy names only Stripe as a subprocessor and sending and hosting providers are not disclosed, so buyers with infrastructure transparency requirements should ask directly.

SSO

Not offered; team access is covered by the $79 teams add-on with customizable contributor permissions.

Security notes

Every new newsletter importing subscribers from an external source goes through a manual approval process of typically 8 to 24 hours. IP filtering runs against Spamhaus and Project Honeypot, inactive addresses are cleaned automatically, and a configurable Firewall shipped in April 2025 lets you set thresholds that auto-block suspicious signups into a manual review queue. Buttondown adheres to complaint feedback loop standards, sends from its own IP addresses for reverse DNS, and disables accounts for spam or cold emailing.

Channels

Email support and concierge at concierge@buttondown.comPublic GitHub Discussions for feature requests and bug reportsSupport page at buttondown.com/support

Documentation

Documentation at docs.buttondown.com, itself open source on GitHub, covering the API, imports, deliverability, and a glossary of email infrastructure concepts.

Community

Public roadmap and bug tracker repositories on GitHub where issues are discussed openly, plus a published changelog.

Founded

2017

Headquarters

Fully remote, United States

Ownership

Bootstrapped and independent, profitable, with no outside funding raised

Founders

Justin Duke

Employees

Roughly 12 to 13 people listed publicly, a mix of full-time staff and contractors

Funding

No funding raised. Buttondown states it is profitable, self-funded, and has no plans to change that. Justin Duke built it as a side project while an engineer at Stripe and left to run it full time around 2022 at roughly $15,000 in monthly recurring revenue. Current revenue is not published.

Buttondown is the most intellectually honest product in this category. Billing only for people still reading, turning tracking off by default, taking nothing from your subscription revenue, and letting you buy three features instead of thirty are all decisions that cost the company money and benefit the customer, which is the sort of thing only a bootstrapped business with no growth mandate tends to do. For a writer or developer with a list under 20,000 who wants a newsletter from their own domain and an API they can script against, nothing else at $9 a month comes close. The gaps are real and worth weighing: no A/B testing at all, automation that is a sequence tool rather than a workflow builder, no discovery mechanism, an undisclosed sending provider, and no published price whatsoever above 20,000 subscribers, which makes planning for growth genuinely awkward. Buy it if the newsletter is the product and you value ownership and privacy over features you would not use. Look at Ghost if you need a publication, beehiiv if you need an audience, and Kit if the list exists to sell things.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.