Thirteen templates, already in your repo
Every scaffold ships 13 production React Email + Tailwind templates — TypeScript components you own, not rows in our database. Edit them in your editor, preview them in Studio, review them in a PR.
Activation
4 templates
Conversion
3 templates
conversion-usage-milestone
ConversionThe upgrade ask, timed to the moment of value.
conversion-trial-expiring
ConversionDays-left honesty without countdown theatrics.
Retention
2 templates
Reactivation
2 templates
reactivation-final-nudge
ReactivationThe last email before you stop sending. (And you should stop.)
Churn prevention
1 template
churn-payment-failed
Churn preventionDunning that sounds like a person, not a billing system.
Feedback
1 template
Components in, HTML out
Everything between your editor and the inbox is engine plumbing. Email guide → Transactional email API → Studio →
Your editor is the editor
Templates are React Email + Tailwind components in src/emails/ — edit them like any component. Studio previews them with live props and per-template stats. It doesn't edit them. Your editor does — that's the point.
The engine does the plumbing
The engine renders React → HTML, rewrites links for first-party tracking, checks preferences, then hands plain HTML to your provider.
Send from a journey or the API
Send one from a journey with sendEmail(), or transactionally via POST /v1/emails.
Thirteen templates, one command
The scaffold puts all 13 templates — plus 10 journeys, Docker, and env — in a repo you own. Edit the first one tonight.
pnpm dlx create-hogsend@latest my-appFree to self-host · One scaffold command · No per-contact billing