Key takeaways
- 1AI drafts release note entries directly from GitHub commits and merges, with a draft ready about 12 seconds after a merge in the product's own example; Conventional Commit prefixes are parsed for cleaner grouping when present but aren't required
- 2One approval publishes everywhere at once: a hosted changelog page, a 4.3kb in-app widget (one script tag, live in 30 seconds), and a Markdown feed built for AI assistants to read
- 3MCP server lets Claude, Cursor, or ChatGPT draft and publish entries directly, extending the workflow into tools teams already use
- 4Pro is a flat $35/month per product (unlimited posts, unlimited team members), not per-seat; Free needs no credit card and has no time limit
- 5Every AI-drafted entry needs a human approval before it publishes, with per-draft controls for tone, detail level, and language; there is no auto-publish switch
From GitHub Merge to Published Release Note
ReleasePad connects to a GitHub repo and reads every commit and merge as it happens, using AI to turn code changes into a release note draft within seconds. The product's own example shows a draft ready about 12 seconds after a merge, taking a 44-file merge down to 3 clear update entries; actual timing will vary with repo size and commit volume. There's no commit format to adopt first: Conventional Commit prefixes are parsed for cleaner grouping when they're already there, but ReleasePad doesn't require them, unlike generators such as conventional-changelog or semantic-release that need strict commit discipline to produce good output. That draft lands as a starting point, not a final publish. A human reviews it, edits it if needed, and only then does it go live, so the AI's job is to remove the blank-page problem rather than to make editorial calls unsupervised.
The Three-Step Workflow: Connect, Draft, Approve
The flow has three parts. First, connect a GitHub repo (or write notes directly, or dictate them to an AI assistant through the MCP server). Second, ReleasePad's AI reads the change and writes a draft entry, tagged by category: feature, improvement, or fix. Third, a team member reviews that draft, tweaks it if they want, and publishes. That third step is deliberately manual every time, and it comes with real editing control: tone (professional, casual, technical), detail level, language, and emoji style are all adjustable per draft, and a [skip] tag on any commit keeps noise out of the draft entirely. The product is explicit that there's no auto-publish switch: a draft waits until someone approves it, which matters for teams that want AI speed on the writing side without AI making the unsupervised call on what customers see.
Publishing Everywhere at Once, Including an AI-Readable Feed
One approval pushes the release note to three places simultaneously: a hosted, SEO-friendly changelog page, a 4.3kb in-app widget that goes live with a single script tag and adapts automatically to light or dark mode, and a Markdown version of the feed built specifically to be read by AI assistants and crawlers. That last surface is a genuinely forward-looking touch: as more product discovery and research happens through AI tools, a changelog that's already structured for that is an advantage older changelog tools don't have by default. Teams also get a REST API and webhooks that fire when a post is created, published, or deleted (the published event arrives with an X-ReleasePad-Event: post.published header), for wiring the changelog into whatever else they use to track releases internally.
Flat Per-Product Pricing and the Claude/Cursor MCP Server
Pro runs $35 a month per product, flat, regardless of team size: a 50-person team pays the same as a solo founder, with unlimited posts and unlimited team members included alongside changelog analytics, a custom domain for the public page, and the API and webhook access, plus priority support on top of the direct email support every plan gets. The free tier needs no credit card, carries no time limit, and includes the public changelog page and basic widget, enough to run a full release cadence before paying anything. The MCP server extends the same drafting flow into tools teams already have open: ReleasePad can be reached from Claude, Cursor, or ChatGPT, so describing a shipped change to an AI assistant is enough to get a draft without opening ReleasePad's own dashboard first.
Who Should Bring ReleasePad Into Their Release Process
ReleasePad fits teams that ship through GitHub regularly and don't have anyone whose job is writing about what shipped: early-stage founders, small product teams, and any company running multiple products that benefits from per-product rather than per-seat pricing. The MCP integration also makes it a natural fit for teams already working inside Claude or Cursor day to day. Teams that write release notes from internal planning docs more than GitHub activity will still get full use of the manual editor and the MCP server's ability to draft from a plain-language description, so the GitHub pipeline is a bonus layer rather than the only way in.
Ratings
A single script tag brings the widget live in 30 seconds, and connecting GitHub through the marketplace app is a familiar one-time setup with no webhooks or keys to configure
Flat $35/month per product with unlimited posts and seats undercuts per-seat changelog tools for growing teams, and the free tier needs no card to start
Drafting directly from commits without requiring strict commit formatting, and publishing an AI-readable Markdown feed alongside the usual widget and page, is a distinct combination most changelog tools don't offer
The core drafting and publishing loop, API, and webhooks are well covered; changelog analytics and a custom domain for the public page round out the set on the Pro plan
Support runs through direct email with the founder, with priority support layered on for Pro accounts
Best for
Small teams and founders who ship through GitHub regularly and want their release notes written for them, especially multi-product teams who benefit from ReleasePad's flat per-product pricing instead of per-seat billing.
Not ideal for
Teams planning to lean on changelog analytics or a custom domain from day one will want to start on Pro, and teams whose releases are tracked outside GitHub will get the most value from the manual editor and MCP server rather than the commit-reading pipeline.
Pros
- AI drafts release notes directly from GitHub merges without requiring Conventional Commit formatting; prefixes are parsed for cleaner grouping only when they're already there
- One approval publishes everywhere at once: a hosted changelog page, a 4.3kb in-app widget, and a Markdown feed built for AI assistants to read
- MCP server lets Claude, Cursor, or ChatGPT draft and publish entries directly, extending the workflow into tools teams already use
- Pro is a flat $35 a month per product, with unlimited posts and unlimited team members included, so pricing doesn't climb with headcount
- Free plan needs no credit card, has no time limit, and includes a public changelog page and basic widget to get started
- Every draft comes with tone, detail-level, and language controls, plus a [skip] tag to exclude noise, so AI speed never becomes an AI editorial decision
- REST API and webhooks for post creation, publishing, and deletion let teams wire the changelog into their own tools
Cons
- The free plan's post allowance isn't listed as a specific number on the pricing page, so teams shipping very frequently should check with ReleasePad directly as they plan ahead
- Changelog analytics and a custom domain for the public page are part of the Pro plan rather than the free tier
- Annual billing is handled through a direct request to the team rather than a self-serve toggle, worth a quick email for finance teams that prefer one invoice a year
Verdict
ReleasePad is built for a specific moment: a team that ships constantly through GitHub but has nobody whose job is turning those merges into something customers can read. The AI-drafted-from-commits pipeline, paired with one-click publishing to a changelog page, an in-app widget, and an AI-readable Markdown feed, covers that moment well, and the approval step keeps a human in charge of what actually goes out. The lowest-friction way to see it work is to connect a repo on the free plan, no card required, and look at the first draft ReleasePad generates from a recent merge. Teams running more than one product, or already living inside Claude or Cursor, have an extra reason to move to Pro's flat $35-per-product pricing and MCP access once that first draft earns the switch.
Frequently asked questions
How does ReleasePad turn GitHub commits into release notes?
Connect a repo and ReleasePad's AI reads each merge and writes a draft entry within seconds; the product's own example shows about 12 seconds after a merge, though actual timing will vary with repo size. Conventional Commit prefixes are parsed for cleaner grouping when present but aren't required. A person reviews and can edit the draft, including tone and detail-level settings, before it publishes.
What's included on the free plan?
The free plan needs no credit card and has no time limit. It includes a public changelog page and the basic in-app widget, plus an allotment of published posts to start with; for the exact number, ReleasePad is best reached directly since the pricing page doesn't spell it out.
Does anything publish without my approval?
No. ReleasePad is explicit that there's no auto-publish switch: every AI-drafted entry waits for a person to review, edit if needed, and approve before it goes live on the changelog page or widget.
What does the MCP server do?
It connects ReleasePad to Claude, Cursor, or ChatGPT, so describing a shipped change to an AI assistant is enough to get a draft release note without opening ReleasePad's dashboard directly.
How does pricing work if we run more than one product?
Pro is $35 a month per product, billed monthly, with no per-seat fees and unlimited team members. A team running three products on Pro pays for three products, not for however many people are on each team.
