Uber SubmitQueue review
An open-source, self-hosted queue that validates parallel changes against predicted branch states.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Uber SubmitQueue is an open-source merge-queue system for teams managing concurrent changes, particularly in large monorepos. Its central idea is to validate proposed changes against likely future states of the main branch before they land. Teams that need to keep a busy trunk moving may value its speculative, parallel approach; it is less suited to buyers looking for a hosted merge-queue service or a ready-made workflow with minimal operational ownership.
The queue accepts, batches, validates, and lands changes through a gateway and orchestrator. It speculatively rebases and validates multiple changes in parallel, then can land passing changes automatically. When a validation fails, SubmitQueue isolates the failing change and retries the rest of the batch, helping avoid blocking unrelated changes. Runway handles version-control operations, conflict checks, and merges. This focus on predicted branch states and batch recovery is the product’s defining strength for teams with concurrent changes, rather than a general-purpose code review or deployment tool.
SubmitQueue is self-hosted, with a local Docker-based quickstart. Its extension points cover change providers, build runners, storage, queues, and scoring, which gives teams room to fit it to bespoke workflows but also means they own deployment and configuration. GitHub pull requests are supported in the documented setup; the project’s provider extensions may matter to teams with other workflows, but the documented setup does not establish their availability. Support is through community and documentation. Choose SubmitQueue if your team can operate self-hosted infrastructure and wants speculative batch validation; consider another option if you need a hosted service, or depend on a documented provider beyond GitHub.
Uber SubmitQueue pros and cons
- Where it wins
- Validates multiple changes in parallel against possible future branch states
- Isolates a failing change and retries the remaining batch
- Pluggable providers and runners support bespoke workflows
- Where it doesn't
- Self-hosted deployment puts runtime operation with your team
- The documented pull-request provider is GitHub
- Support channels are community and documentation
Uber SubmitQueue fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update