Compare
Aviator MergeQueue vs GitHub merge queue
GitHub's built-in merge queue gets the basics right. Aviator is purpose-built for monorepos and high-velocity teams that have outgrown it — parallel queues, affected-targets routing, flaky-test resilience, and enterprise controls.
Detailed comparison
| Queue at scale | Aviator | GitHub |
| Dynamic parallel queuesSpin up disjoint queues per affected target so independent PRs never wait on each other. | ||
| Affected-targets routing for monoreposRoutes a PR only to the queues for the build targets it actually touches. | ||
| Predictive batching | Basic | |
| Stack-aware queue (stacked PRs) | ||
| Fast-forward (linear-history) merge | ||
| Cross-repo coordination via ChangeSets | ||
| Reliability | Aviator | GitHub |
| Flaky-test tolerance with retry budget | ||
| Quarantine for chronically flaky tests | ||
| First-class priority mergesPush a hotfix to the front of every queue without disrupting in-flight batches. | ||
| Pause and drain the queue | Manual | |
| Auto-update PRs against latest main | ||
| Integrations & extensibility | Aviator | GitHub |
| CI-agnostic (Actions, BuildKite, CircleCI, Jenkins, GitLab, Argo)Other CIs work via status checks but lose first-class integrations. | GitHub Actions first | |
| Custom required checks (with wildcards) | ||
| Cross-team automation engine (Pilot) | ||
| REST + GraphQL APIs | ||
| Webhooks for queue lifecycle events | Limited | |
| Slack notifications for every queue event | ||
| Visibility | Aviator | GitHub |
| Live queue dashboard | Basic | |
| Per-PR time-in-queue analytics | ||
| Org-level queue throughput metrics | ||
| Enterprise & security | Aviator | GitHub |
| Self-hosted / on-prem deployment | GitHub Enterprise Server only | |
| SAML SSO | Enterprise plan | |
| SCIM provisioning | Enterprise plan | |
| SOC 2 Type II | ||
| Audit logs exportable to data warehouse | Limited | |
| Support | Aviator | GitHub |
| Shared Slack channel with engineering | ||
| Dedicated customer success engineer | Premium plan | |
| Community Discord / forum |
| Queue at scale | Aviator | GitHub |
|---|---|---|
| Dynamic parallel queuesSpin up disjoint queues per affected target so independent PRs never wait on each other. | ||
| Affected-targets routing for monoreposRoutes a PR only to the queues for the build targets it actually touches. | ||
| Predictive batching | Basic | |
| Stack-aware queue (stacked PRs) | ||
| Fast-forward (linear-history) merge | ||
| Cross-repo coordination via ChangeSets |
| Reliability | Aviator | GitHub |
|---|---|---|
| Flaky-test tolerance with retry budget | ||
| Quarantine for chronically flaky tests | ||
| First-class priority mergesPush a hotfix to the front of every queue without disrupting in-flight batches. | ||
| Pause and drain the queue | Manual | |
| Auto-update PRs against latest main |
| Integrations & extensibility | Aviator | GitHub |
|---|---|---|
| CI-agnostic (Actions, BuildKite, CircleCI, Jenkins, GitLab, Argo)Other CIs work via status checks but lose first-class integrations. | GitHub Actions first | |
| Custom required checks (with wildcards) | ||
| Cross-team automation engine (Pilot) | ||
| REST + GraphQL APIs | ||
| Webhooks for queue lifecycle events | Limited | |
| Slack notifications for every queue event |
| Visibility | Aviator | GitHub |
|---|---|---|
| Live queue dashboard | Basic | |
| Per-PR time-in-queue analytics | ||
| Org-level queue throughput metrics |
| Enterprise & security | Aviator | GitHub |
|---|---|---|
| Self-hosted / on-prem deployment | GitHub Enterprise Server only | |
| SAML SSO | Enterprise plan | |
| SCIM provisioning | Enterprise plan | |
| SOC 2 Type II | ||
| Audit logs exportable to data warehouse | Limited |
| Support | Aviator | GitHub |
|---|---|---|
| Shared Slack channel with engineering | ||
| Dedicated customer success engineer | Premium plan | |
| Community Discord / forum |
Real-time support
Personalized support your team deserves
Every Aviator customer gets a shared Slack channel with our engineering team. No tickets, no triage queues — just direct line to the people who built MergeQueue.
FAQs
Can we use Aviator MergeQueue if we're already on GitHub merge queue?+
Yes. Aviator runs as a GitHub App, so you can migrate one repository at a time. We help large teams cut over without freezing development.
Does Aviator work with our existing CI?+
Yes. Aviator is CI-agnostic and integrates with GitHub Actions, BuildKite, CircleCI, Jenkins, GitLab CI, and Argo via status checks plus first-class hooks for the common ones.
Do you support monorepos with Bazel, NX, Pants, or Turborepo?+
Yes. Affected-targets routing uses your build tool's dependency graph to send each PR only to the queues for the targets it touches. The result is thousands of parallel queues running in lockstep.
Is there a self-hosted option?+
Yes. Aviator ships as an on-prem bundle that runs entirely inside your network. SOC 2 Type II, audit logs, and SAML SSO are available on every deployment model.
How does pricing work?+
Free for teams under 15 developers. Above that, pricing is per active developer with volume discounts for larger orgs. Talk to us for a quote.
Stop fighting your merge queue
Free for teams under 15 developers. No credit card required.
Join us at The Hangar
A vetted community for developer-experience (DX) enthusiasts.