Merge code.
Ship the update.
Mergelay turns a merged pull request into an evidence-backed brief, an editable draft and an approved update — before anything reaches your team or customers.
Breaking change · 3 evidence links · migration required
Code shipped. Context didn’t.
Mergelay closes one small but expensive gap: the time between a real product change and a clear, trustworthy explanation of it.
A merge is not an update
The code is reviewed and deployed, but the people around the product still do not know what changed or why it matters.
Context disappears quickly
The author moves on, the diff gets buried, and support or sales reconstructs the story from fragments days later.
Generic summaries lose trust
A useful update needs evidence, a human edit and an exact approval — not another unsupervised AI paragraph.
One small loop, done well.
Mergelay prepares the first useful version. Your team keeps the decisions: what the change means, how the message reads, and where the approved revision goes.
- Understand the impact from the merged pull request and its evidence
- Edit the message until it sounds like your team
- Approve one exact revision before publication is unlocked
- Publish only to the destinations you selected
Start narrow. Publish reliably.
Prepare one approved update, then send it to built-in release notes, Slack, email, a Microsoft Teams webhook or your social accounts on X, Bluesky, Mastodon and LinkedIn — every destination you selected, and only those.
Create a durable, customer-ready update inside Mergelay.
Publish an approved update to the team channel that needs it.
Send focused stakeholder updates to the people who need them.
Publish an approved update through a Teams workflow webhook.
Post an approved update to your connected X account.
Post an approved update to your Bluesky account.
Post an approved update to your Mastodon instance.
Post an approved update to your LinkedIn feed.
Two plans. Pick the capacity your team needs this month.
Both plans keep GitHub monitoring and human approval at the center. Choose the number of repositories, destinations and prepared Updates that match how often you ship.
Watching merges never consumes the allowance. Sending the same approved Update to several destinations still counts once — you are billed when an Update is prepared, not when it is published.
Buy a top-up only when needed. No automatic charge and no unused rollover.
Developer
For a developer or small team that wants the essential merge-to-update workflow on one repository.
- 10 prepared Updates each month
- 1 GitHub repository
- 3 connected destinations
- 10 social deliveries each month
- Built-in release notes for every approved update
- Human approval before every publication
Team
For a product team coordinating internal and customer-facing communication across several repositories.
- Everything in Developer
- 50 prepared Updates each month
- Up to 5 GitHub repositories
- Up to 10 connected destinations
- 50 social deliveries each month
A social delivery is one approved post delivered to one social account — Developer includes 10 and Team includes 50 each month. Publishing the same approved Update to several accounts counts one delivery per account.
Mergelay has no free plan or free trial. Billing begins only after the selected plan and renewal terms are confirmed during checkout. Both plans can add 10 prepared Updates for $5 through an explicit top-up; automatic overages and rollover are never applied.
Enterprise needs (SSO, custom limits, SLA)? Write to hello@mergelay.com.
Turn the next merge into an update.
Create your workspace, connect a GitHub repository and keep the final approval in human hands. Developer is $9 and Team is $39 per workspace each month.