Email and newsletters decision
Buttondown
A competent engineer can build a usable newsletter sender and archive in a few months using open-source components and SES/Stripe, but matching Buttondown's deliverability, concierge migration, integrated comments/surveys, and polished product experience would require more time and operational effort.
Visit website↗$9/mo
$108/yr
Read off the official pricing page.
$100one-off80 h to build
$25/mo8 h/mo upkeep
On cash alone, building overtakes the subscription at 4 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Buttondown alternatives, with the arithmetic →
Code Buttondown publishes itself
Not a way out of the subscription - these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Accept subscribers, compose/format newsletters, schedule/send via SMTP/transactional provider, host public archives, and manage paid subscribers via Stripe.
What it still won’t have
- Concierge migration service
- Buttondown's deliverability & spam-protection optimizations
- Built-in comments, surveys, and sponsorship marketplace
- Whitelabeling and team features with no per-seat charge
- GDPR/privacy integrations and analytics out of the box
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 4 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted newsletter service using PostgreSQL, a single-node Rails or Django app, and Amazon SES for delivery. Include: subscriber signup/unsubscribe endpoints with email validation and duplicate prevention; a Markdown editor for composing newsletters and HTML rendering; scheduling and immediate-send support that enqueues jobs (Sidekiq or Celery) and sends via SES with retries and bounce handling; hosted public archives per newsletter; Stripe integration to accept paid subscriptions and gate archive pages; basic analytics (open/click via tracking pixels and proxied link redirects). Out of scope: comment system, sponsorship marketplace, multi-tenant whitelabeling, and concierge migration. Include error handling for delivery failures, webhook handlers for bounces/complaints, automated tests for subscriber flows and send pipeline, and deployment scripts for a single VPS (systemd/docker) and instructions to configure SES DNS and Stripe keys.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Evidence score63
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productButtondown — Newsletter software for people like you
- official pricingButtondown: Pricing
- official docsButtondown Email Newsletter Features
- open sourceknadh/listmonk
- open sourceBillionmail/BillionMail
Integrity checks
What held up, and what did not.
