Ship it, publish it once, and let everyone see it
DeskCrew ships a public changelog with an in-widget "What’s new" tab: publish once and every visitor sees it on your site, on your board, and in the chat launcher, free to start.
Last updated: July 2026
How does the changelog loop close?
One publish, three surfaces
Your hosted changelog page, the public board, and the widget’s "What’s new" tab with an unread badge. Users notice releases without you writing three posts.
Closes the feedback loop
Requests voted on your board move through the roadmap and end as changelog entries, so the customers who asked can see it shipped. That visibility is what keeps boards alive.
Automatable
Create entries via the REST API with a scoped key from your release pipeline, or let your own AI tooling draft entries for review through the same door.
Changelogs, asked and answered
What is a changelog tool?
A place to publish product updates your users actually see: a public page, plus in-app surfacing so shipped work gets noticed instead of buried in a blog nobody visits.
Where do updates appear?
Three places from one publish: your hosted changelog page, your public board, and the "What’s new" tab inside the chat widget on your site, with an unread badge on the launcher.
Is it free?
Yes. The changelog, the board, and the widget are all on the free plan. Paid plans add custom domains and white-labeling.
Can it close the loop with feedback?
That is the point of having them together: a request on your feedback board moves through the roadmap, and the shipped entry lands in the changelog, so the people who asked can see it happened.
Can I publish from the API?
Yes. Changelog entries can be created via the REST API with a scoped key, so your release pipeline or your AI tooling can draft entries for you to publish.