The question "what are the best alternatives to Qodo Merge" presumes Qodo Merge is still something you can pick from a shelf. Qodo's own documentation stopped treating it that way.
Read on 2026-09-19 from the Qodo docs llms.txt index. It splits the product documentation into "Qodo Review (v2)" as current and "Qodo Merge (v1)" as legacy, with the note to use the v1 pages only for "migration, backward compatibility, or historical questions." The qodo.ai/merge page now returns 404. Qodo Merge was renamed and replaced, not deprecated into a competing tool.
So the alternatives question is really two questions now: what to use instead of Qodo's review product, and what to run if you are self-hosted.
What Qodo Review still covers, per its docs, is the useful part. The installation matrix lists three deployment models: multi-tenant, single-tenant, and on-premises, the last being the air-gapped path and Enterprise only. Across those three, the supported Git providers are GitHub Cloud and Enterprise Server, GitLab, Bitbucket Cloud, Azure DevOps, and Gerrit.
The part that matters for teams not on GitHub is which providers have an on-prem install listed at all. From that same matrix, read on 2026-09-19:
- GitHub Cloud: multi-tenant and single-tenant only, no on-prem.
- GitLab: multi-tenant, single-tenant, and on-prem.
- Azure DevOps: multi-tenant and single-tenant only, no on-prem.
- Bitbucket Cloud: multi-tenant and single-tenant only, no on-prem.
- Gerrit: on-prem only.
GitLab is the one major forge besides GitHub Enterprise Server and Gerrit where Qodo lists an on-prem install path. Self-managed Azure DevOps Server and Bitbucket Data Center are absent from Qodo's on-prem coverage, and Bitbucket Server and Data Center do not appear in the provider matrix at all.
For teams on self-managed Azure Repos or Bitbucket Data Center, that closes off one option. The path that still holds there is PR-Agent, which lives outside Qodo: MIT-licensed, community-owned since Qodo donated it, and documented to run on GitHub, GitLab, Bitbucket, Azure DevOps, and Gitea. Qodo Review endorses the same ecosystem from the vendor side by dropping those forges from its on-prem list.
The practical takeaway for a forge-specific decision: name the edition before you name the tool. On GitLab self-managed you still have both paths on paper. On Azure DevOps Server and Bitbucket Data Center the vendor-owned option is not stated in Qodo's matrix, and the open-source route is the one documented to run.
Top comments (0)