An owned email stack — no vendor lock-in
Jessy Mariau
An owned email stack
Most newsletters live inside Beehiiv, Mailchimp or ConvertKit: your list, your sends and your deliverability all sit on someone else's platform, at their price and under their rules. That's fine until it isn't.
The Model, my own newsletter site, with signups stored in a table I own
So I built the stack instead
The Model is my own newsletter. Signups on themodel.one write straight into a Postgres table on Supabase, with the source and consent time recorded. The list is a table I own outright. For sending, the design pairs it with Resend, an email API that works with any database.
The issue system
Owned, not rented
The list can move anywhere, because it's a Postgres table. The same pattern frees any newsletter from the platform it's currently renting.
Like this project
Posted Jul 12, 2026
A newsletter stack without Mailchimp or Beehiiv, so the bill doesn't climb as the list grows. Subscribers live in a Postgres table I own, and sending pairs that table with Resend, an email API.
Likes
0
Views
10
