Should you build your own Buttondown?
Send Markdown newsletters from a small list with archives and simple automations
The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Buttondown, send Markdown newsletters from a small list with archives and simple automations. The hard boundary is excellent deliverability, hosted simplicity, integrations, and creator-friendly support, plus deliverability, growth network, and integrations.
ENOriginal research content in English. Original prompt preserved in English.
Build a personal replacement for Buttondown in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Amazon SES; do not offer alternative stacks.
The core loop is: collect subscribers to a small list, compose and send compliant Markdown newsletters with simple automations, publish a web archive, and report basic delivery and click events.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement subscriber import, double opt-in, unsubscribe, suppression, tags, and consent timestamps.
Create a Markdown campaign editor with HTML and plain-text previews.
Queue sends through SES with retries, rate limits, idempotency, and resumable batches.
Process delivery, bounce, complaint, open, and click webhooks without logging message content.
Publish a simple issue archive and subscriber preference page.
Add test sends, seed-list checks, DNS setup guidance, exports, and backups.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a newsletter recommendation marketplace.
Deliberately leave out ad sales and payment infrastructure.
Deliberately leave out complex lifecycle automation and enterprise deliverability support.
Finish by running the tests and listing the exact commands used.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
Collect subscribers to a small list, compose and send compliant Markdown newsletters with simple automations, publish a web archive, and report basic delivery and click events.
What you will need
- Amazon SES account
- verified sending domain
- PostgreSQL
- public HTTPS deploy target
- DNS access
People still pay for Buttondown because newsletter operators pay for inbox placement, growth mechanics, and operational confidence on publication day. The recurring cost buys DNS authentication, reputation, bounces, complaints, unsubscribe compliance, templates, queues, analytics, backups, and support, not just the visible interface.
xexcellent deliverability, hosted simplicity, integrations, and creator-friendly support
xinbox-placement expertise
xadvanced automations
xcommerce integrations
xrecommendation and ad networks
How much does Buttondown cost?
- Monthly billing
- $9/mo$9/mo
- Per year
- $108/yr$108/yr
- On a Brazilian card, with 3.5% IOF
- R$47.03/moR$564/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Buttondown’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| free first 100 subscribers | $0/workspace | $0/workspace | First 100 subscribers cost $0. |
| subscriber-based base plan | custom | - | Base cost is determined by subscriber calculator; exact public numeric schedule was not exposed in crawled text. |
| small add-ons | $9/workspace≈ $9 | - | $9/mo each: tagging/segmentation, paid subscriptions, comments/surveys, analytics, RSS-to-email, sponsorships, attachments. |
| medium add-ons | $29/workspace≈ $29 | - | $29/mo each: custom-domain archives, multiple newsletters, automations. |
| large add-ons | $79/workspace≈ $79 | - | $79/mo each: whitelabeling, teams. |
Free tier$0 for the first 100 subscribers.
Billing termssubscriber-based calculator plus monthly add-ons; annual terms not verified
Additional costsCore capabilities are modular add-ons: $9/mo, $29/mo and $79/mo items can stack on top of subscriber pricing.
verified 2026-08-10 · source ↗
Is it cheaper to build or buy Buttondown?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (multi-day). Does not price what you give up (support, integrations, security).
Can I rebuild Buttondown?
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal Buttondown replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does Buttondown cost?
Buttondown costs about $9/mo (Basic, checked 10/20/2026), which is $108 per year. That’s what you save by replacing it with one prompt.
What do I lose by replacing Buttondown?
Honestly: excellent deliverability, hosted simplicity, integrations, and creator-friendly support; inbox-placement expertise; advanced automations; commerce integrations; recommendation and ad networks. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Buttondown?
Yes: Listmonk (Mature open-source newsletter and mailing-list manager.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.