Changelogs
that don't suck.
Write product updates in Markdown. Schedule. Tag. Ship. Your customers see one clean feed. Your team sees one clean editor. Nothing else.
A tool for the ship-day brain.
Write fast.
Markdown, slash-commands, paste-friendly. No WYSIWYG nonsense.
Schedule it.
Queue posts for Tuesday 9am. Respect the team timezone.
Tag everything.
feature / fix / api / breaking. Filter on read, group on share.
Public or private.
Per-project visibility. Customers see what you want them to see.
Versioned.
Every post can carry a semver tag. Sortable, searchable, linkable.
Built for ship-day.
Keyboard-first. Press N to draft. Press P to publish.
Teams who'd
rather be shipping.
“We replaced three docs and a Slack channel with one Notch project.”
“Customers actually read this one. The format invites it.”
“Keyboard-first means we stop avoiding writing updates.”
“The scheduling alone earned its keep. Tuesday 9am, every week.”
“Visibility per project. Customers see polish. Internals see the mess.”
“Honestly, the markdown editor is the whole pitch for me.”
Questions,
answered.
Free for one workspace, three projects, unlimited posts. Upgrade when you outgrow it.
Yes. Markdown is the source. Slash commands handle the rest.
Weekly digest per project for subscribers. Daily for breaking changes.
Public projects expose a subscribe form. Email-only, double opt-in.
Yes. Invite teammates by email, assign roles, post under their byline.
Each post takes an optional version tag. We render and link it.
Read API is public on every published changelog. Write API is on the roadmap.
Drafts vanish on delete. Published posts get unpublished and archived.