Votelantern

Changelog software for small software teams

A changelog is the page where you tell customers what changed in your product. Done well, it answers three questions for the reader: what is new, does it affect me, and did you fix the thing I complained about. Changelog software gives you that page without building it yourself, and the better tools connect it to the requests people sent you, so the people who asked hear back when the work ships.

This page covers what a changelog tool should do, which feedback-board vendors include one on which plan, and how Votelantern's changelog works. For an example changelog, and a sample "what's new" panel as it would appear inside your app, see the changelog template page.

What a changelog tool should do

Before comparing vendors, decide what the page is for. A changelog read by customers is a different thing from a commit log read by engineers. If your readers are customers, look for these five things.

  1. Entries written for people, not for the repository. Each entry needs a plain title, a sentence on why it matters, and short groups such as New, Improved and Fixed. Version numbers are optional.
  2. A link from each entry to the requests it delivers. This is the feature that separates a feedback tool's changelog from a blog. When an entry names the requests it closes, the tool can tell the voters.
  3. Notifications people chose. Emails should go only to people who opted in, with an unsubscribe link in every one.
  4. An in-app panel. Customers who never visit your site still see what changed when a small "what's new" panel opens inside the product.
  5. A public page you can link to. Sales and support staff can point to it instead of rewriting the same news in every reply.

A standalone changelog tool may do the first, third, fourth and fifth well. Only a tool that also holds your feature requests can do the second, because it knows who asked for what, and that is also what lets it email the right voters.

Which plans include a changelog (rival facts)

The table lists what each vendor's own pricing page said about its changelog and in-app widget, read on each rival's own page, 10 November 2026. Where a page said nothing, the table says so. Four more vendors (Frill, Nolt, Feature Upvote and Convas) refused our fetcher, so they aren't listed.

Vendor Changelog In-app widget
Canny All plans Free plan and up
Featurebase All plans, including a public changelog page on Free Growth plan and up
Upvoty Super and Hyper (not listed on Power) Not stated on the pricing page
Fider Not stated on the pricing page Not stated on the pricing page
Sleekplan All plans All plans (JavaScript SDK, including Indie)
UserJot All plans Not gated on the page
FeatureOS All plans Starter and up
Rapidr All plans Startup and up
Supahub Offered; which plan isn't stated Starter and up (changelog and feedback widgets)
ProductLift All plans Not stated on the pricing page
FeedBear All plans Lite and up
Productboard Not stated Embedded portal on Business
Votelantern Free plan and up Free plan and up

What the table shows: a changelog is close to standard in this category. The differences sit elsewhere, in what the changelog is connected to and what you pay to remove the vendor's branding. If you only need a changelog, several free plans will do. If you want the changelog to close the loop with the people who asked, check that the tool links entries to requests and emails voters.

How Votelantern's changelog works

Prices may change before launch: Free, $0; Team, price not set yet; Business, price not set yet. On Team the badge can be removed, and you can put the changelog on your own domain.

The release notes template page shows three fictional releases for a made-up dance studio app. Opened in Votelantern, they become draft entries on your changelog.

Open this in Votelantern

If your readers are developers who want version numbers and fixed headings, a stricter layout suits them better. The changelog template page shows a versioned changelog for a fictional time-off tracker, with changes sorted under fixed headings, newest first.

Open this in Votelantern

Writing a changelog entry customers read

The tool matters less than the writing. A few habits help.

For a fuller guide to structure, see the release notes template and the changelog template. If you are still choosing a request board, the feature request software page compares what vendors gate by plan.

Free changelog software: what to check

Several vendors in the table offer a changelog on a free plan, and so does Votelantern. Before you settle on any free plan, check three things.

FAQ

Is a changelog the same as release notes? They overlap. Release notes usually describe one release in detail; a changelog is the running list of all of them. In Votelantern, each changelog entry can serve as the release note for that release.

Can the changelog show inside my app? Yes. The widget's "what's new" mode opens your latest entries in a panel, and it works on the free plan.

Do voters get an email every time I publish? No. Only voters on the requests linked to that entry get an email, and only if they opted in to updates.

Do I need a feedback board to use the changelog? No, you can publish entries without linking anything. The link to requests is what lets the changelog notify voters.

All templates and guides