I’ve been working on Caveat, a self-hosted publishing tool for people who want control over their newsletter’s design, subscriber data, and infrastructure.
It includes a rich-text editor, autosave, reusable content blocks, publication designs, typography and colour controls, subscriber management, exports, and Resend email delivery. It includes both the editor and public website.
Repo: [https://github.com/CaveatJS/site](https://github.com/CaveatJS/site)
Examples/docs: [https://caveat-home.vercel.app/](https://caveat-home.vercel.app/)
I built the first version over a few hours across three sessions with GPT-6 Astra. I chose the features, tested the workflows, and refined the design and implementation.
The sessions processed roughly 43.6M tokens, about 97% cached input.
Caveat is still early: paid subscriptions, scheduling, and multi-author workflows are not implemented yet.
If you publish a newsletter, what part of your workflow would prevent you from using it today?
Comments URL: [https://news.ycombinator.com/item?id=49605072](https://news.ycombinator.com/item?id=49605072)
Points: 1