Starter
For small teams publishing a polished update each week.
- ✓1 connected repository
- ✓2 reviewers
- ✓4 published releases per month
- ✓Hosted changelog and RSS
Mergecast turns the GitHub work your team already shipped into clear, customer-ready product updates. Less release-note archaeology. More signal.

niftybits/atlas
Listening for merged pull requests
Review queue
Three stories from eight merges
Faster project search
Ready to publish
New workspace roles
Review carefully
Refactor connection pooling
Internal · suppressed
From merge to message
Choose the GitHub repository Mergecast should listen to. Setup takes a few minutes.
Merged pull requests are classified, filtered, and shaped into customer-ready drafts.
Review the language, approve the story, and publish to your hosted feed when it is right.
Why Mergecast
Most release tools wait for someone to remember what shipped. Mergecast starts from the work itself, filters out the noise, and puts a useful story in front of the person who knows the customer.
Titles, descriptions, labels, changed files, and linked work inform every first draft.
Nothing reaches customers until someone on your team reviews and approves it.
Review and edit freely. Your allowance only moves when you publish a release.
On the horizon
Clearly coming soon—never presented as part of the product you can use today.
Bring product specs and acceptance criteria into the release story.
Tell teammates and customers the moment an update goes live.
Pair the story with crisp before-and-after product screenshots.
Simple pricing
Every plan includes unlimited draft review and editing. Only published releases count toward your monthly allowance.
For small teams publishing a polished update each week.
For teams shipping and communicating several times a week.
For multi-product teams with a high release cadence.
Questions, answered
No. Drafts always land in a review queue. A person on your team edits, approves, and publishes each update.
The classifier separates customer-facing work from refactors, configuration, and operational changes. Low-confidence items are clearly flagged.
Only a published release counts. Ingesting pull requests, reviewing drafts, editing, and rejecting items do not use your monthly allowance.
Yes. Billing is month-to-month and managed through Stripe. You can cancel from your workspace billing portal.
Connect GitHub. When the next customer-facing pull request merges, the first draft will be waiting.
Start with one repository14-day plan trial · Human review by design