An owned email stack — no vendor lock-in
Jessy Mariau
Most newsletters live inside Beehiiv, Mailchimp or ConvertKit: your list, your sends, your deliverability — all on someone else's platform, at their price, under their rules. That's fine until it isn't.
The Model — a motion site with an owned newsletter behind it
So I built the stack instead
The Model runs its own email system end to end. Signups capture into Postgres/Supabase; sends go out through Resend — no third-party ESP in the middle. The list is a table I own outright, and the send path is code I control, not a plan on someone else's roadmap.
The issue system
Owned, not rented
Live at themodel.one — a V4 motion site with a real, owned newsletter behind it. Zero vendor lock-in, by construction rather than by promise.
The same owned-infrastructure pattern frees any newsletter from the platforms it's currently renting.
Like this project
Posted Jul 12, 2026
A newsletter stack with no Mailchimp, no Beehiiv and no monthly ransom as the list grows. Subscribers live in Postgres, Resend does the sending, and the whole thing is portable — because the list is the asset and it shouldn't sit inside someone else's product.
