ReleasePad
153+ teams using ReleasePad

The changelog app
your users actually open.

Most changelog apps put your updates on a page nobody visits. ReleasePad puts yours where your users already are — inside your product, on a hosted page they can bookmark, and in a Markdown file AI tools can read. One source, drafted from your GitHub commits.

What's New
3 new
New Today

Slack integration is live

Connect a channel and every published release posts to your team's Slack automatically — no copy-paste, no extra step.

Improved 2 days ago

Faster dashboard rendering

Charts and tables now load up to 3x quicker on accounts with lots of history.

Fix Last week

CSV export no longer truncates

Large exports now include every row instead of cutting off at 1,000.

releasepad.io ?markdown=true →
30s
To go live
paste one snippet
3
Surfaces, one source
widget · page · Markdown
$35
Flat per month
no per-seat fees
153+
Teams shipping
indie to scale-up
Definition

What is a changelog app?

A changelog app is software that helps a product team publish and distribute its release notes — the running log of new features, improvements, and fixes — to the people who need to see them. Instead of maintaining a hand-written CHANGELOG.md or a forgotten blog category, a changelog app gives you one place to write an update and then pushes it everywhere it matters: an in-app widget, a hosted public page, an RSS or JSON feed, and increasingly a machine-readable file that AI tools can ingest. ReleasePad is a changelog app built for SaaS teams that drafts those entries automatically from your GitHub commits.

The problem

You ship constantly. Your users have no idea.

A plain text file in your repo is for developers. A blog category nobody subscribed to is a graveyard. Meanwhile the customers paying you have no reliable way to find out what changed — so they assume nothing did.

The repo file is invisible

A CHANGELOG.md is great for engineers and useless to the customer who's wondering whether you ever fixed that bug.

Writing it is a chore

By the time you've shipped, the last thing you want is to translate ten commits into prose. So the update never gets written.

A dead-looking product churns

When users never see movement, the product feels abandoned — and they leave for a competitor that looks more alive.

💡 A changelog app fixes all three: write once, reach everyone, automatically.
One source, everywhere

Write the release once. It shows up in three places.

A changelog app is only useful if the update reaches people. ReleasePad publishes every entry to the three surfaces that actually get read — from a single source you never duplicate.

In-app widget

A 4.3kb embeddable widget that surfaces your updates inside the product, with a per-user unread badge. The one place every user already is.

Explore the widget

Hosted public page

An SEO-friendly changelog page on your own domain that users can bookmark and subscribe to — with RSS and JSON feeds built in.

See the public page

AI-readable Markdown

The same content at a stable ?markdown=true URL so Claude, Cursor, and ChatGPT can answer questions about your product accurately.

Why machine-readable

And you don't write any of it by hand — connect a repo and ReleasePad's release notes tool drafts each entry from your GitHub commits. You edit and publish.

Why a changelog app earns its keep

It's a growth channel disguised as a chore.

A changelog isn't admin work. Done well, it drives adoption, cuts support load, and keeps users from quietly leaving.

Drives feature adoption

Shipping a feature is only half the job. When users see the update in-context, they're far more likely to try it than when it's buried in an email — closing the gap between "we built it" and "they use it".

Cuts repetitive support tickets

"Can it do X yet?" "When's Y coming?" A surprising share of support is about things you already shipped. A changelog app answers those questions before they're asked.

Reduces churn with visible momentum

A steady stream of updates is proof the product is alive and improving. That perception of momentum is one of the cheapest retention tools you have — and one of the most overlooked.

Feeds the AI tools reading your product

Customers increasingly ask Claude or ChatGPT "does this tool do X?" If your changelog is machine-readable, those answers are accurate. If it isn't, the AI guesses. A modern changelog app gets you on the right side of that.

How it compares

Choosing the best changelog app

Most changelog apps give you a page or a widget. Few draft the content for you, and fewer still expose a machine-readable feed for AI tools. Here's how ReleasePad lines up against common changelog software.

Changelog app In-app widget Auto-drafts from GitHub AI-readable Markdown Pricing
ReleasePad $35/mo flat
Beamer Per-MAU tiers
ReleaseNotes.io Tiered
Hand-written CHANGELOG.md Partial Free, manual

Feature comparisons reflect each product's standard plans and change over time — check current docs before deciding. For deeper breakdowns, see our guides to Beamer alternatives and how to write release notes that get read.

Changelog app FAQ

Common questions

Built and maintained by the ReleasePad team · Last updated

A changelog app is software for publishing and distributing your product's release notes. You write an update once, and the app delivers it to the places your users actually look — typically an in-app widget, a hosted public page, and feeds like RSS, JSON, or AI-readable Markdown. ReleasePad adds automatic drafting from your GitHub commits on top of all of that.

A CHANGELOG.md in your repo is perfect for developers reading your source. It does nothing for the paying customer inside your product who never opens GitHub. A changelog app exists to reach that second audience — surfacing the same updates in-app and on a page they can find, without you maintaining two copies.

ReleasePad has a free tier so you can connect a repo, draft your first entries, and embed the widget without paying. The Pro plan is a flat $35/mo per product — no per-seat or per-MAU pricing — when you're ready to ship without limits. See the pricing page for the full breakdown.

Yes. Connect your repository and ReleasePad turns merged commits into draft release notes automatically — you review, edit the wording, and publish. That's the core of the release notes tool built into the app, and it's why teams ship a changelog every release instead of once a quarter.

Yes — that's the in-app widget. It's 4.3kb gzipped, vanilla JavaScript with zero dependencies, and installs with a single HTML snippet that works in React, Vue, Rails, or plain HTML. Each user sees an unread badge when something new ships. The in-app widget page covers it in detail.

Users increasingly ask assistants like Claude and ChatGPT whether a product does something. Those tools answer from whatever they can read. ReleasePad exposes your changelog as Markdown at a stable URL, so AI gives accurate, current answers about your product instead of guessing from a stale crawl.

The terms overlap. "Release notes" usually describes the writing for a single release; a "changelog" is the running history of all of them. A changelog app handles both — drafting each release and maintaining the public, searchable log. If the distinction matters for your team, our guide on changelog vs release notes goes deeper.

Give your shipping a place to live.

Connect a repo, let ReleasePad draft your first release notes, and embed the widget in the next 30 seconds. Free to start, $35/mo per product when you're ready to ship without limits.

ReleasePad changelog app — in-app widget, hosted page, and AI-readable Markdown from your GitHub commits
Try me now!