# Build brief — a focused alternative to Kit

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

## Context

**Kit** — Email marketing and automation platform for creators. It currently costs $39/mo.

A simple newsletter sender is buildable, but Kit's value is deliverability, subscriber forms, automations, recommendations, commerce, migrations, and creator-specific flows.

This brief describes a focused, single-operator replacement for the part of Kit 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

Build subscriber forms, a campaign editor, segmentation, simple automations, and send via an email API.

- 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.
- DNS/SPF/DKIM/DMARC.
- Database.
- Unsubscribe/compliance flows.
- Hosted app.

### 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 tool to replace Kit for a small list. Requirements:

- Node + Express + better-sqlite3 on my VPS. Subscribers, campaigns, sends, and
  events all in one SQLite file.
- A public /subscribe form with double opt-in: signed confirmation link by email
  before anyone is added. One-click unsubscribe link in every footer, no login.
- Compose campaigns in Markdown in the admin UI (bound to localhost or my VPN
  only), preview rendered HTML, send to everyone or to a tag.
- Sends go through Amazon SES or Postmark (key in .env) at a throttled rate, with
  per-recipient status recorded; bounce and complaint webhooks auto-suppress bad
  addresses.
- Tags on subscribers, plus one simple welcome autoresponder: a single email sent N
  minutes after confirmation.
- CSV import and export of the list, so I can arrive from Kit and leave anytime.
- No accounts beyond mine, no telemetry, no tracking pixels by default.
- Out of scope: landing pages, visual automation builders, the creator
  recommendation network, and commerce. This sends email, nothing else.
- README with a blunt warning: deliverability is DNS homework. Walk me through SPF,
  DKIM, and DMARC before the first send, and treat it as its own task.

## 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:

- Deliverability.
- Automations.
- Forms/landing pages.
- Recommendations.
- 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.
- Maintain every third-party integration as APIs and OAuth rules change.

## 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:

- [Listmonk](https://github.com/knadh/listmonk) — Open-source newsletter and mailing-list manager suitable for self-hosted campaigns

---

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