Skip to main content
AI Choice Engine
← All AI code review tools

Qodo

Qodo

Qodo is a Qodo pull-request reviewer on GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit (on-premises), billed as hybrid, last verified October 1, 2026. A governance-heavy reviewer: rules, cross-repo context, and analytics aimed at teams drowning in AI-generated PRs — not only a comment bot.

Catalog record checked October 1, 2026; vendor pricing and policies can change.

Open QodoPricing source
Qodo specification
SpecificationQodo
VendorQodo
Git hostsGitHub, GitLab, Bitbucket, Azure DevOps, Gerrit (on-premises)
SurfacePR review, IDE, and agent skills
Billing modelHybrid
Hourly / throughputCredits + spending cap (no hourly PR meter)
Trial14-day trial with unlimited credits, no card. Trial is the initial state of every workspace, not a separate plan.
Config / rulesQodo portal; repository wiki/root `.pr_agent.toml`; organization/project `pr-agent-settings` repositories
Inline comment capNot verifiedUnverified
Self-hosted optionYes
CI hostsNot a separate CI product
AutofixNot verifiedUnverified
Merge gateNot verifiedUnverified
Free for qualifying OSSNot verifiedUnverified
Hybrid

Qodo

A governance-heavy reviewer: rules, cross-repo context, and analytics aimed at teams drowning in AI-generated PRs — not only a comment bot.

Best for

  • Orgs applying shared review standards across many repos
  • Teams mixing IDE review with PR review
  • Enterprises that want BYOK or on-prem options

Watch out

Credit packs and the workspace spending cap determine paid usage; “No rate limits” does not mean unlimited included reviews. Credits expire monthly and overage uses the base credit rate. Pricing and billing docs disagree on the Pro Team user ceiling, so confirm the selected entitlement. Single-tenant and on-premises deployment are Enterprise-only; the installation matrix lists Gerrit and Bitbucket Data Center for on-premises. Git-provider features differ: PR-history indexing is beta on GitHub/GitLab, and Bitbucket/Gerrit do not support collapsible finding sections. No provider-wide autofix or merge-enforcement capability is inferred from agent skills or configuration options.

How a review works. Vendor-documented multi-agent review, codebase context, governance rules and agent skills. Findings appear in summary and/or inline views depending on configuration and Git-provider capabilities; no universal findings-collapse count is asserted. PR-history indexing and its finding-recommendation agent are beta for GitHub/GitLab, with Bitbucket and Azure DevOps listed as coming soon. Agent skills can fetch rules and resolve PR findings in a compatible coding agent; this is distinct from automatic changes by the PR reviewer.

Pricing (verified). Pro Team uses pooled workspace credits, not per-seat billing: $0.012/credit, with a $30 2,500-credit pack (~18 reviews/month by Qodo's estimate); 5,000 and 20,000 credits are estimated at ~36/~144 reviews. The pricing page markets Pro Team for up to 30 users and Enterprise for 30+, while the billing docs describe unlimited Pro Teams users; confirm the selected workspace's entitlement. Monthly billing, no annual self-serve commitment. Credits expire monthly without rollover; overage uses the same credit rate up to a customer-set cap. The 14-day trial has unlimited credits and no card. Enterprise adds SSO, BYOK, single-tenant or on-premises deployment. No permanent free tier; qualified OSS projects can apply for free access.

Hourly / throughput. No published per-developer hourly PR cap. The Pro Team pricing page states “No rate limits”; usage is pooled workspace credits with overage up to a configurable monthly spending cap. Docs also say reviews can skip until the next billing cycle if a monthly review limit is hit, and GitHub’s own hourly API rate limit can delay processing. After the trial, usage stops unless paid billing is active.

Trial. 14-day trial with unlimited credits, no card. Trial is the initial state of every workspace, not a separate plan.

Watch out. Credit packs and the workspace spending cap determine paid usage; “No rate limits” does not mean unlimited included reviews. Credits expire monthly and overage uses the base credit rate. Pricing and billing docs disagree on the Pro Team user ceiling, so confirm the selected entitlement. Single-tenant and on-premises deployment are Enterprise-only; the installation matrix lists Gerrit and Bitbucket Data Center for on-premises. Git-provider features differ: PR-history indexing is beta on GitHub/GitLab, and Bitbucket/Gerrit do not support collapsible finding sections. No provider-wide autofix or merge-enforcement capability is inferred from agent skills or configuration options.

Compare Qodo

vs

Qodo vs CodeRabbit

vs

Qodo vs Gitar

vs

Qodo vs Greptile

vs

Qodo vs GitHub Copilot code review

Common questions

Questions about Qodo

Answered from the verified figures on this page rather than general guidance.

What is Qodo?
A governance-heavy reviewer: rules, cross-repo context, and analytics aimed at teams drowning in AI-generated PRs — not only a comment bot. It reviews on GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit (on-premises) as pr review, ide, and agent skills.
How does Qodo price reviews?
Pro Team uses pooled workspace credits, not per-seat billing: $0.012/credit, with a $30 2,500-credit pack (~18 reviews/month by Qodo's estimate); 5,000 and 20,000 credits are estimated at ~36/~144 reviews. The pricing page markets Pro Team for up to 30 users and Enterprise for 30+, while the billing docs describe unlimited Pro Teams users; confirm the selected workspace's entitlement. Monthly billing, no annual self-serve commitment. Credits expire monthly without rollover; overage uses the same credit rate up to a customer-set cap. The 14-day trial has unlimited credits and no card. Enterprise adds SSO, BYOK, single-tenant or on-premises deployment. No permanent free tier; qualified OSS projects can apply for free access.
What is the hourly or throughput limit for Qodo?
No published per-developer hourly PR cap. The Pro Team pricing page states “No rate limits”; usage is pooled workspace credits with overage up to a configurable monthly spending cap. Docs also say reviews can skip until the next billing cycle if a monthly review limit is hit, and GitHub’s own hourly API rate limit can delay processing. After the trial, usage stops unless paid billing is active.
Is there a trial for Qodo?
14-day trial with unlimited credits, no card. Trial is the initial state of every workspace, not a separate plan.
Does Qodo autofix or block merges?
Autofix: Not verified. Merge gate: Not verified. Vendor-documented multi-agent review, codebase context, governance rules and agent skills. Findings appear in summary and/or inline views depending on configuration and Git-provider capabilities; no universal findings-collapse count is asserted. PR-history indexing and its finding-recommendation agent are beta for GitHub/GitLab, with Bitbucket and Azure DevOps listed as coming soon. Agent skills can fetch rules and resolve PR findings in a compatible coding agent; this is distinct from automatic changes by the PR reviewer.
What is the catch with Qodo?
Credit packs and the workspace spending cap determine paid usage; “No rate limits” does not mean unlimited included reviews. Credits expire monthly and overage uses the base credit rate. Pricing and billing docs disagree on the Pro Team user ceiling, so confirm the selected entitlement. Single-tenant and on-premises deployment are Enterprise-only; the installation matrix lists Gerrit and Bitbucket Data Center for on-premises. Git-provider features differ: PR-history indexing is beta on GitHub/GitLab, and Bitbucket/Gerrit do not support collapsible finding sections. No provider-wide autofix or merge-enforcement capability is inferred from agent skills or configuration options.