惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

文章列表

Compulsive curiosity, or, how I built an infinite idea machine Gift details on the subscriber portal Portal link in the archive nav The physicists who convinced Fermilab to send Brazil's emails First, add no friction: How micropayments lost and subscriptions won Filter subscribers and automations by source Automations, rebuilt What email will look like in the future Filter subscribers by bounce date and reason Email could have been X.400 times better Three features are moving behind the paywall Firewall changes and improvements Put your name and voice into your company newsletter Simplified email address settings Subscription wall Inboxes were overwhelming before we'd even named them The US government tried really hard to screw up email Public postmortem: database connection exhaustion Ask a nerd: what is the best way to unsubscribe from newsletters? Bookshop.org embeds Email was into agents before they were cool Passwordless login Rename metadata keys in bulk A spring cleaning for our legal docs Ask a nerd: what happens when you click the spam button? Passkey support for two-factor authentication How Buttondown's API versioning works Safer defaults for the email creation API How to send email to space How we enabled Content Security Policy for everyone Recovery codes for two-factor authentication Filter sent emails by engagement rate How we migrated to TypeIDs without breaking clients How we check every link in your email Use newsletter metadata in your emails Should we bring back email exploders? Sort and filter by open and click rates Custom click tracking domains More newsletter settings in the API Revamped replies Custom email templates for everyone Simplified cancellation Ask a Nerd: Does email length affect deliverability? The changelog, reborn Swedish localization Forwarding an email is not always straightforward Public descriptions for tags OpenAPI spec for archives How Rodrigo brings a humanistic view to consumer technology Subscribers can come from anywhere. Even another newsletter platform's form. Survey responses on the web How Brandon Lucas Green shares his music and supports artists Your newsletter's archives are more valuable than your list Better tag self-management Smarter automation filters Granular API keys Snippets New design settings pages Ask A Nerd: How does newsletter cadence affect deliverability? Starred views More ways to customize your archives Inbox filtering Mastodon follower analytics Ask a Nerd: What are good open, click, and response rates for an email newsletter? How we migrated our database to PlanetScale Two new archive themes Custom buttons now work in Markdown mode Ask a Nerd: Does attaching files to your newsletter hurt deliverability? Seline and Tinylytics support Unban subscribers Announcement bars for your archives Bang paths, source routing, and how email trips were planned Public postmortem: archive downtime disposables.app Russian localization Ask a Nerd: Can you improve email deliverability with a personal domain? More locale options How we interview customers at Buttondown Bluesky analytics Reply to conversations Minimum viable complexity How Jeffery Hicks goes behind-the-scenes in his newsletter Changes to our stack in 2025 2026: Emails What the hell is a UTM? TK reminders in the editor Randomize survey answer order Why we insourced analytics Scroll sync in the editor 2026: Archives How Jamie Thingelstad uses Buttondown to explore tech topics How Kelly Jensen uses Buttondown to discuss key library issues Keeping feature creep at bay Improved filters Content Security Policy in archives Open source Sniperl.ink Auto-activating RSS reader subscriptions What the hell is ActivityPub? Gift subscriptions How Igor Ranc built Berlin's largest expat tech newsletter
2025
Justin Duke · 2025-12-25 · via

What we shipped in 2025

It's become a tradition to look back on the previous year and reflect on what we shipped, what we didn't, and what's next. Let's start with all the stuff we built to make your lives easier, however slightly:

FeatureDescription
CAPTCHAAdvanced CAPTCHA to protect signup and forms from automated spam and abuse.
CLIA dedicated command-line interface with bidirectional sync for emails, automations, and images.
Configurable firewallComprehensive spam and abuse protection with tunable aggressiveness, CAPTCHA support, and smart detection.
Dark modeFull dark mode support for the app and public pages. (complete)
Gift subscriptionsSubscribers can purchase paid subscriptions as gifts directly from the subscribe page.
InboxIntegrated test inbox for previewing emails before real subscribers receive them.
LocalizationApp and subscriber-facing pages support multiple languages, with per-newsletter overrides.
Managed DNSProvide a single domain; Buttondown automatically configures both sending and hosting, including Google Postmaster and tracked replies.
PlaygroundDedicated sandbox for experimenting with automations and templates without affecting live data.
PortalSelf-service subscriber portal for managing email, referrals, preferences, and unsubscriptions.
Revamped archivesMultiple archive themes and point-and-click controls for custom design, no CSS needed.
Rewritten search experienceMuch faster and more complete search for authors and subscribers. (complete)
Test modeSafely test automations, campaigns, and subscription flows without contacting real subscribers.

We did this while scaling up our support and infrastructure, reducing technical debt, and keeping our bug count low (as of this essay, the count is at 12.) There are some thing we didn't get to by the end of the year — faster exports, custom fonts + design tokens, and a bookmarklet — but we'll get to them in 2026, for real this time.


By the numbers

By the numbers, 2025 was a great year for Buttondown. The three most important metrics we look at are consistent usage, outgoing emails, and revenue (how many people use us; how many people are we sending to; how much money are we making). Here's how things shook out:

Metric% Change
Active authors (sent in last 30 days)+45%
Unique subscribers emailed+72%
Revenue+61%

Notable in the above is the fact that authors actually grew faster than we did. This is terrific!

If you're a dork, here are some really inside baseball metrics on the operational side:

Metric20252024% Change
Codebase commits6,5144,487+45%
Support tickets answered5,2473,906+34%
Median first response time5 hours7 hours-29%
Support ticket word countOver 2.2M1.7M+29%

Numbers and features are fun for us, but they mean nothing on their own unless done in concordance with our core values. If you're reading this, you likely don't particularly care about our growth — nor may you particularly care about our new features, as the plurality of users (including, perhaps, you!) do not need any of them and merely want Buttondown to do the main thing really well: send emails quickly and reliably, manage subscribers without giving you a migraine. To that end:

Principle2025 Update
Data protection and privacyOur stance on data protection and privacy is not just as strong as ever; it’s stronger, thanks to our insourcing of third-party data services (details) and our evolved stance on AI (our approach).
Financial sustainabilityWe remain cash-flow profitable, meaning we don’t need to chase a big fundraising round or pivot to video advertising or social networking.
Open sourceWe've deepened our open source commitment by releasing additional parts of our core platform and extending our broader open source pledge.
Customer serviceOur customer support team has grown stronger and more responsive, aiming to provide even better experiences for authors and subscribers.
Stability and change managementFrankly, we had too many incidents and breaking changes in 2025. While some were necessary, we're prioritizing stability moving forward by instituting better processes around backwards compatibility and proactively engaging authors whenever major changes—like to CSS or API behaviors—are on the horizon.

2026 roadmap

Our plans for the coming year are, as ever, a little boring and entirely devoid of plot twists:

ProjectDescription
Paid subscriptions 2.0An embedded checkout experience that doesn't rely on Stripe, plus improved support for esoteric options like per-email/PWYW pricing.
Archives 2.0Our archives feel as good as our core app to use (and customize). We offer multiple themes to fit our various segments; non-technical authors can customize them without dropping down to CSS. Subscribers have a cohesive experience across all parts of their web experience (reading, subscribing, surveys, comments, paid subs.)
Unified importsA smoother one-step import experience for all data types, including subscribers, emails, and exogenous data.
Data 2.0Speeding up our three largest data-shaped operations: event-level aggregation for analytics, fuzzy search within a newsletter, and exporting large datasets.
Self-hosted SMTPEmail sending is our single biggest unit cost and has also been a supply chain risk given incidents and reputational damage from all of our downstream MTAs; by insourcing this, we can improve performance, reliability, and cost.
Automations 2.0The automations UI is rebuilt and integrated more deeply into the core app with an eye towards the most common use cases: sync, drip sequences, etc.
DNS 2.0Rather than a separate hosting and sending domain, we let users just provide a single domain to us, which we manage and spin up both hosting and sending for. In addition, we spin up auxiliary services like Google Postmaster Tools and tracked replies without them having to do anything.

Okay, we're done with tables now, I promise. It is time to get a little earnest.

The industry in which we build is a unique one: authors have extremely high levels of portability and agency. Every single one of you, if so you wish, could export all of their data and migrate it to one of myriad other options over the course of an afternoon. (In fact, we invest a lot in making that true because you deserve to own your data end to end.)

Every passing day in which you don't do that — in which you continue to invest in us — is a tacit acknowledgement that you find Buttondown valuable enough to keep paying for, and that is not something we take for granted.

Nor do we take for granted the fact that while our competitors have the resources to buy Super Bowl ads and spend millions of dollars luring individuals onto their platforms, we rely simply and merely on word of mouth, on the hope that you find us useful enough to tell a friend or colleague about.

And you do. A lot.

Our growth this year is owed entirely to you: not just because you find us useful, but because you like us enough to tell a friend or colleague about us. This grants us both the luxury and the responsibility of building exactly what you want us to build.

Our work is grounded in a single conviction: that our most important job is to provide continuity and reliability for you and your readers, not just for years but for decades to come.

Speaking personally: when I started Buttondown years ago, I had no idea it would grow in size or scope the way it has. I am flattered and honored that I get to work on it every single day alongside a group of people who care just as much about writing and reading as I do; I am equally flattered and honored that you collectively vote with your hearts and wallets to let us keep doing it.

On behalf of the team — thank you.

(And, as always, if you have anything you wish to tell me, I'm at justin@buttondown.email.)

signature