# Build brief — a focused alternative to beehiiv

> **Verdict:** Partly, if you narrow it · **Buildability:** 48/100 · **Category:** Newsletter
> **Source:** https://www.canitbevibecoded.com/beehiiv
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from beehiiv. Verify current pricing and capabilities before acting.

## Context

**beehiiv** — Newsletter publishing, growth, monetization, and email platform. It currently costs $49/mo.

You can build a newsletter CMS and send emails, but beehiiv's moat is deliverability, growth network, recommendations, ad marketplace, automations, analytics, and migrations.

This brief describes a focused, single-operator replacement for the part of beehiiv that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Create posts, maintain subscribers, send campaigns through an email provider, publish web archive, and show basic analytics.

- Compose, segment, preview, and queue a small newsletter workflow.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Email service provider.
- Domain/DNS auth.
- Database.
- CMS/editor.
- Unsubscribe/compliance.
- Hosting.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a personal newsletter system to replace beehiiv. Requirements:

- Node + Express + better-sqlite3. Posts are Markdown files in posts/;
  subscribers live in SQLite: email, token, subscribed_at, unsubscribed_at.
- A localhost admin page: write and preview a post (marked, rendered inside
  a tested single-column email HTML template), see subscriber count, send.
- Sending via Resend or plain SMTP, creds in .env. Every email carries a
  one-click unsubscribe link (token in the URL) and a List-Unsubscribe
  header; that is a legal requirement, never skip it.
- Log each send per subscriber as sent or failed so an interrupted batch
  resumes without double-sending anyone.
- Public surface, deployable as one small server: a subscribe form with a
  double-opt-in confirmation email, and a web archive of past posts at
  /archive.
- CSV import and export of the subscriber list.
- Out of scope: open/click analytics, referral programs, and paid
  subscriptions; beehiiv's growth network is the actual product.
- README: .env keys, the ESP's SPF/DKIM DNS records, and a blunt warning to
  warm up a new sending domain slowly or everything lands in spam;
  deliverability is most of what the fee buys.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Email deliverability.
- Referral/recommendation network.
- Ad network.
- Automations.
- Reliability at the vendor's scale is an operations problem, not a prompt.
- The value comes from the people already using it.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Ghost](https://github.com/TryGhost/Ghost) — Open-source publishing/newsletter platform with memberships and email support

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/beehiiv