Moosend

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me the newsletter platform that replaces Moosend.

**Rent the delivery, own everything else.** That is the shape of every honest answer in this category, and the layer above the relay is a weekend.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode
- MJML for templates, a relay provider for delivery
- Caddy in front

THE DATA MODEL
- subscribers: id, email, name, attrs_json, status, source, confirmed_at, unsubscribed_at, created_at
- lists and memberships, so somebody can be on several
- campaigns: id, subject, preheader, template_id, template_version, list_query, scheduled_for, sent_at
- sends: id, campaign_id, subscriber_id, sent_at, provider_ref, status
- events: id, send_id, kind, at — delivered, bounced, complained, clicked
- suppressions: address_hash, reason, at — **permanent, and checked before every single send**

SENDING PROPERLY
- Everything queued with retries and a dead-letter list; never send inside a web request
- Idempotency per campaign per subscriber, so a retried batch does not send twice
- Throttle to the relay's limit, and spread a large send over time rather than firing it all at once
- **A test send to yourself that renders exactly what subscribers get**, including the unsubscribe link and the personalisation, with a real subscriber's data

THE TEMPLATE
- MJML, which handles the client quirks that make hand-written email HTML miserable
- **A plain text alternative on every message**, generated and editable. It improves deliverability and it is what some people actually read
- Personalisation with a default for every field — 'Hello ,' is the classic and it is entirely avoidable by requiring a fallback
- Dark mode considered: a logo that disappears on a dark background is the most common broken email of the last few years

COMPLIANCE, WHICH IS NOT OPTIONAL
- Confirmed opt-in with the time, the IP hash and the source recorded. **That record is your defence if anybody complains**
- One-click unsubscribe headers as well as a link, now expected by the large providers
- Unsubscribe honoured immediately and permanently, across every list
- A postal address in the footer where the law requires it

REPORTING WORTH TRUSTING
- Delivered, bounced, complained and clicked. **Treat opens as unreliable** — privacy proxies pre-fetch images and inflate them by an unknown amount
- Click map per campaign, which tells you what people actually wanted
- Bounce split by hard and soft and by receiving domain, so a provider-specific problem is visible

LIST HYGIENE
- Stop sending to anybody with no click in six months, and say so in the interface. It is the cheapest deliverability improvement available

WHAT MATTERS MOST
Permanent suppression, confirmed opt-in records, and a plain text alternative. Those three are the difference between a newsletter and a deliverability problem.