Skip to main content

Newsletter — Listmonk (vs Ghost)

Decision (answers notes #7 "ghostjs or custom?"): use self-hosted Listmonk for bulk newsletters, with content authored in Payload (CMS). Ghost is not adopted.

Why not Ghost​

Ghost bundles blog + newsletter + memberships, but:

  • Multilingual is a hard requirement; Ghost i18n is weak, Payload localization is strong.
  • Ghost is a separate app + DB + admin, fighting our per-tenant + RBAC model.
  • We already have a blog (Payload) and transactional messaging (Notifications). Ghost's unique value (native newsletters) is covered by Listmonk — open-source, self-hostable, high-volume.

So Ghost would add a parallel CMS we don't need. See Tech-Stack Rationale.

Architecture​

  • Authoring in Payload (localized blocks) → rendered to an email-safe template.
  • Audiences from CRM segments synced to Listmonk lists.
  • Send + analytics (opens/clicks/bounces/unsubs) in Listmonk; metrics surfaced to BI.
  • Compliance: double opt-in, unsubscribe, suppression handled by Listmonk.

Division of labor​

ConcernOwner
Blog/article contentPayload
Newsletter content authoringPayload (→ template)
List management + sending + email analyticsListmonk
Transactional messages (order/service/AMC)Notifications
Segments/audiencesCRM → synced to Listmonk

Tenant config​

Listmonk URL/API key (secret), SES/SMTP creds, default lists, double-opt-in policy, sender identity/branding.

Open questions​

  • Author newsletters fully in Payload, or allow Listmonk's native editor as fallback?
  • Segment sync cadence (real-time vs scheduled).