Announce it to the people who asked for it

A changelog with an editor, categories, and a public feed. Publishing notifies everyone who voted for the linked posts — the loop from request to announcement closes itself.

The problem

Shipping in silence

You built the thing they asked for, and they never found out. The release note went into a blog nobody subscribes to, or a Slack channel your customers cannot see, and six weeks later the same request arrives again.

Announcing is not a marketing task, it is the last step of the feedback loop. When the changelog knows which requests a release closes, that step happens by itself.

What you get

Everything in release notes

Notification is the point

Publishing tells every voter on every linked post, plus changelog subscribers. No mailing list, no export, no CSV.

A real editor

Write the note with formatting, images, and links. Categories — New, Improved, Fixed — let readers skim the parts they care about.

Public feed

A hosted changelog on your portal or your own domain, indexable, linkable, and citable from a support reply.

In-app widget

A badged 'What's new' panel inside your product. Customers who never open a release email will click a badge sitting in their toolbar.

Subscribers

Anyone can subscribe to the changelog without an account, and unsubscribe from any email.

Drafts

Write it while the work is in review, publish it the moment it goes out.

Questions

Frequently asked

Your customers already told you what to build

It is in a support inbox, three Slack threads, and a spreadsheet nobody has opened since March. Put it somewhere it can be counted.

No credit card required to start. $0 forever.