staqd
staqd: An open-source, self-hosted tool for merging GitHub pull-request stacks and restacking branches. Ranked #21 of 26 in Merge Queue Software by our editors (6.2/10); pricing: Free plan; best for gitHub teams managing dependent PR stacks.
At a glance
- Editor score6.2 / 10
- PricingFree plan
- Best forGitHub teams managing dependent PR stacks
- Free planYes
- Paid fromFree
- Batch validationNo
- Facts checked23 Oct 2026
Where it wins
- Discovers stack relationships from pull-request base branches
- Merges a stack sequentially with approval checks
- Restacks child branches and reports conflicts with manual fix commands
Where it doesn't
- Requires setup as a GitHub Actions reusable workflow or composite action
- Targets GitHub; GitLab and Bitbucket are not supported
- Does not provide batch validation or merge trains
Our verdict on staqd
For GitHub teams working with dependent pull requests, staqd manages stacked PR workflows through GitHub Actions and pull-request comments. It is open source and self-hosted, with no separate SaaS service or required CLI. Its focus is maintaining stack relationships: it can discover a stack from pull-request base branches, merge one PR and restack its children, or process a stack sequentially with approval checks.
Setup involves adding a reusable GitHub workflow or composite action and configuring repository permissions; GitHub App credentials are optional. The integration set centers on GitHub Actions, GitHub pull requests, the GitHub API, and Git. Commands targeting the same base branch are serialized, and after a parent PR is manually merged in GitHub, staqd can update child PR base branches. These choices suit teams already organizing work as GitHub PR stacks, rather than teams seeking a service spanning multiple repository hosts.
The project reports restack conflicts and provides manual fix commands, which gives maintainers a path to address conflicts instead of treating every stack operation as automatic. Its scope is narrower than a general merge queue: it does not offer batch validation or merge trains. Choose staqd when stack discovery, sequential merging, and child-branch maintenance are the priority; teams that need those broader queue workflows or support for GitLab or Bitbucket should look elsewhere.
Your product? Our editors can test staqd in depth and publish a review, labelled as paid · from $149/mo →
staqd pricing
staqd fact sheet
| Free plan | Yes |
|---|---|
| Paid from | Free |
| GitHub support | Yes |
| GitLab support | No |
| Bitbucket support | No |
| Batch validation | No |
| Merge trains | No |
| Deployment model | Self_hosted |
| Max parallel batches | Not verified |
| Deployment | Self-hosted |
| Integrations | 4 integrations: GitHub Actions, GitHub pull requests, GitHub API, Git |
| Pricing | Free plan |
| Website | github.com |
| Facts checked | 23 Oct 2026 |
staqd integrations
staqd lists 4 integrations on its own site.
- GitHub Actions
- GitHub pull requests
- GitHub API
- Git
Alternatives to staqd
- MergifyMerge queues and stacked PRs paired with test-health tools and broad CI integrations.8.9
- BitbucketA practical fit for Bitbucket teams that want merge queues alongside code hosting and CI/CD.8.5
- ProwSelf-hosted CI and pull-request merge automation for teams running Kubernetes.8.1
Used staqd? Be the first to review it
The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used staqd for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.
Write a reviewTwo minutes · verified accounts only · read by an editor before it appears
Featured on iTechGuides
staqd is listed in our Merge Queue Software directory. Add the badge to your site — it links back to this page.
<a href="https://www.itechguides.com/products/staqd/"><img src="https://www.itechguides.com/best/badge/staqd.svg" alt="Featured on iTechGuides" width="230" height="46"></a>
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
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