ADR 14: Newsletters as a product — one studio, an engine per client
Status: adopted (2026-07-29)
Context
Backpack sells a newsletter service. The engine is self-hosted Listmonk relaying through Amazon SES (50k/day granted, raised on request). David wants a fully owned, Beehiiv-class experience without forking the engine (ADR 12 logic: never adopt an upstream codebase’s maintenance tax when a layer on top owns the experience).
Decision
- Campaign Studio (Backpack-Ops/campaign-studio) is the only surface humans touch: brand kits extracted from admired emails (reallygoodemails.com as muse, style tokens only, never another brand’s content), themed MJML blocks, AI-drafted campaigns, visual composer, send flow, stats.
- Engine per client. Each client gets their own Listmonk container on ops-1 with its own database, behind the studio’s engine registry (client -> url, token, sending domain). Same isolation pattern as Hermes profiles (ADR 13) and per-client trust walls (ADR 11). The shared campaigns.backpackops.com instance is registry entry #1, Backpack’s own newsletter.
- Clients send as themselves. Per-client SES domain identity with DKIM published via our DNS APIs (Cloudflare fleet token, Spaceship). Heavy senders graduate to dedicated SES configuration sets or their own SES account without affecting the fleet.
Consequences
- COGS is SES ($0.10 per 1,000 sends) plus marginal VPS. Strong margins against Beehiiv/Mailchimp price anchors.
- The pitch includes data ownership: a client’s list lives in their own database and leaves with them.
- Listmonk upgrades stay trivial (untouched upstream images).
- A newsletter-service provisioning playbook (container + SES identity + DKIM + registry entry) is the unit of client onboarding.