
Buttondown
Newsletter software for people who write
About Buttondown
Buttondown is newsletter software for writers, built by Justin Duke in 2017 and run by Buttondown, LLC on customer revenue with no outside investors. It centers on a Markdown editor, a complete API and a CLI, and takes no cut of paid subscriptions beyond card fees. As of 2026-10-26 plans are tiered by list size and features: free up to 100 subscribers, $9 a month up to 1,000 with tags and paid subscriptions, and automations from the $29 tier.

What it is
Buttondown is a browser-based newsletter service. An author writes an issue in its editor; it sends the email, builds a web archive, and handles signups, unsubscribes, bounces and stats. By default mail goes out from an address like username@buttondown.email, and a custom domain can be connected.
It positions itself as a newsletter backend and nothing more. A testimonial quoted on the homepage notes it is not trying to become a social network or curated feed, and the alternatives page lists what it will not do: drip campaigns with branching logic, a content management system, self-hosting, media hosting and ecommerce email, each with a named product to try instead.
Justin Duke built it. The 2017 year-in-review post, dated 2017-12-26, says the decision to build came in late April that year; it could send email by the end of May, launched officially at the end of June, and had its first paying customers in July.
The company runs on customer revenue. The about page says it is funded by customers, not investors or VCs, and the pricing FAQ says the company has been profitable and self-funded since its founding in 2017, with no plans to change (as reported by the vendor). As of 2026-10-25 the about page lists 14 team members by first name.
Buttondown's API has been designed to be as RESTful and uninteresting as possible.
Core capabilities
Writing. The editor supports native Markdown, with a conventional visual mode as well; the features page also says an issue can be sent to Buttondown straight from a personal or work email account, without opening the web app.
Developer access. The docs describe the API as designed to be "as RESTful and uninteresting as possible": every object in Buttondown can be retrieved, created, modified and deleted, API changes go into the changelog, and backwards-incompatible ones get their own writeup. A CLI supports writing in a local editor, keeping drafts in Git alongside code and syncing them to Buttondown, and bulk-managing subscribers or pulling analytics from CI.
No cut of paid subscriptions. Payments run through Stripe, with monthly and yearly billing, multiple tiers, pay-what-you-like pricing and every currency Stripe supports; Buttondown takes nothing from subscription revenue, so the author pays only card fees. The features page adds that authors own the paying subscribers and their subscriptions and can take them along when they leave. Sponsorships carry no cut either.
Extras. Automations send sequences to new subscribers or run flows on tagged ones; there are also surveys, comments, attachments, RSS-to-email (turning a blog feed into emails), and more than 40 embed integrations for video, music and social posts.
Tracking off by default. The features page says no data about subscriber behavior is collected by default and open and click stats must be switched on; the about page says data is never sold and can be exported or deleted at any time.
Free migration. The homepage promises a free migration of any list size within one business day after the customer contacts support (as reported by the vendor).
Changelog. The changelog records shipped work day by day. Changes in late October 2026 include: on 2026-10-24 screen reader and keyboard support in the author app, limits on repeated sign-in attempts, and auto-disabling webhooks after five failed deliveries; on 2026-10-23 Brazil's LGPD standard contractual clauses in the data processing agreement.
Who it's for / Not for
For:
Individual and technical writers. Buttondown offers a Markdown editor, a CLI and a full API, and drafts can live in the same repository as code.
Authors starting a paid newsletter who want to keep more revenue. Buttondown takes no cut, and the subscriber relationship belongs to the author, portable to another platform later.
Small teams and non-profits that care about privacy and stability. Tracking is off by default; registered non-profits get 50% off with proof of registration.
People with an existing list who dread migrating. The free concierge migration covers lists of any size.
Not for:
Teams needing heavy marketing automation. Automations do not support branching or retries, and Buttondown's own alternatives page sends these needs to Kit.
People who want a website or blog CMS. Buttondown offers an email archive, not block editing or deep theming, and recommends Ghost instead.
Organizations that must self-host or audit source code. The core service is closed source; Buttondown recommends the open-source, self-hosted Listmonk.
Writers who rely on a platform network to grow. Substack has in-network recommendations and beehiiv has recommendation and ad networks; Buttondown has no in-network recommendations.
Large lists sending very often. The pricing page says all prices assume at most one email a day to the whole list; beyond that, usage pricing is negotiated with sales.
How it compares
Competitor prices are from each vendor's pricing page as of 2026-10-25 and Buttondown's are as of 2026-10-26, all at 1,000 subscribers.
Against Substack. Starting and publishing on Substack is free; authors keep 90% of paid revenue minus card fees. Substack has a reader app and in-network recommendations, which Buttondown lacks; Buttondown takes no cut and charges by subscriber count instead.
Against Ghost. At 1,000 members, Ghost(Pro) Starter is $15 a month billed yearly and includes a website and newsletter; paid subscriptions need the Publisher plan at $29 a month billed yearly, and the page states no payment fees. Ghost is a CMS with a website; Buttondown is mainly an email service.
Against beehiiv. beehiiv's free plan covers up to 2,500 subscribers; paid subscriptions start on Lite at $49 a month billed yearly with a 0% take on subscription revenue, plus ad and recommendation networks. beehiiv leans toward growth and monetization tools; Buttondown toward writing and the API.
Against Kit. Kit's free plan covers up to 10,000 subscribers and includes selling digital products and subscriptions; Creator at 1,000 subscribers is $390 billed yearly, shown as $33 a month. Buttondown's alternatives page names Kit for complex marketing automation.
Buttondown itself. Basic, up to 1,000 subscribers, is $9 a month and includes paid subscriptions; automations and multiple newsletters are on Standard at $29 a month. The paid-subscriptions page has a revenue calculator whose competitor figures are Buttondown's own calculations (as reported by the vendor).
Getting started
Step one, sign up. The docs say Buttondown runs entirely in the browser with no software to download; sign-up takes a username (it appears in the public URL), an email address and a password, followed by a click on the confirmation link sent to that email.
Step two, set branding and a sending domain. Fill in the newsletter name, description, colors and logo in settings. Mail goes out from a buttondown.email address by default; using a custom domain requires adding the DNS records shown. The changelog shows that in October 2026 several DNS-check issues were fixed, with a specific note for Cloudflare users.
Step three, import or grow subscribers. An existing list can be uploaded or handed to support for the free migration, and a signup form can be embedded on the newsletter's own site.
Step four, write and send the first issue. Write in Markdown or the visual mode, send a test email to the author's own address to preview, then send now or schedule it.
Going further. Paid subscriptions need Basic or above and a connected Stripe account; developers find the API key on the API requests page or manage drafts with the CLI. The pricing slider shows the tier and monthly price for a given list size, with the tier each feature needs marked next to it.
Pricing & license
Plans are tiered, and the tier sets both the subscriber limit and the features. As of 2026-10-26 the pricing page's offer data reads: Free for the first 100 subscribers; Basic $9 a month up to 1,000, or $90 a year; Standard $29 a month up to 5,000, or $290 a year; Professional $79 a month up to 10,000, or $790 a year; $139 a month up to 20,000; larger lists via the page slider. Only active subscribers who receive email are billed.
Features unlock by tier. Basic adds tagging and segmentation, paid subscriptions, comments and surveys, analytics, RSS-to-email and attachments; Standard adds sponsorships, custom-domain archives, multiple newsletters and automations; Professional adds white-label and teams. The page defaults to 100 subscribers, and the "+$9", "+$29" and "+$79" next to features are the price difference for upgrading from the free tier to the tier that includes them. They are not separate add-on fees and do not stack: needing both tags and automations means Standard at $29 a month.
Discounts and limits. Registered non-profits get 50% off; all prices assume at most one email a day to the whole list, with usage pricing beyond that.
License. Buttondown is a closed-source hosted service governed by its terms of service; the buttondown GitHub organization open-sources only peripheral packages such as editor extensions and Django tools, for example the MIT-licensed tiptap-footnotes.
Risks & limits
Features and tiers. Automations, multiple newsletters and sponsorships need Standard, from $29 a month, and teams and white-label need Professional, from $79 a month. Needing just one of them still means paying for the whole tier.
The features page and the pricing page differ. The features page says "Unlimited newsletters… only charged for your total subscribers" and "Unlimited contributors", and the homepage says teams have "no per-seat charge", yet the pricing page offers multiple newsletters only from Standard and teams only from Professional.
Free tier. Free stops at 100 subscribers, against 2,500 on beehiiv and 10,000 on Kit. The about page explains the company deliberately avoids very generous free plans to keep serving all customers well.
Team size. As of 2026-10-25 the about page lists 14 names; an Open Source Pledge article puts full-time staff at "a half-dozen-or-so" (the article is undated).
Infrastructure migration. September 2026 had two public incidents: on 2026-09-02 00:46–01:06 (UTC+8) the dashboard and archives on default domains were down for about 20 minutes; on 2026-09-10 02:35–04:35 (UTC+8) the web app was slow and sending was delayed, and the postmortem says no data was lost and all emails eventually went out. The stack page shows Heroku replaced by AWS on 2026-10-21. The postmortems are published, and the status page shows 99.98% uptime for the subscriber-facing and author-facing apps from July to October 2026 (as reported by the vendor).
Limited marketing automation. Buttondown concedes its automations are less complex than dedicated marketing platforms, without branching or retry logic.
Accessibility. The 2026-10-24 blog post says the author app now supports screen readers and keyboard navigation, but has not yet been audited against WCAG 2.2, and support for Windows' high-contrast mode is still planned.
How it got here
It began with TinyLetter. In the introduction to the Buttondown book, Justin Duke recalls that TinyLetter, bought by Mailchimp, had gone unmaintained to the point that every button press felt risky; Buttondown started as a personal replacement, and only after sharing development screenshots drew strong interest did it become a public product.
- The year-in-review post records wanting such a tool on social media in January and February, starting in late April, sending email by the end of May, launching at the end of June, and the first paying customers in July.
In the years since, Buttondown has stayed unfunded. The Open Source Pledge profile says the team grew to about a half-dozen full-time staff, and that this was not for lack of investor interest but because the founder does not want to run the company that way. The company pledges 10% of profits to the open-source projects it depends on and is a FOSS Funders member and Open Source Pledge signatory.
Engineering cleanup in 2026. Earlier in the year the database moved to PlanetScale; a 2026-09-10 post describes deleting the three largest tables and shrinking the database from about 2TB to 750GB. From 2026-09-14 development tooling switched from Cursor and OpenAI to Anthropic, and on 2026-10-21 hosting moved from Heroku to AWS. The stack page lists the monthly cost of every service, totaling about $96,258 a year as of 2026-10-25 (as reported by the vendor), with Stripe not listed because it scales with revenue.
In October 2026 the team focused on accessibility in the author app while continuing daily features and fixes.
Our verdict
What sets Buttondown apart: no cut of paid subscriptions; a complete API and a CLI; a published changelog and postmortems; a stack page listing the monthly cost of each piece of infrastructure; and tiers priced by subscriber count.
Its limits: no in-network recommendations; automations without branching or retries; a free tier capped at 100 subscribers; and automations and teams on the $29 and $79 tiers respectively. The alternatives page recommends Ghost for a content website and Kit for complex marketing automation.
Why it stands out
Buttondown is newsletter software for people who write, started and still led by Justin Duke with a very small team, with a level of engineering care and written restraint that larger competitors do not match. The editor stays out of the way, the API is complete, and the documentation is a pleasure.
The company has grown steadily without venture funding, publishes its changelog like a diary, and has become the default choice for technical writers who want to own their audience without owning a mailing infrastructure.
It is led by its founder, Justin Duke, with a very small team, has grown without venture funding, and offers a complete API and a public changelog.
Sources
Official
- Buttondown — Newsletter software for people like you · Accessed Oct 25, 2026
- Buttondown: Pricing · Accessed Oct 25, 2026
- About Us — Buttondown · Accessed Oct 25, 2026
- Buttondown Email Newsletter Features · Accessed Oct 25, 2026
- Paid Email Newsletter Subscriptions - Buttondown · Accessed Oct 25, 2026
- Email Newsletter Alternatives — Buttondown · Accessed Oct 25, 2026
- Changelog – Buttondown · Accessed Oct 25, 2026
- Welcome to Buttondown! | Buttondown Docs · Accessed Oct 25, 2026
- API introduction | Buttondown Docs · Accessed Oct 25, 2026
- Stack – Buttondown · Accessed Oct 25, 2026
- The Great Pruning – Buttondown blog
- Dashboard and Archives downtime – Buttondown blog
- Web app and email delays – Buttondown blog
- Buttondown Status · Accessed Oct 25, 2026
- Making Buttondown easier to use – Buttondown blog
- Terms of service – Buttondown · Accessed Oct 25, 2026
- 2017 in review – Buttondown blog
- Introduction – The Buttondown book · Accessed Oct 25, 2026
Media & third party
- Buttondown: How One Team Built a Successful Business by Building Less – Open Source Pledge · Accessed Oct 25, 2026
- Buttondown (GitHub organization) · Accessed Oct 25, 2026
- Substack Revenue Calculator · Accessed Oct 25, 2026
Related products
- Ghost(Pro) plans & pricing · Accessed Oct 25, 2026
- Pricing - beehiiv · Accessed Oct 25, 2026
- Kit pricing · Accessed Oct 25, 2026
Updates & reading
Making Buttondown easier to use
This time, we turned that lens on ourselves: the app you use to write, send, and manage your newsletter.
What I love about Django
I do not look at Buttondown and see a Django app; I see a well-structured codebase with many things that have been solved by smarter people than myself.
We built our own dig
So, on a rainy day last week, I built our own version , which we've been using happily ever since.
How we localize Buttondown
JSON is portable and legible, and those two properties are increasingly underrated these days!
Turning our OpenAPI schema into a bug finder
Example-based tests show that an endpoint handles the scenarios we know to test. Schemathesis probes the scenarios we did not think to write down.