Changelog tools for a small product, compared

A changelog is the cheapest kind of marketing a small product has. It is also the first thing that goes stale, because writing it is a separate act from shipping. The tools below differ less in what the page looks like than in who writes it and from where.

Two kinds of tool

Dashboard-first. Beamer, AnnounceKit, Noticeable and LaunchNotes are built for someone opening a web app, writing an update, choosing a segment and a widget format, and pressing publish. They add popups, banners, NPS surveys, feature-request boards and roadmaps around the changelog. The widget is the product: unread badges, read state across devices, many display formats.

Code-first. A tool where the changelog is an API and the page is a consequence. Nordva Launch is in this group: an entry is a POST with a title and Markdown, from your CI, a GitHub release, a script, or an AI coding agent that has read your commits. The hosted page, the widget, the email to subscribers and the RSS, Atom and JSON feeds all follow from that one call.

Headway sits between: a hosted page and a widget with a generous free plan, written in a dashboard, with no documented API.

The tools, briefly

Beamer has the widest surface: changelog page, in-app widget, popups, banners, top bars, and feedback boards, roadmap and NPS sold as add-ons. Its free plan has no API; the Starter plan does, with a monthly request quota. It is bundled with Userflow, so it makes sense for a team that also wants product tours.

Headway is the simplest. Unlimited changelogs on the free plan, a public page, a widget, custom categories. Pro adds a custom domain, whitelabel, scheduling, a private changelog, and Slack and Twitter integrations. Nothing is published from code.

Noticeable is strongest on the in-app side: a widget with unread badges and cross-device read state, per-label email preferences for subscribers, segmentation and scheduled or expiring publications. The GraphQL API starts on the Growth plan.

AnnounceKit has ten or more widget formats, email, Slack, RSS and webhooks on every plan, feature requests with voting, a roadmap, and an MCP server. No per-seat fees. No free plan, a 15-day trial.

LaunchNotes is a release-communication suite for product-marketing teams: multi-channel announcements, a public roadmap, SOC 2, SSO, a GraphQL API and an MCP server, billed annually after a demo call.

Nordva Launch is the code-first option. Entries are Markdown over REST, can be scheduled, and appear on a hosted page at launch.nordva.dev/log/<slug> or on your own domain (Builder), in a script-tag widget, and in three feeds. Subscribers get an email on Indie and up. A GitHub Action publishes a release’s notes as an entry. The MCP server has the whole lifecycle, and the draft_changelog_from_commits prompt has an agent write the entry from your git log. The same key runs a waitlist, feedback and notifications, so there is one bill, not four. There are no popups, banners, segments or a roadmap.

How to choose

Your situation	Pick
A marketer writes updates and wants popups, banners, NPS and boards from one vendor	Beamer or AnnounceKit
You want a hosted page and a widget for free and will write in a dashboard	Headway
The in-app widget, with read state and per-label email preferences, is what you are buying	Noticeable
A product-marketing team with SSO and compliance requirements	LaunchNotes
Updates should come from CI, GitHub releases or an AI agent, with subscribers and feeds, next to a waitlist and feedback	Nordva Launch

Publishing from code, so the changelog does not go quiet

The failure mode of every changelog is silence. Whatever tool you pick, the fix is the same: make publishing a side effect of shipping. Three ways, from least to most automatic.

From a script. Any tool with an API can be called from a release script. With Launch, the whole call is:

curl -X POST https://api.nordva.dev/v1/changelog/entries \
  -H "Authorization: Bearer $NORDVA_SECRET_KEY" \
  -H "Idempotency-Key: v1.4.0" \
  -H "Content-Type: application/json" \
  -d '{ "title": "Dark mode", "body_markdown": "…", "category": "feature", "notify_subscribers": true }'

An entry without scheduled_at is published at once; with it, the minute cron publishes it at that time.

The Idempotency-Key is the tag name, so a re-run of the script cannot create a second entry.

From a GitHub release. One step in a workflow that runs on release: published posts the release notes as the entry. The release id is the idempotency key. The YAML is on the use-case page.

From an agent. With the MCP server connected in Claude Code or Cursor, ask for a changelog entry. The draft_changelog_from_commits prompt reads the git log since the last published entry, keeps what a user would notice, drafts in the tone of your earlier entries, and publishes only when you say so. The guide on publishing from Claude Code or Cursor walks through it.

Who should not use Launch for this

If your users need a rich in-app experience (unread badges, segments, expiring posts) or your team wants popups and banners, the dashboard-first tools do that and Launch does not. If you only ever need a page and a widget and have no wish to publish from code, Headway’s free plan is hard to argue with.