Qodo pricing

About

Qodo (formerly Codium AI) is an AI code-integrity platform built around three surfaces: Qodo Gen (an IDE plugin for in-editor code review and test generation), Qodo Merge (a pull-request review agent), and Qodo Command (a CLI for agentic quality workflows). It positions itself as “the AI code review platform for the enterprise,” targeting individual developers up through large engineering organizations with distributed, multi-repo codebases.

The company markets strong adoption signals — a 4.7 rating across the VS Code and JetBrains marketplaces, over 40K weekly active users, and roughly 1,000 weekly active companies. Its differentiation centers on context-aware review across services and repositories, enforceable organization-wide quality standards, and security posture (SOC 2 Type II, two-way encryption, secrets obfuscation, and deployment options up to on-prem / air-gapped).

Qodo serves developers, team leads, and enterprise engineering leaders who want automated PR review, test generation, and policy enforcement embedded in the IDE, CLI, and Git workflow rather than bolted on after the fact.

Pricing summary : per-seat tiers with a credit-metered IDE/CLI usage layer

Qodo prices on per-seat subscription with a usage layer underneath: a free Developer plan, a paid Teams plan shown at $30/user/month (annual billing, “Save 21%”), and a custom-quoted Enterprise plan. Seat price is the headline dimension, but actual day-to-day usage inside Qodo Gen and the CLI is metered in credits, and PR-review volume on Teams is capped at 20 PRs/user/month.

The billing dimensions are:

• Seats — billed per user/month on Teams; Enterprise is quoted by seats, repos, and deployment model.
• PR-review volume — Teams includes 20 PRs per user per month.
• Credits — every LLM network request or MCP tool call costs credits inside Qodo Gen / CLI. Most operations cost 1 credit; premium models cost more (Claude Opus = 5 credits/request, Grok 4 = 4 credits/request). Credits reset every 30 days from the date of the first message, not on a calendar boundary.
• Deployment — Enterprise adds SaaS (single/multi-tenant), private cloud, and on-prem / air-gapped options.

What makes this different: Qodo blends a simple per-seat headline with a hidden, model-tiered credit meter underneath — usage limits surface only when a developer exhausts the monthly credit allowance, and overage purchasing (“buy additional credit bundles”, pay-as-you-go) is advertised as coming soon rather than live.

Pricing by product

Qodo platform (Individual & Team plans)

Qodo Command / Enterprise deployment

Sales motions across products: PLG / self-serve for Developer and Teams; sales-led for Enterprise.

Hidden costs : credit burn on premium models and the no-overage wall

The headline Teams price ($30/user/month) is clean, but two mechanics drive real cost: the 2,500-credit monthly allowance and premium-model multipliers. Most requests cost 1 credit, but Claude Opus costs 5 and Grok 4 costs 4 credits per request — so a developer who leans on premium models can exhaust a month’s credits in a fraction of the requests a 1-credit user gets. And because there is no way to buy more credits yet, hitting the limit means waiting up to 30 days for the reset rather than paying an overage.

A 5-person Teams squad ($30/user/mo, annual) that runs Qodo Merge near its 20-PRs/user/month cap and uses premium models heavily:

The hidden cost here is not a surprise bill — it is a productivity wall. A heavy Opus user on Teams burns the 2,500-credit pool in roughly 500 premium requests, after which there is no paid escape hatch until the rolling reset. SSO is also an add-on cost on Teams (it is bundled only at Enterprise). For predictable high-volume usage, the only fix today is a sales-led Enterprise quote.

Want to estimate your own Qodo bill? Use the Qodo pricing calculator to model your monthly cost based on seats, PR-review volume, and premium-model credit burn.

Pricing evolution : from CodiumAI’s free tools to a credit-metered seat model

Cadence

Tracked range: 2024 Q3–2026 Q2 (qodo.ai/pricing Wayback snapshots). Earlier CodiumAI pricing pre-dates the qodo.ai domain and is reconstructed from press coverage. Quarters not listed were verified stable.

Notable changes

• 2022 — CodiumAI founded by Itamar Friedman and Dedy Kredo around test generation and code integrity.
• 2023-03 — $11M seed round; exits stealth. Open-source PR-Agent released (later Qodo Merge).
• 2024-01 — AlphaCodium open-source paper published; outperforms Google DeepMind’s AlphaCode on CodeContests (a strong community-credibility moment, 87-point Hacker News thread on the System-2/AlphaCodium write-up).
• 2024-09-30 — Rebrand to Qodo + $40M Series A (Susa Ventures, Square Peg). Teams = $19/user/mo, usage explicitly unmetered.
• 2025-03 — Teams cut to $15; Enterprise price made visible at “Starting at $45/user/mo”.
• 2025-05 — First usage meter (“messages”) layered onto the per-seat price.
• 2025-07 — Teams doubled to $30 and the meter became credit-based with premium-model multipliers; Qodo Command CLI launched.
• 2025-09 — Free-tier allowance tightened to 75 credits/month; Enterprise reverts to opaque “Contact us”.

The shift from unlimited to credit-metered in detail

The most consequential change is not a single price move but the mid-2025 transition from “no restrictions on calls/tokens or repositories” to a hard credit meter. At the rebrand (Sep 2024) Qodo sold a simple per-seat promise with unlimited usage. By mid-2025 it had: (1) introduced a message cap, (2) renamed it to credits, (3) made premium models cost 4–5× a normal request, (4) halved the Teams allowance while doubling the price, and (5) tightened the free tier from 250 to 75 credits. The same quarter that introduced credits doubled the Teams seat price — a rare case of a vendor raising the seat fee and adding a usage cap simultaneously, effectively repricing the product twice in one move. Critically, the overage path (buy-more-credits, pay-as-you-go) is still “coming soon,” so the meter today functions purely as a hard ceiling rather than a revenue lever.

What’s unique : code-review-first positioning with a hybrid seat-plus-credit meter

1. Code review as the wedge, not autocomplete. Unlike Copilot- or Cursor-style assistants that lead with completion, Qodo’s headline surface is PR review and test generation (Qodo Merge + Qodo Gen). Pricing reflects this: the Teams cap is denominated in PRs per user per month (20), a value metric tied to review volume rather than tokens. This is a different value-metric choice than most coding-assistant peers.

2. A hybrid seat-plus-credit model that arrived late. Qodo spent its first year as a pure per-seat product with unlimited usage, then bolted on a credit-based usage meter in 2025. The result is a hybrid pricing model where seats are the headline but credits are the real constraint — the opposite migration path from vendors that started usage-metered and added seats.

3. Premium-model credit multipliers. Rather than a flat per-request charge, Qodo prices by model cost: 1 credit for standard models, 4 for Grok 4, 5 for Claude Opus. This passes foundation-model economics through to the buyer transparently, but makes a developer’s monthly capacity depend on which model they pick — an unusual coupling of model choice to plan limits.

4. A 30-day rolling reset, not a calendar month. Credits reset 30 days from each user’s first message, so two teammates on identical plans can hit their ceilings on different days. This avoids a synchronized month-end usage spike but makes team-level capacity planning harder.

5. Deployment as the Enterprise lever. The Enterprise tier’s differentiation is less about features and more about deployment — SaaS, private cloud, on-prem, and air-gapped, with self-hosted proprietary Qodo models. For regulated buyers, deployment model (not seat count) is the primary pricing variable.

Strengths & weaknesses

Billing UX : credit meter, quota speedometer, and a 30-day rolling reset

• Monthly/Annually toggle on the pricing page, with an explicit “Save 21%” annual-discount label.
• Per-seat Teams checkout (“Get Started”) with a 20 PRs/user/month allowance.
• Credit meter — every LLM request or MCP tool call inside Qodo Gen / CLI consumes credits; most operations are 1 credit, premium models cost more (Claude Opus 5 credits, Grok 4 4 credits).
• Quota “speedometer” icon (“Show quota”) at the top of Qodo Gen chat to check remaining credit balance and the next reset date.
• 30-day rolling reset — credits reset 30 days from the first message sent, not on a calendar month boundary.
• Usage-limit interstitial — a limit message appears when monthly credits are exhausted; today the only remedy is waiting for the reset (buy-more-credits, higher allowances, and pay-as-you-go with spend controls are advertised as “coming soon”).
• Enterprise demo path — a “Request a 30-Minute Executive Demo” / “Book a Demo” form for custom Enterprise quotes and deployment selection.

Strategic wins : decisions that worked in Qodo’s pricing playbook

1. Leading with code review, not autocomplete

By denominating its paid value in PR reviews per user per month rather than tokens or completions, Qodo anchored its price to a metric buyers already track and value (review throughput). This sidesteps the token-anxiety problem that plagues completion-first tools and ties cost to a visible business outcome — a textbook value-metric selection. It also positions Qodo against incumbents like GitHub Copilot on a different axis (quality/governance) rather than competing head-on on completion quality.

2. Keeping a genuinely usable free tier

The Developer tier remained free through every repricing, preserving Qodo’s product-led growth funnel and its open-source credibility (PR-Agent, AlphaCodium). For a tool whose adoption is bottom-up among developers, free access is the acquisition engine — and Qodo’s “40K weekly active users” claim depends on it.

3. Transparent per-model credit costs

Publishing exact credit costs per model (Opus 5, Grok 4 4, everything else 1) is unusually honest usage-based pricing communication. It lets a developer reason about capacity before committing, and it cleanly passes through the reality that premium foundation models cost the vendor more — avoiding the margin-erosion trap of flat-rate unlimited usage.

4. Deployment as the Enterprise upsell

Rather than gating core features, Qodo reserves deployment flexibility (on-prem, air-gapped, self-hosted models) for Enterprise. For regulated buyers this is the single highest-value lever, and it lets Qodo keep the self-serve tiers feature-rich while still having a compelling sales-led story. This mirrors how other enterprise AI vendors structure their gates.

Areas to improve : gaps that create friction for Qodo buyers

1. Ship the overage path before the wall

Today, exhausting credits means waiting up to 30 days with no paid escape. Concrete fix: launch the already-advertised buy-more-credits bundles and pay-as-you-go with spend caps, so heavy users can keep working without jumping to a sales-led Enterprise quote. A hard ceiling with no overage is the worst of both worlds — it caps revenue and frustrates the most engaged users. See bill shock and cost unpredictability.

2. Show both Teams rates side-by-side, not behind a toggle

The pricing page defaults to the annual rate ($30/user/mo, “Save 21%”) and only reveals the $38/user/mo month-to-month rate after flipping the Monthly/Annually toggle. Concrete fix: display both monthly ($38) and annual ($30) rates on the same view so buyers can see the true discount without toggling — and so $30 is not mistaken for the month-to-month price.

3. Stabilize and re-expose Enterprise pricing

Enterprise briefly carried a public “Starting at $45/user/month” anchor in early-to-mid 2025, then reverted to “Contact us.” Concrete fix: restore a public starting price or band. A visible anchor shortens sales cycles for mid-market buyers who self-disqualify when there is no number at all — a known pricing-transparency advantage.

Key takeaways

1. A clean seat headline can mask the real constraint. Qodo’s $30/user/mo looks simple, but the binding limit is the 2,500-credit pool — buyers should price on credit burn, not seats.
2. Adding a usage meter to a previously unlimited product is a repricing event. Qodo doubled the seat price and introduced credits in the same quarter; teams that grandfathered into “unlimited” felt two changes at once.
3. Premium-model multipliers couple plan capacity to model choice. A team standardizing on Claude Opus gets ~5× less effective capacity than one on standard models for the same plan.
4. A hard cap with no overage is a productivity risk, not just a billing one. Without a pay-as-you-go path, the meter blocks work rather than generating incremental revenue — a strategic gap.
5. Deployment, not features, is the cleanest enterprise lever for regulated buyers. Qodo’s on-prem/air-gapped story justifies a custom quote without crippling the self-serve tiers.

UBP implications

1. The seat-to-credit migration path is becoming common in AI coding tools. Qodo started per-seat-unlimited and added credits under cost pressure; this “seat first, meter later” pattern is the inverse of usage-native startups and signals that flat-unlimited is unsustainable once foundation-model costs bite.
2. Pass-through model pricing is a viable UBP design. Charging credits proportional to underlying model cost (1× standard, 4–5× premium) keeps margins intact while staying legible to buyers — a replicable template for any AI product reselling multiple models.
3. An overage path is table stakes for credit systems. Qodo demonstrates the failure mode of shipping a meter without a way to exceed it: the cap caps revenue and annoys power users. Usage-based pricing only works when crossing the line costs money, not productivity.

Sources

• Qodo pricing page (accessed 2026-06-03) — Teams monthly $38 / annual $30 split independently re-verified 2026-06-04
• Qodo Enterprise solution page (accessed 2026-06-03)
• Qodo “Book a Demo” page (accessed 2026-06-03)
• Qodo blog: Introducing Qodo (formerly Codium) (accessed 2026-06-03)
• Qodo blog: $50M total funding announcement (accessed 2026-06-03)
• Qodo help center: Understanding Credits in Qodo (accessed 2026-06-03)
• Qodo documentation: Subscription Plans (accessed 2026-06-03)
• Browse the full pricing blueprint corpus for peer AI-coding companies.

Bottom line

Qodo’s pricing tells the story of a category maturing: a free-and-unlimited CodiumAI grew into a credit-metered, seat-priced Qodo as foundation-model economics caught up with it. The $30/user/mo Teams plan is easy to budget but the 2,500-credit pool — and the absence of any way to buy more — is the real constraint buyers must model. With strong open-source credibility, an honest per-model credit table, and a deployment-led enterprise motion, Qodo is well-positioned; closing the overage gap and re-exposing Enterprise pricing would remove its sharpest friction points.

Compare Qodo against other AI-coding pricing models in the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

Current snapshot — Developer / Teams / Enterprise

Jun 2026

Qodo prices its AI code-review platform on three per-seat tiers: a free Developer plan, a Teams plan shown at $30/user/month (annual billing, 'Save 21%') with a 20 PRs/user/month cap, and a contact-sales Enterprise plan adding the Qodo Command CLI, multi-repo context engine, SSO, and on-prem/air-gapped deployment. Usage inside the IDE/CLI is metered in credits (1 credit/request; premium models cost more, e.g. Claude Opus 5 credits, Grok 4 4 credits) that reset every 30 days. Teams is billed at $38/user/month month-to-month or $30/user/month on annual billing (the 'Save 21%' discount).

Free tier tightened to 75 credits; Enterprise returns to Custom

Sep 2025

Wayback snapshot shows the free Developer allowance cut from 250 to 75 credits per month (and 75 PRs/month on Qodo Merge); the previously visible Enterprise '$45/user/month' is replaced with 'Contact us'. Teams holds at $30/user/month with 2,500 credits. Supported models update to GPT-4.1/o3/o4-mini, Claude 4 Sonnet, Gemini 2.5 Pro, with Claude 4 Opus and Grok 4 Enterprise-only.

Teams doubles to $30; credits replace messages; Qodo Command launches

Jul 2025

Wayback snapshot shows Teams jump from $15 to $30/user/month while the allowance is roughly halved (5,000 messages → 2,500 credits); the meter is renamed 'credits'. Qodo Command (CLI for agentic workflows, 'in Alpha') is added across plans. Premium-model multipliers (Claude Opus 5 credits, Grok 4 4 credits) appear.

Message metering introduced

May 2025

Wayback snapshot adds usage allowances: Teams stays at $15/user/month but is now '5,000 messages', and the free Developer tier is capped at '250 messages & tool use per month'. This is the first metered usage layer on top of the per-seat price — the transition away from the earlier 'unlimited' promise.

Teams drops to $15; Enterprise price surfaces at $45

Mar 2025

Wayback snapshot shows the Teams seat price lowered to $15/user/month and, for the first time, a visible Enterprise price of 'Starting at $45/user/month'. Usage is still unmetered (no credits). AI model selection (GPT-4o, o3-mini, Claude 3.5 Sonnet, self-hosted DeepSeek-R1, Gemini 2.0 Flash) is shown across plans.

Rebrand to Qodo + $40M Series A

Sep 2024

CodiumAI rebrands to Qodo and raises a $40M Series A led by Susa Ventures and Square Peg (total funding ~$50M). The pricing page shows Developer (free), Teams at $19/user/month with a 14-day trial, and a custom Enterprise plan. The page explicitly states 'no restrictions on the number of calls/tokens or repositories' — there is no credit meter yet. Products: Qodo Gen (IDE), Qodo Merge (Git agent), Qodo Cover (CLI agent).

$11M seed, exits stealth

Mar 2023

CodiumAI exits stealth with an $11M seed round co-led by Vine Ventures and TLV Partners, with angels from OpenAI, Snyk and VMware. The flagship is Codiumate (IDE test generation); the open-source PR-Agent (later Qodo Merge) is released around this period. Pricing is free / freemium.

CodiumAI founded

Jan 1970

CodiumAI is founded by Itamar Friedman (CEO, formerly director of Alibaba's Israel AI lab) and Dedy Kredo (CPO) to build a generative-AI 'code integrity' platform focused on test generation and bug detection. The product is free during early access.