Skip to content
For SaaS founders shipping with GitHub

You ship the improvement.We draft the announcement.

Turn your GitHub changes into release notes, customer emails and team updates. Spend your time building; review the wording and approve customer messages before they go out.

Draft my first announcement See a real change explained

Your first Update is free. No card required.

  • Read-only GitHub access
  • Editable drafts
  • Customer sends require approval
Source GitHub
One reviewed UpdatePublic communication · Internal communication
YOUR NEXT ANNOUNCEMENT, MADE CONCRETE

See what you could send your users.

Start with an announcement based on our own Settings release, or explore sample messages for a feature launch, a fix or an API change.

5 COMPLETE PACKSRelease gallery

API migration, UX feature, production hotfix, export cadence and permission audit — each rendered for three audiences.

Open the gallery FULL CUSTOMER EMAILInvoice API deprecation

The exact subject, deadline, field mapping, action and branded message behind the example already shown on this page.

Read the email FROM A SHIPPED MERGELAY CHANGEA fix your users can understand

See how our Settings fix becomes a short customer announcement and an internal support note.

See the before and after HONEST COMPARISONMergelay vs Beamer

Beamer wins for an in-app widget and engagement suite. Mergelay wins when the missing work begins at the GitHub merge.

Compare the products

Prefer the repository-native baseline? Read the equally direct comparison with GitHub release notes.

THE COMMUNICATION GAP

Shipping got faster. Explaining what changed still takes time.

Teams deliver more changes, more often. Yet every release still triggers the same round of internal updates, customer emails, release notes and social posts.

Mergelay groups related work into one release and prepares only the formats you use, so a single review keeps everyone current while product and engineering move on.

WITHOUT MERGELAY
Release noteWho is writing this?Waiting
SlackContext scattered in threadsUnclear
Customer emailRewrite it againLater
WITH MERGELAY
Product releaseReady
Several merges. One source for every audience.

A public record plus customer and team drafts for the channels you connected.

Release noteTeamEmailSocial
HOW IT WORKS

From many merges to one release.

Mergelay prepares the first useful version. Your team keeps the final word.

01

Keep shipping

Choose the GitHub repositories Mergelay may watch. Related merges accumulate in one release with their pull requests, commits and diffs attached.

Read-only GitHub access
02

Shape the release

Mergelay turns the useful product outcomes into one clear Update. Audience-specific drafts appear only for the channels you connect.

Every claim linked to evidence
03

Send with control

Edit the wording, approve one exact version and send it only to the destinations you selected.

Customer publication waits for approval
SOURCE-GROUNDED DRAFTS. HUMAN DECISION.

Automation without losing control of the message.

Mergelay does not publish a vague summary and hope for the best. Evidence stays linked, drafts stay editable and approval belongs to your team.

  • Source-awareImportant claims stay traceable to the change that supports them.
  • Made for your voiceEdit every format before your customers or teammates see it.
  • Exact-version approvalApproving one version never silently approves a later edit.
ONE STORY, SHAPED FOR EACH AUDIENCE

Approve once. Publish where the update belongs.

A customer release note should not read like a Slack message. Mergelay keeps one source of truth while adapting the format for every destination.

Microsoft TeamsWebhook
SocialX · LinkedIn · Bluesky · Mastodon

Drafts, approvals and deliveries are unlimited under fair use — LinkedIn, Bluesky and Mastodon included. Automatic X publishing is the one metered exception: 10 posts a month on Developer, 50 on Team, then 30¢ of prepaid credit; publishing on X yourself is always free. When one destination fails, you retry that destination alone — the ones already delivered are never sent twice. Detection, grouping and drafting run on their own; customer-facing publication is the step that always waits for a person, and what is automated says exactly where that line sits.

See publishing details
SIMPLE PRICING

Choose by repository scope. Ship without counting.

Every plan includes unlimited prepared updates, approvals and publishing — LinkedIn, Bluesky and Mastodon included under fair use. Automatic X publishing is the one metered exception. Start with one repository or connect them all.

ONE REPOSITORY

Developer

For a product shipped from one GitHub repository.

$11/ workspace / month

USD, excluding VAT and sales tax — calculated and charged at checkout by Polar Software, Inc., our merchant of record.

  • Unlimited prepared updates
  • Every destination, plus LinkedIn, Bluesky and Mastodon under fair use
  • 10 automatic X posts a month, then 30¢ of prepaid credit
  • Sends from a Mergelay sub-domain, no DNS setup
Start with Developer
UNLIMITED REPOSITORIESMost flexible

Team

For teams shipping one product across multiple repositories.

$46/ workspace / month

USD, excluding VAT and sales tax — calculated and charged at checkout by Polar Software, Inc., our merchant of record.

  • Unlimited prepared updates
  • Every destination, plus LinkedIn, Bluesky and Mastodon under fair use
  • 50 automatic X posts a month, then 30¢ of prepaid credit
  • Send from your own domain (DKIM/SPF)
Start with Team

Prepared updates, destinations and targeted retries are unlimited under fair use, and so is publishing to LinkedIn, Bluesky and Mastodon. You pay for repository scope, never for the number of releases you ship — only automatic X posts beyond the monthly allowance draw on prepaid credit, and publishing on X yourself stays free.

Compare plans
YOUR NEXT MERGE CAN ALREADY BE THE UPDATE

Make the next release easy to follow.

Connect one repository and turn the next meaningful change into a reviewed pack.

Create your workspace