Mergify Review (2026): Pricing, Features & Honest Verdict

TLDR

Mergify is a merge queue and CI orchestration platform for GitHub teams. It batches pull requests, retries flaky CI, and keeps your main branch green when many developers ship at once. It solves real pain, but it is fiddly to configure and GitHub’s free native queue covers small teams. Best for: busy DevOps and platform teams. Price: Free up to 5 users, Max $21/seat/mo. Rating: 6.9/10.

What is Mergify?

Mergify automates everything that happens between a pull request and a clean main branch. Its core feature is a merge queue: instead of merging PRs manually and praying the build stays green, you hand them to Mergify, which queues them, re-runs CI against the latest base, batches several together into one CI run, and merges only what passes. When a batch fails, it bisects automatically to find the culprit instead of nuking every PR in the queue. Around that core sit four more products: CI Insights for observability into slow and failing jobs, Test Insights for spotting and quarantining flaky tests, Merge Protections for governance rules, and Stacks for breaking giant PRs into reviewable chains.

It was built by Julien Danjou and Mehdi Abaakouk, who started the company in 2018 after years of watching engineers waste hours babysitting pull requests and chasing CI failures. Both came from open-source backgrounds, and Mergify began life as an open-source bot before becoming a commercial SaaS. The team is spread across France and the Netherlands and bootstrapped the business rather than raising venture money, reaching seven-figure revenue on its own. We found it now runs across 300,000+ repositories at 2,000+ organizations, merging tens of thousands of PRs a month. The pitch matters more now than ever: AI coding assistants mean teams open more PRs than their CI can validate, and a busy monorepo without a merge queue grinds to a halt on conflicts and stale bases.

What Are Mergify’s Key Features?

Merge Queue with Batching

This is the reason most teams sign up. Mergify takes approved PRs, tests them against the real future state of the branch, and batches multiple PRs into a single CI run. If the batch passes, all of them merge; if it fails, automatic bisection isolates the bad PR instead of rejecting the whole group. On a repo merging dozens of PRs a day, batching can dramatically cut total CI minutes, which is where the cost savings come from. GitHub’s native queue does not batch, so every PR pays for its own full CI run.

Priority Lanes and Queue Rules

You can define multiple queues scoped by label, path, or branch, and give urgent PRs a priority lane so a hotfix jumps ahead of routine work. Rules are written in YAML conditions (for example, queue only when two reviews and all required checks pass). This configurability is Mergify’s real edge over the native queue, which offers one queue and far fewer knobs. It is also the source of most complaints, because the rule language takes time to get right.

CI Insights and Test Insights

CI Insights gives you dashboards on which jobs are slow, which fail most, and where CI minutes are burned, plus automatic retries for transient failures. Test Insights detects flaky tests and lets you quarantine them so one unreliable test does not block the whole queue. This is useful, but honesty matters here: users report Mergify’s flaky-test protection inside the queue is weaker than rivals, and a flaky failure can force the speculation chain to rebuild from scratch, wasting CI time.

Stacks and Merge Protections

Stacks lets you split one large change into a dependent chain of smaller PRs that review and merge in order, which is handy for big refactors. Merge Protections layer on governance: scheduling policies, required conditions, and freeze windows so nothing merges during a deploy freeze. These are nice-to-haves rather than headline features, but they round out the platform for teams with compliance or release-train needs.

How Much Does Mergify Cost?

Mergify starts free: up to 5 active users on private repositories, with all five products included and email support. Open-source projects on public repos are covered too. The key detail is the billing unit. Mergify charges per active contributor, defined as someone who opened a PR or pushed commits in the last 30 days. Bots and dormant accounts do not count, so a 40-person org where only 18 people touched code last month pays for 18 seats, not 40.

The paid Max plan is $21 per seat per month, with a 15% discount on annual billing, supporting up to 100 users with 30-day data retention and 24/7 premium support. Enterprise is custom-priced for unlimited users, custom retention, a Slack Connect support channel, and optional on-premise deployment. There is also a startup program offering up to $12,000 in credits for eligible companies.

The comparison that matters is GitHub’s native merge queue, which is free and bundled with GitHub. Trunk Merge Queue is priced per active committer and competes directly on developer experience. So Mergify is not cheap in absolute terms; its value is the CI minutes batching saves and the throughput priority lanes unlock. If your CI bill is large and your queue is constantly backed up, $21 a seat can pay for itself. If it is not, the free native queue is the rational starting point.

Run the math before committing. A 25-engineer team where 20 people are active most months pays roughly $420 a month on Max, or about $5,000 a year, before the annual discount. That is trivial next to a CI bill running tens of thousands of dollars a year, and Mergify ships an ROI calculator precisely so you can frame it as CI savings rather than a new line item. But for a 6-person team on a quiet repo, that same $420 buys very little over the free native queue. The cost case scales directly with how much your queue currently hurts.

Who is Mergify Best For?

Use Mergify if your team is shipping faster than CI can keep up. The sweet spot is platform and DevOps teams on a high-traffic repo or a monorepo where merge conflicts, stale bases, and CI cost have become a daily tax. Batching, priority lanes, and per-scope queues genuinely move the needle once PR volume is high, and the per-active-contributor billing keeps costs sane for teams with many occasional committers.

Skip Mergify if you are a team of fewer than ten engineers on a single, low-traffic repository. GitHub’s native merge queue is free, ships with GitHub, and is improving steadily; for most small teams it is enough. Also think twice if nobody on your team wants to own a YAML rule set, because Mergify rewards configuration effort and punishes neglect. And if flaky tests are your single biggest problem, evaluate competitors carefully, because Mergify’s in-queue flaky handling is not its strongest area.

Best Mergify Alternatives

GitHub Merge Queue

The obvious one, and free. GitHub’s native merge queue is built into branch protection, costs nothing, and is the right first step for small teams. It tests PRs against the projected base and merges in order. What it lacks is batching, priority lanes, monorepo scoping, and queue analytics, which is exactly the gap Mergify fills. If you have not tried the native queue yet, do that before paying anyone.

Trunk Merge Queue

Trunk is the closest paid competitor and leans hard into developer experience, with strong flaky-test detection baked in (an area where Mergify is comparatively weak). It is priced per active committer and bundles a wider suite (flaky test management, CI analytics, code quality). If flaky tests are your core pain, Trunk is worth a serious look alongside Mergify.

Aviator

Aviator targets larger engineering orgs with sophisticated batching, affected-target detection for monorepos, and change management workflows. Pricing is largely custom and aimed at bigger teams. It overlaps heavily with Mergify’s enterprise tier, so if you are evaluating Mergify Enterprise for a large monorepo, put Aviator on the same shortlist.

Final Verdict: Is Mergify Worth It?

Mergify earns a 6.9. It does one important thing very well: keeping the main branch green and CI bills down on busy repos through batching, bisection, and configurable priority queues. For platform teams that have outgrown manual merging, those features are the difference between shipping smoothly and fighting the queue all day. The per-active-contributor pricing is fair, and the free tier is genuinely usable for small teams and open source.

The reasons it is not higher are real. Configuration is hard enough that you need someone to own it, the in-queue flaky-test story trails rivals like Trunk, and GitHub’s free native merge queue keeps getting better, which narrows the gap for everyone except the largest, busiest repos. Our recommendation: if your CI is constantly backed up on a monorepo, trial Mergify and measure the CI minutes you save. If you are a small team on one quiet repo, start with GitHub’s native queue and only graduate to Mergify when the pain is obvious.