Newsletters · checked 2026-10-19

Can I vibecode Buttondown?

KINDA· weekend project

Writing in Markdown, keeping a subscriber list, confirming addresses and sending an issue to a few hundred people is a short build; an agent does it in an evening on top of Amazon SES, Postmark or Resend. The weekend goes on what makes email arrive and stay legal: double opt-in, unsubscribe, bounce and complaint handling, authentication records on your domain, and a sender that lets you send. Paid subscriptions, automations and imports from other platforms are further weekends.

$9/moprice

$108you'd save a year

weekendbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyIntermediate · Some system setup or keys.

TimeAn evening for the tool; a day or more for SES approval

Claude Code, Codex or CursorAny of them can run the prompt.
Python 3.12A virtual environment keeps the dependencies tidy.
An Amazon SES accountNew accounts start in a sandbox; request production access and wait for AWS to approve it.
A public addressReaders must reach the signup and unsubscribe pages, and AWS must reach the bounce endpoint.

Before you buildButtondown is free up to 100 subscribers, so under that size there is nothing to replace. Self-hosting listmonk or Keila may beat a build for larger lists.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a small newsletter tool to replace Buttondown for a list under 1,000 subscribers. Requirements:

- Python 3.12: FastAPI with Jinja2 templates, run with `uvicorn app:app` on http://127.0.0.1:4890.
Public pages are /subscribe, /confirm/<token>, /unsubscribe/<token> and /archive; the admin lives
under /admin behind one password in .env.
- Storage: SQLite through SQLModel in ./data/news.db for subscribers (email, status, confirmed_at,
tags), issues (slug, subject, markdown, status, sent_at), deliveries (issue, subscriber, SES
message id, status) and a suppression list.
- Writing: a split-pane Markdown editor in /admin with a live preview. Render with `markdown-it-py`
(tables, footnotes), inline the CSS with `premailer`, make a plain-text alternative, and send a
test issue to my own address before any real send.
- Signup: double opt-in. The form sends a confirmation link valid for 3 days and only confirmed
addresses receive issues; rate-limit the form per IP and add a honeypot field.
- Sending: Amazon SES through `boto3`, with AWS keys and SES_FROM in .env, at most 14 messages a
second, `List-Unsubscribe` and `List-Unsubscribe-Post` headers and one unsubscribe link per
recipient. A crash mid-send must never email anyone twice (unique key on issue and subscriber)
and the job resumes where it stopped.
- Bounces and complaints: an endpoint at /ses/events that verifies the SNS signature, confirms the
subscription itself, and suppresses hard bounces and complaints.
- Archive: published issues render at /archive/<slug>, with an Atom feed at /archive/feed.xml.
- Import and export: CSV in (email, tags, optional confirmed date); CSV out of subscribers, and
issues out as Markdown files with front matter.
- Single author. No reader accounts, no tracking pixels or link rewriting, no telemetry; the only
outbound traffic is to AWS.
- Out of scope: paid subscriptions, automations, segments beyond tags, open and click analytics.
- README: SES setup (verify the domain, add DKIM, request production access: AWS reviews it, so do
not expect to send the same day), the SNS topic and HTTPS endpoint, and the footer rules that
CAN-SPAM and GDPR expect (a postal address and a working unsubscribe link).

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Buttondown.

Add an importer to the newsletter tool in this folder. Requirements:

- A command `news import --from substack|kit|csv <file>` that reads the platform's
  subscriber export (email, subscribed date, status) and maps it to subscribers.
- Import only addresses that were active and confirmed on the old platform; skip
  unsubscribed, bounced and complained addresses and put them on the suppression list.
- Print counts of imported, skipped and duplicate rows before writing; support `--dry-run`.
- Keep the original subscription date as confirmed_at.
- Update the README.

Add a link digest draft to the newsletter tool in this folder. Requirements:

- A /admin page with a box where I paste URLs, one per line, each with an optional note.
- A command that fetches each page title and meta description (10-second timeout, no
  JavaScript) and builds a Markdown draft: a heading per link, my note, the description.
- The draft opens in the normal editor; nothing is sent automatically.
- Update the README.

Add a sponsor block to the newsletter tool in this folder. Requirements:

- A sponsor table (name, text, URL, start and end date, impressions sent).
- A Markdown shortcode `{{sponsor}}` that inserts the active sponsor's text and link, marked
  "Sponsored", at render time; if none is active, render nothing.
- Count how many emails each sponsor was in, and show it on a /admin page that exports CSV.
- No link rewriting or click tracking.
- Update the README.

What you lose

Paid subscriptions through Stripe
Automations, tagging and segmentation, and multiple newsletters under one account
Open and click analytics, comments and surveys, sponsorships
Free migration help and import guides for other platforms
An API with a CLI, webhooks and integrations kept up by someone else

Why people still pay

A newsletter list is the asset, and writers want it to send reliably without becoming email engineers. Buttondown charges mostly by active subscribers, lets you pick add-ons, and says it is profitable and self-funded. For a few hundred readers, $9 a month is cheap insurance against a bad deliverability week.

Moatinfrastructure scale compliance & regulation switching costs

Do the math

Buttondown or your own copy?

Over

Your usage

Count my time12h ×$/h

Buttondown, 1 yr$108

Your own copy, 1 yr$50running + build session

You keep$59pays for itself in 2 months

Estimate · SES charges per message sent, which is cents at this size; a small VPS adds about $5. The build is token usage on your agent plan.

Leaving Buttondown

Take your data, then cancel.

1 · Take your data out of Buttondown

1Subscribers: open the Subscribers tab, optionally select some, and click Export in the top right. You get a CSV with ID, email, notes, type, referrer, UTM fields, dates, IP address, tags and metadata; a long export is emailed to you.
2Emails: open the Emails tab, select the issues (or none for all) and click Export. You get a CSV with ID, subject, publish date, source, type and slug, plus a folder with each email's body as a Markdown file.
3Newsletter settings, templates and automations have no export described in the docs we read: note them down or take screenshots.

2 · Cancel Buttondown

1Open the billing page (buttondown.com/settings/billing) and cancel the subscription; the old pause option no longer exists.
2After cancelling you keep access to everything except sending: you can still collect subscribers, edit emails and manage archives, and archives are kept.
3You can reactivate from the billing page at any time.
4To remove everything, go to Settings, Danger Zone and click Delete your account; it removes your data from Buttondown's servers immediately and permanently, so export first.

Snooze (Settings, Danger Zone) is not a cancellation: a snoozed newsletter loses public archives and can't take new subscribers.
The base price assumes at most one email a day to your whole list.
Export subscribers with their dates and statuses so the next platform doesn't have to re-confirm people who already confirmed.
Keep the old signup form and archive links alive, or redirect them, until the new tool is sending.

Checked 2026-10-19 against Buttondown's docs: 1, 2, 3, 4, 5

The escape hatch

Don't feel like building it? These are already free.

listmonkOpen sourceAGPL-3.0 single-binary mailing list and newsletter manager with lists, campaigns and templates; you bring the SMTP or SES sender.★ 24k · active Oct 2026 · docker to self-host
WebVisit ↗GhostOpen sourceMIT publishing platform with built-in newsletters and paid memberships; heavier than a mailing tool but includes the site.★ 56k · active Oct 2026 · docker to self-host
WebVisit ↗KeilaOpen sourceAGPL-3.0 newsletter tool with a campaign editor, forms and segments; sends through your own SMTP or SES account.★ 2.2k · active Oct 2026 · docker to self-host
WebVisit ↗

All 4 free alternatives to Buttondown ›

The numbers

Buttondown pricing

Plan	Monthly	Annual, per month	What you get
Free (up to 100)	$0	$0	Up to 100 subscribers; Markdown or rich-text editor, sending from a custom domain, hosted archives.
Up to 1,000 subscribers	$9	$7.50	Same base features, priced for up to 1,000 active subscribers.
Up to 5,000 subscribers	$29	$24.17	Priced for up to 5,000 active subscribers.
Up to 10,000 subscribers	$79	$65.83	Priced for up to 10,000 active subscribers.
Up to 20,000 subscribers	$139	$115.83	Priced for up to 20,000 active subscribers.

Free tier: 100 subscribers. Prices assume at most one email a day to the whole list; more than that needs a usage-based quote.
Billing: Monthly, or annually at ten times the monthly price (two months free). You pay for active subscribers, not every contact. Cancelling keeps your subscribers, drafts and archives but stops sending; you can reactivate from the billing page. Registered non-profits get 50% off.
Hidden costs: Features sit in add-ons on top of the subscriber price: tagging and segmentation, paid subscriptions, comments and surveys, analytics, RSS-to-email and attachments are $9 each a month; sponsorships, custom-domain archives, multiple newsletters and automations are $29 each; whitelabeling and teams are $79 each. Segments, paid subscriptions and analytics together add $27 a month.
Source: buttondown.com

Also on the list

Kit (formerly ConvertKit)$39/mo · NewslettersKINDA

MailerLite$12/mo · NewslettersKINDA

beehiiv$59/mo · NewslettersKINDA

Questions

Buttondown, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Free for your first 100 subscribers, with a rich-text or Markdown editor, a custom sending domain and hosted archives.

Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: Paid subscriptions through Stripe, Automations, tagging and segmentation, and multiple newsletters under one account.

About $9 a month on the Up to 1,000 subscribers plan, $108 a year (checked 2026-10-19).

Paid subscriptions through Stripe; Automations, tagging and segmentation, and multiple newsletters under one account; Open and click analytics, comments and surveys, sponsorships; Free migration help and import guides for other platforms; An API with a CLI, webhooks and integrations kept up by someone else. If any of those matter to you, keep paying.