Mergepatrol vs Trunk Merge Queue

2026-10-31

Trunk sells a merge queue as part of a CI reliability suite that also covers flaky tests. Mergepatrol is a merge queue whose agent resolves rebase conflicts and fixes failed checks, so fewer pull requests go back to their authors. Checked against Trunk’s docs and pricing on 31 October 2026.

At a glance

	Trunk Merge Queue	Mergepatrol
Price	Free for up to 5 committers; Team price after the trial not listed; Enterprise custom	Public repos free; private repos $15 a seat a month after a 14-day trial; self-hosted free
Parallel testing	Predictive testing and parallel lanes	No speculative builds: one batch of up to `batch_size` PRs (8 by default)
Batching	A failed batch is split in half and retried; passing PRs merge	A failed batch is split in half down to the PR that broke it
A PR that conflicts	Back to its author: we found no conflict agent in its docs	An agent resolves the conflict, checked by your `verify` commands
A required check that fails	Back to its author. CI Autopilot, a separate product in private beta, can open fix PRs	An agent commits a fix on the PR, in the queue, up to `fix_ci.attempts` times
Flaky tests	Anti-flake protection, and Trunk’s flaky-test product	The fix agent gives up on a failure that is not the PR’s, and the PR is ejected
Source	Proprietary SaaS	Apache-2.0, self-hostable

Where Trunk is the better fit

Flaky tests are your main problem. Trunk’s queue tolerates flakes, and its flaky-test product finds and quarantines them.
High throughput. Parallel lanes and predictive testing keep many builds in flight.
Up to 5 committers on private repos, for free.

Where Mergepatrol is the better fit

Conflicts and real failures eject your pull requests. The fix happens in the queue, on the PR, while it keeps its place, rather than in a separate PR.
You want to self-host, or want public repos free at any team size.
Agents open your PRs. Mergepatrol’s MCP server lets them queue and follow their own.