Pricing / Built around your repository
Free for public repos.
Paid for private repos.
Catch supported layout regressions before you merge. The same source review, whether you build in the open or with your team. MergeRay is in private beta: billing is not open yet and nothing is charged.
Public repositories
Make layout findings part of your public pull requests, with evidence your contributors can review.
Free
For public repositories
- GitHub-verified public repositories
- Same-repository pull requests
- Free hosted review within usage limits
Pro
Bring the same source review to your private codebase, with repository access and billing managed in your workspace.
$10
USD per developer / month · billing is not open yet
- Authorized private repositories
- No monthly review quota or per-review charges
- Choose exactly who gets a developer seat
- Free viewing for workspace members
Your team. Your choice.
Pay for developers. Keep reviewing.
Choose your seat count, then assign seats to GitHub accounts in your workspace. New members and pull requests never add charges.
$30 USD / month
3 × $10. Before applicable taxes.
Viewers are free. No per-review charges. An example only: billing is not open yet.
One review standard. Both repository types.
Supported scopeSource-first analysis
Review supported React, Next.js and CSS changes from committed source. No preview deployment required.
Evidence you can inspect
Findings, source locations and explicit coverage. Uncertain results stay visible as uncertain.
In your pull request
A GitHub Check and job summary bring the review back to the place where you decide to merge.
Open source clients. Private hosted engine. You choose which repos to connect.
How source is handledAccess & billing
A clear path to your first review.
Connect your repository. Confirm access. Review the change.
Read the quickstartCan I subscribe yet?
Not yet. MergeRay is in private beta, billing is not open and nothing is charged. When it opens, Pro will be $10 USD per developer per month, before applicable taxes, managed by a workspace owner from Billing in the dashboard, with no annual commitment or minimum team size.
Who needs a paid seat?
Each developer whose private pull requests you want MergeRay to review needs an assigned Pro seat. The workspace owner purchases a seat quantity, then assigns seats to members who have signed in with GitHub. Members who only view results, and contributors using the verified public review path, do not need paid seats.
Will a new PR or team member increase my bill?
No. Opening a PR, inviting a member or assigning an available seat never purchases another seat. A private PR from an unassigned author is not reviewed by MergeRay. The owner must explicitly buy more seats or reassign an available seat; one invoice covers the workspace.
Are private reviews unlimited?
Pro has no monthly source-review quota and no per-review overage fee. Technical limits still apply to source size, processing time, concurrency and storage. The initial Pro workspace allowance is 20 connected repositories and 40 projects. It does not include unlimited AI usage or infrastructure. Public review has separate usage limits; final public hosted allowances will be published before enrollment opens.
What happens when I remove a seat?
Removing an assignment stops new private reviews for that developer and frees the seat for someone else. It does not reduce the purchased seat quantity or bill. To change that quantity or cancel, use Manage seats & billing and confirm the change in Stripe. Existing results remain available within retention limits.
How does MergeRay identify the PR author?
We verify the author with GitHub and match their permanent account ID to the assigned seat. The person who reruns a workflow does not replace the original author. Renaming a GitHub account does not transfer its seat to another account. Bot-authored private PRs are not included in the initial seat model.
What if a public repository becomes private?
MergeRay rechecks repository visibility with GitHub. New private reviews require an active Pro subscription and a seat for the PR author. Changing visibility never starts a subscription or charges you automatically.
Can I use the CLI with my seat?
The CLI uses a personal CLI token you create in the dashboard, bound to your GitHub identity and your Pro seat, so it is not available until billing opens. It cannot be shared as a workspace-wide seat. The free public path uses verified GitHub source; downloading the open source client does not grant hosted access.
Which parts are open source?
The public distribution covers the CLI, GitHub Action, protocol, configuration and hosted client. The analysis engine stays private for both plans. The CLI is published on npm as mergeray.