mergefreeze.com

What it is

Merge Freeze is a GitHub App with a very focused goal: preventing Pull Requests from being merged during critical release, deployment, or maintenance windows, so teams do not have to rely solely on verbal Slack announcements or informal agreements to enforce a code freeze. It works via the GitHub Status/Checks API, and its site clearly states that it does not access repository contents or request code access permissions.

Core features and integrations

In terms of functionality, Merge Freeze supports one-off freezes, allowing team members to temporarily block merges. It also supports scheduled freezes based on daily, weekly, monthly, and other rules, making it suitable for fixed release windows. It provides a Web UI for managing freeze status, as well as a Web API for checking the current status of a repository or triggering a freeze, which makes it easy to integrate with CI/build pipelines or internal release platforms. Slack integration is one of its key selling points: teams can use /mergefreeze to check project status, freeze or unfreeze branches with one click in Slack, and choose notification channels. The installation process is based on GitHub OAuth and the official GitHub Marketplace: log in to GitHub, install the App, then select the organization repositories and protected branches.

Pricing and permissions

The pricing tiers are straightforward: Open Source is free and intended for public repositories; Reactive costs $25/month and supports up to 20 private repositories, Slack integration, and email support; Proactive costs $40/month and supports up to 50 private repositories, the Web API, and scheduled freezes; Enterprise is custom-priced and offers unlimited private repositories, dedicated support, and onboarding assistance. All paid plans include a 14-day free trial. Payment methods include major credit cards, and ACH is available for enterprise customers. The terms also mention that paid plans are billed through GitHub Marketplace.

Pros and cons

Its strengths are a clear product focus, lightweight onboarding, strong fit for teams using GitHub and Slack, and reduced security concerns because it does not access source code. The API and scheduled freezes make it more than just a button-based tool; it can become part of a release workflow. The drawbacks are that its ecosystem is clearly centered on GitHub, with no stated support for GitLab, Bitbucket, or self-hosted platforms. Key automation features such as the Web API and scheduled freezes require the Proactive plan or above. The number of private repositories is also limited in the lower and mid-tier plans. In addition, the site notes that it has been acquired by Fork Equity, so future product direction and commercial strategy may change.

Who it is for and access from China

Merge Freeze is suitable for small, mid-sized, and large engineering teams that use GitHub and Slack and need release freeze controls, especially organizations with multiple repositories, many collaborators, and frequent release cycles. Open-source projects can use the free plan. The crawled text does not provide information about access from China, and because it depends on GitHub, Slack, and GitHub Marketplace, practical usability for teams in China may be affected by the network availability and payment environment of these external services. If a team primarily uses domestic code hosting or a self-hosted Git platform, it should evaluate alternative workflows or internal CI gatekeeping solutions.