Disclosure: CodeToolPilot may earn a commission if you buy through links on this page, at no extra cost to you. How we make money.
Last verified: October 12, 2026. This is an editorial research review — how we review. Prices and plans change often; confirm on the vendor’s site.
Status update: Formerly Codium (CodiumAI), renamed Qodo in September 2024. Qodo now focuses on code review; its open-source PR-Agent project was handed to a community-owned GitHub organisation.
Qodo is the company formerly known as Codium (often called CodiumAI). It renamed itself in September 2024. The company first became known for AI test generation and an IDE assistant, but through 2026 it has turned itself almost entirely into an AI code review and governance platform. Its March 2026 release notes say it directly: “Qodo is transitioning from a code generation tool to a code review agent.”
The product is aimed at engineering organisations that care less about one more comment bot and more about enforcing written standards across many repositories, Git providers and coding agents. Qodo’s pitch, “Code review for agents. Governance for humans,” fits teams where much of the code is now written by tools such as Claude Code, Codex or Cursor, and where leads need a consistent quality gate before merge.
This is an editorial research review. It is based on Qodo’s pricing page, documentation, changelog and announcements as of October 2026, not on hands-on benchmarking. Qodo’s own performance claims are not repeated here as fact.
Quick verdict
Qodo is a strong fit for organisations that want code review to enforce explicit, evolving rules across many repositories and Git providers. Its deployment options go all the way to air-gapped installations. It is a weaker fit for small teams that want to try a tool cheaply. There is no permanent free tier, the credit-based pricing makes the cost per review vary, and several of the newest Qodo 3.0 features are still in Beta or Research Preview.
- Pro: Works with GitHub, GitLab, Bitbucket, Azure DevOps and Gerrit.
- Pro: A rules system that can mine standards from your PR history and enforce them in every review.
- Pro: Deployment ranges from multi-tenant SaaS to single-tenant, on-premises and air-gapped (Enterprise).
- Pro: The Pro Team plan bills one pooled credit balance per workspace rather than per seat, with a spending cap you set.
- Pro: The Agentic Toolbox lets coding agents check their work against the same rules before a PR is opened.
- Con: No permanent free tier; only a 14-day trial.
- Con: By Qodo’s own estimate, the $30 entry pool covers only about 18 reviews a month, and larger PRs use more credits.
- Con: Several new capabilities, including PR Triage, Software Map and cross-repo review, are labelled Beta or Research Preview.
- Con: SSO, audit logs, bring-your-own-key and self-hosting are Enterprise-only.
What is Qodo?
Qodo describes itself as an “AI code review and governance platform.” The core is an agentic pull request reviewer that became generally available with Qodo 2.0 in February 2026. Instead of a single model pass, specialised agents each handle part of the review, drawing on what Qodo calls its Context Engine: your rules, your codebase, PR history and business requirements from linked tickets.
Qodo 3.0, released on 1 October 2026, adds tools for running review at organisation scale. These include PR Triage (Research Preview), an analytics dashboard (Beta), an onboarding wizard and Gerrit support across all deployment types. The company raised a $70 million Series B led by Qumra Capital in March 2026, bringing its reported total funding to $120 million.
It helps to know where Qodo came from. The 2024 rename turned the IDE plugin Codiumate into Qodo Gen, and the PR-Agent project into Qodo Merge. The hosted review product has since grown into today’s platform, and Qodo has handed the open-source PR-Agent project to a community-owned GitHub organisation that now maintains it independently. If you used Codium or PR-Agent years ago, today’s Qodo is a different product.
Key features
Multi-agent pull request review
Reviews run automatically on pull requests and post findings in the PR. Recent releases added PR-history-based relevance, review verbosity controls, an “Outdated” label for findings already addressed, and a Findings page for tracking issues across reviews. Conversational chat inside PRs is in alpha for GitHub, GitLab and Azure DevOps.
Rules system and Rule Miner
Governance is the centre of the product. Teams define review standards that are enforced on every PR. Rule Miner, introduced in June 2026, generates rules from your PR history. For organisations that started using Qodo on or after 1 September 2026, generated rules are activated automatically by default. That saves setup time, but it also means someone should audit what gets switched on.
Cross-repo review and Software Map
Cross-repository review (Beta) looks for changes that could break other repositories downstream. Software Map (Beta), added in September 2026, shows how repositories and services connect and where findings cluster. Both are aimed at microservice-heavy organisations where the risk lies between repositories rather than inside one diff.
PR Triage and analytics
PR Triage, the headline Qodo 3.0 feature, groups related pull requests into work packages across repositories and Git providers. It shows blast radius, review difficulty, waiting time and a suggested review order. It is a Research Preview, so expect it to change. The new analytics dashboard reports findings, fix rates and unresolved issues.
Agentic Toolbox
Generally available since September 2026, the Agentic Toolbox gives coding agents access to Qodo’s rules and codebase context, and can review local changes before a PR exists. It is offered as a CLI, an MCP server, plugins for Claude Code and Codex, and a Kiro Power.
IDE extension
Qodo lists VS Code, JetBrains IDEs and Visual Studio as IDE surfaces. Since March 2026 the extension puts review first and can review both committed and uncommitted changes. Developers who mainly used the old plugin for code generation should note this change of focus.
Who should use Qodo
Qodo suits mid-size and large engineering organisations with many repositories, several Git providers or Gerrit, and a real need to enforce and audit standards. That is especially true where coding agents produce a large share of the code. Regulated teams that need on-premises or air-gapped review are a natural fit for the Enterprise plan.
Who should skip it
Solo developers, very small teams and open-source maintainers without program approval will find the lack of a free tier and the credit metering hard to justify. Teams that just want an affordable bot to comment on GitHub PRs may find the governance features more than they need.
Strengths and limitations
Strengths
- Git provider breadth. GitHub, GitLab, Bitbucket and Azure DevOps on the hosted service, plus Gerrit, which few competitors support. Qodo’s deployment matrix also covers GitLab self-managed on multi-tenant SaaS, GitHub Enterprise on single-tenant or on-premises installs, and Bitbucket Data Center on-premises.
- Serious deployment options. Enterprise customers can run single-tenant, fully on-premises or air-gapped deployments, use their own keys, and use self-hosted models through their own gateway. Qodo names NVIDIA Nemotron as an example.
- Governance as a first-class feature. Rules, rule mining, enforcement and analytics are built for leads who need to show that standards are actually applied, not just suggested.
- Pooled team pricing. One shared credit balance per workspace, with no per-engineer provisioning, suits teams where review volume is uneven across people.
- Clear training stance. The pricing page says Qodo “does not train models on your code,” and the trust center lists SOC 2.
Limitations
- Hard to predict cost. Credits are consumed according to PR size and complexity, so the cost per review varies. Busy teams may need the larger pools, and overage builds up until your cap is reached.
- No free tier. After the 14-day trial, reviews stop unless you pay. Individuals and hobby projects are better served elsewhere, or by the community PR-Agent project.
- Many features are still maturing. PR Triage, Software Map, cross-repo review and in-PR chat are all in Beta, Research Preview or alpha. Qodo also scheduled selected legacy v1 commands for permanent removal on 1 October 2026, so older automations may need updating.
- Enterprise gating. SSO, audit logs, BYOK and every self-hosted option need an Enterprise contract. The Pro Team plan is described as designed for teams of up to 30 users.
- Retention period not published on the pricing page. Both plans list “strict data retention,” but the specific period is not stated there. The detailed policy is offered through the trust center, so request it before connecting sensitive code.
- Rule automation needs oversight. Automatically activated, mined rules can save time, but they can also encode habits a team does not actually want enforced.
Pricing (as of October 2026)
| Plan | Price | What you get |
|---|---|---|
| Free trial | $0 for 14 days, no credit card | Unlimited reviews, credits and users during the trial; reviews pause afterwards until you choose a plan |
| Pro Team | $30/month for 2,500 pooled credits (about 18 reviews, per Qodo); larger pools of 5,000 credits (about 36 reviews) and 20,000 credits (about 144 reviews) at $0.012 per credit | Agentic PR review, rules system, Git and IDE integrations, pre-PR review skills, dashboard and analytics, monthly overage cap; monthly billing only; the pricing page says it is designed for up to 30 users |
| Enterprise | Custom | For 30+ users: SSO/SAML, audit logs, advanced self-learning, BYOK, single-tenant SaaS or on-premises/air-gapped, Gerrit, custom agentic workflows, priority support, annual contracts |
| Open source | Free by application | Qualifying open-source projects can apply to the Qodo for Open Source program |
Credits expire at the end of each monthly cycle, and overage is billed at the same per-credit rate up to a cap you set. Qodo’s estimates work out to an average of about $1.67 per review on the entry pool, but small PRs use fewer credits and large ones more. Confirm current plans and credit rates on Qodo’s pricing page before committing.
Prices verified on October 12, 2026 against the official Qodo pricing page. Plans change often — confirm on the vendor’s page before you buy.
Use cases
Qodo is built for organisations that want code review to enforce written standards, not just add comments to pull requests. The scenarios below are based on Qodo’s documented features as of October 2026, and each notes where a feature is still in Beta or limited to the Enterprise plan.
Enforcing one review standard across several Git providers
A platform team whose repositories are split across GitHub, GitLab, Bitbucket and Azure DevOps can use one Qodo rules system to apply the same standards to every pull request. Teams that also run Gerrit can bring it in, although Qodo’s pricing page lists Gerrit under the Enterprise plan. In our assessment, this provider breadth is Qodo’s clearest advantage over GitHub-only review tools. Check Qodo’s deployment matrix before buying, because supported self-managed hosts differ by deployment type.
Checking coding-agent output before a pull request exists
Teams where agents such as Claude Code or Codex write much of the code can use Qodo’s Agentic Toolbox, generally available since September 2026, so agents check local changes against the team’s rules before a PR is opened. The Toolbox is offered as a CLI, an MCP server, plugins for Claude Code and Codex, and a Kiro Power. This moves the quality gate earlier, so fewer agent-written PRs arrive with known rule violations. It works best once the team’s standards are actually written down as Qodo rules.
Turning tribal knowledge into enforced rules
A tech lead who keeps leaving the same review comments can use Rule Miner, introduced in June 2026, to generate rules from the team’s PR history and enforce them on every review. This helps when standards live in senior engineers’ heads rather than in a style guide. For organisations that started using Qodo on or after 1 September 2026, mined rules are activated automatically by default. Someone should audit what gets switched on, so the tool does not enforce habits the team actually wants to drop.
Code review in regulated or air-gapped environments
Banks, healthcare providers and public-sector teams that cannot send code to a multi-tenant service can run Qodo single-tenant, on-premises or fully air-gapped on the Enterprise plan. Enterprise also supports bring-your-own-key and self-hosted models through the customer’s own gateway, with NVIDIA Nemotron named by Qodo as an example. These options come with annual Enterprise contracts, so this path suits organisations that already run a formal security and procurement review. As part of that review, ask for the detailed data-retention policy through Qodo’s trust center.
Spotting cross-repository breakage in a microservice estate
Organisations running many services in separate repositories can use cross-repo review to flag changes that may break downstream repositories, and Software Map to see how services connect and where findings cluster. PR Triage, the headline Qodo 3.0 feature, can then group related PRs across repositories into work packages with a suggested review order. All three are labelled Beta or Research Preview, so in our assessment they are worth piloting rather than building a process around yet.
Alternatives
- CodeRabbit covers the same four major Git platforms with per-developer seats, a free plan for IDE and CLI reviews, and free PR reviews for public repositories.
- Greptile focuses on deep, codebase-graph-aware reviews, offers review tiers by effort, and supports self-hosting with custom LLMs on Enterprise.
- GitHub Copilot includes code review on paid Copilot plans, which may be enough for teams that are mainly on GitHub.
- PR-Agent is the open-source project Qodo donated to a community-owned GitHub organisation. It is an option for teams willing to run and configure review tooling themselves.
Final verdict
Qodo has become a governance-first code review platform, and that focus is its main appeal. Organisations that need consistent standards across many repositories, Git providers and coding agents, and that may need on-premises deployment, should shortlist it. Smaller teams should run the 14-day trial with realistic PR volume to see how many credits they actually use before they commit.
FAQ
Is Qodo free?
Qodo has no permanent free tier. It offers a 14-day trial with no credit card, after which reviews pause until you choose a paid plan. Qualifying open-source projects can apply to the Qodo for Open Source program. Teams willing to run their own tooling can also use PR-Agent, the open-source project Qodo handed to a community-owned GitHub organisation.
Is Qodo the same as CodiumAI or Codeium?
Qodo is the company formerly called Codium, often known as CodiumAI, which renamed itself in September 2024. Codeium is a separate, unrelated company, a point Qodo addressed in a 2023 blog post about the similar names. Codeium’s Windsurf editor is covered on this site as Windsurf (now Devin Desktop). If you remember CodiumAI for test generation, note that today’s Qodo has refocused on code review and governance.
Does Qodo work with GitLab, Bitbucket and Azure DevOps?
Yes. Qodo’s hosted service supports GitHub, GitLab, Bitbucket and Azure DevOps, and Qodo also supports Gerrit, which few competitors do. Its deployment matrix adds combinations such as GitLab self-managed on multi-tenant SaaS, GitHub Enterprise on single-tenant or on-premises installs, and Bitbucket Data Center on-premises. Check that matrix for your exact provider and hosting setup before you buy.
Does Qodo train on my code?
Qodo’s pricing page states that Qodo “does not train models on your code,” and its trust center lists SOC 2. Both paid plans mention “strict data retention,” but the pricing page does not give a specific retention period. In our view, teams handling sensitive code should request the detailed policy through the trust center before connecting repositories.
Can Qodo be self-hosted?
Yes, on the Enterprise plan. Enterprise customers can choose single-tenant SaaS, on-premises or fully air-gapped deployment, bring their own keys, and use self-hosted models through their own gateway. These self-hosted options are not part of the Pro Team plan. The community-maintained PR-Agent project can be self-run for free, but it is not the same product as today’s Qodo platform.
Qodo vs CodeRabbit: which should I choose?
In our assessment, Qodo fits organisations that prioritise enforceable rules, Gerrit support, pooled team credits and on-premises or air-gapped deployment. CodeRabbit covers the same four major Git platforms with per-developer seats, a free plan for IDE and CLI reviews, and free PR reviews for public repositories. Teams that mainly want an affordable review bot may find CodeRabbit simpler to start with, while governance-heavy organisations may get more from Qodo. Running both on the same set of real PRs during a trial is the most reliable way to compare them.
Sources
- Qodo pricing
- Qodo homepage
- Qodo docs: Pricing and usage
- Qodo docs: Changelog
- Qodo blog: Introducing Qodo 3.0 (1 October 2026)
- Qodo docs: Deployment model support by Git provider
- Qodo Trust Center
- Qodo blog: Introducing Qodo (formerly Codium) (September 2024)
- PR-Agent repository (community-owned)
- IT Brief: Qodo raises $70 million (March 2026)
- GitHub Docs: Copilot code review
- https://www.qodo.ai/blog/qodo-or-codeium-which-are-you-looking-for



