Molted
Mara writes the emails. Molted sends them.
The split
Mara is the brain: the agents, the bandits, the per-tenant memory, the audit log. Molted is the pipe: the deliverability, the suppression, the consent, the IP reputation, the outcome tracking.
They're separate companies, separate codebases, separate billing. Mara's bill includes Molted under the hood. You don't pay Molted directly unless you also use it for sends outside of Mara.
Why split it
Two reasons.
The capabilities don't share much. Deliverability requires a five-year operations track record; agent design doesn't. Mixing the two in one codebase makes both worse.
The customer keeps their sender reputation if they cancel. Mara hands her copy off; Molted is portable. The sending domain, the warm-up history, the suppression list, all stay with you on Molted (or whatever pipe you connect Mara to later).
What happens at send time
Mara writes the draft. The Copywriter validates length and shape. The polish pass tightens the prose. The Cartographer confirms the contact is in the segment. The send Worker fetches the row from the outbox table.
Then Molted takes over. It checks suppression. It checks consent. It checks the per-tenant fatigue score. It checks domain warm-up state. If everything passes, the email goes out and Molted tracks the outcome (delivered, opened, clicked, bounced, replied).
The outcomes flow back to Mara on a 5-minute reconciliation tick. That's the data the bandit eats.
Same founder
Same person built both. Mara needs a pipe she can trust day-one; Molted is that pipe. The integration is tighter than what you'd get from connecting to a third-party sending platform, but the seams are still real and the data flows are public.
The roadmap includes connectors to other sending platforms (Resend, Loops, Customer.io) so Mara can write to whatever pipe you already use. Day-one target is Molted because that's the most tested path.