Release notes and changelog software.

Changelog software publishes a dated history of product updates, fixes and improvements where customers can find it. Gleap keeps that history in the feedback portal on your domain and in the widget's News tab, emails subscribers when an entry is published, and can show it as an in-app pop-up.

Both use the same editor. A changelog is part of the public release history: it appears on the feedback portal, in the widget and in subscriber emails. News is an in-app announcement, a tip, an event or a company update, shown in the widget and as a pop-up without an entry on the portal.

Customers subscribe to the changelog on your feedback portal. With "Send email to subscribers" on, the first publish of a changelog emails them with your email template. The subscriber list is visible in the dashboard.

Yes. Turn on the in-app pop-up for a changelog or news item and it appears bottom-right in your app with the cover image, title and preview. You choose the audience and page rules, and news can send a push notification as well. To point people at an entry, use an in-app banner or an info card.

Yes. Suggest changelogs scans the merged pull requests of your connected repositories and the feature requests released since your last changelog, then proposes entries in your existing style. You refine them with presets like Shorter or Detail and create a draft; nothing is published until you publish it.

Yes. Released requests are a source for changelog suggestions, and an update posted in a released request is emailed to everyone who voted. The changelog sits next to the requests and the roadmap on the same portal. See the public roadmap and Gleap's customer feedback software.

No. A merged pull request seeds a draft; your team publishes it. Kai Code's customer follow-up is a separate step: by default it waits for a teammate to confirm the fix is live, or it uses a delay you set after the merge. See how the loop closes.

Yes. Reactions and comments on changelog entries are visible in the dashboard, with a Comments tab per entry and the most-reacted entries on the feedback portal overview.

Yes. Pin a changelog or news item to the top of the list, set a future publish date so it goes live on schedule, and set a stop date for the in-app pop-up.

Yes. Changelogs use your portal domain, logo and header design, the email uses your email template, and titles and content can be localized per language with AI translation in the editor.

Views of news and changelog pop-ups over a date range, plus reactions and comments per entry. Survey responses after a release live in in-app surveys.

Gleap publishes the changelog on your portal, in the widget, by email and as an in-app pop-up, next to feature requests and support. Compare Gleap vs Beamer, Gleap vs AnnounceKit and Gleap vs LaunchNotes.

Yes. An agent connected to the Gleap MCP server drafts news and changelog entries with cover images in every language you publish, targets them by contact attributes and events, and checks how many people match. Agents that work in your code, such as Claude Code or Codex, can write the entry from what shipped. Drafts wait for your review.

Changelogs, news, the rest of outbound messaging and the custom portal domain are included from Team ($149 per month, billed annually). See pricing.