Skip to main content

Buyer guide

Qodo Credits & Review Spend Checklist

Qodo's trial ends with no free tier to fall back on. Work out credits from your pull request count, cap overages, and have billing live before reviews stop.

Reading time
2 min read
Sources
8 cited
In this piece
Qodo+17 Mixed

Turn on paid billing before day 14, because Qodo stops reviewing when the trial ends and has no permanent free tier. Every review draws from one workspace credit pool. Size the pack from your pull request volume and set an overage cap before coding agents start pushing.

When you need this

  • Your 14-day trial is running, or has just ended and reviews stopped.
  • Coding agents open pull requests and push many times per change.
  • Finance asks what a reviewed pull request costs.

Evaluation criteria

  1. Know what the trial ends with

    What happens on day 15?

    Look forUsage stops when the 14-day trial ends. In ptr727's repository, Qodo's paid identity posted only a billing-blocked notice, and no Qodo review had appeared since at least pull request #1450. On Amayyas's ChessTrainer, a pull request merged with green checks and no review at all.

  2. Check the open source route

    Do your public repositories qualify for free reviews?

    Look forFree reviews require an actively maintained public GitHub repository with 200 or more stars, or an organization that has one. Rules and PR History still require payment. DotNetWorkQueue sat below 200 stars and lost Qodo when its trial ended.

  3. Estimate credits per review

    How many reviews does a pack buy?

    Look forMeasure credits per review on the billing page during the trial. Qodo estimates 2,500 credits for about 18 reviews, 5,000 for about 36, and 20,000 for about 144. That works out to roughly 139 credits, or US$1.67, per review (GILD calculation). Larger and more complex pull requests use more.

  4. Size the pack

    Which pack covers a month?

    Look forMultiply pull requests per month by reviews per pull request and by your measured credits per review. At Qodo's estimate, 100 pull requests reviewed once each need about 13,900 credits, about US$167 a month (GILD calculation).

  5. Set the overage cap

    What happens past the pack?

    Look forSet the overage cap before agent-written pull requests arrive. Qodo bills overage at the base per-credit rate up to your monthly cap. Credits expire at the end of each monthly cycle.

  6. Price accepted findings

    What does a finding your team acts on cost?

    Look forDivide monthly spend by accepted findings in the analytics dashboard, currently in beta. It separates accepted findings from dismissed or unaccepted ones. Compare that cost with a per-seat reviewer.

  7. Count the users

    Does Pro Team fit your team?

    Look forPro Team has no user limit: Qodo's FAQ says to add as many users as you need, and its billing docs list unlimited users per workspace. The 30-user figure on the pricing card is sizing guidance. Enterprise requires an annual contract with a master services agreement (MSA) and a data processing agreement (DPA).

Questions to ask vendors

  1. How many pull requests, and pushes per pull request, do our repositories see in a month?
  2. How many credits did a typical review draw during our trial?
  3. Which repositories should Qodo review, and which can rely on a cheaper first pass?
  4. Who is alerted when overage nears the cap?

Red flags

  • A merge gate that depends on Qodo with no plan for the trial's end.
  • Reviews on every push of agent-driven pull requests with no overage cap.
  • Comparing Qodo's pack price with per-seat prices without counting reviews per month.
  • Assuming open source repositories are free without checking the 200-star rule.

Products in this piece

Sources

Official documentation
4
Public source
4
  1. Qodo pricingOfficial documentationqodo.ai
  2. Qodo docs: Pricing & usageOfficial documentationdocs.qodo.ai
  3. Qodo docs: Qodo for Open Source ProjectsOfficial documentationdocs.qodo.ai
  4. Qodo docs: Code review analyticsOfficial documentationdocs.qodo.ai
  5. ptr727 ProjectTemplate issue #1465: Qodo no longer reviews this repository (Sep 9, 2026)Public sourcegithub.com
  6. ChessTrainer pull request #61: replace the paused reviewer (Sep 1, 2026)Public sourcegithub.com
  7. bountydesk pull request #103: Drop the Qodo review gate (Sep 11, 2026)Public sourcegithub.com
  8. DotNetWorkQueue issue #362: Evaluate a replacement for qodo PR review, trial ended (Sep 17, 2026)Public sourcegithub.com