- Who can receive PR reviews
- How monthly limits work
- What to do when reviews pause
- How review eligibility works
Check your plan
- Log in to the Qodo Management Portal.
- Locate your username in the bottom-left corner of the portal.
- Click your username to open the account menu.
- Your plan is added to the Account settings.
Plans at a glance
Qodo reviews a pull request when the PR author meets the eligibility rules for their plan. If you maintain a public open-source repository, see Qodo for Open Source Projects.Free plan (Developer)
Each Git user gets up to 30 reviews per Git organization per month. The allowance is counted separately for each Git organization the user contributes to.Once a user reaches the limit in the given org:
- Qodo pauses reviews for that user in the organization until the next monthly reset.
- Other users in the same repository are unaffected.
Teams plan
Reviews run for a developer when both of these are true:- The developer has an assigned paid seat in the Qodo Management Portal.
- The developer’s Git account is linked to their Qodo account.
- Qodo will not review PRs under the Teams plan.
- The developer falls back to Free-tier behavior (30 feedbacks per Git organization per month).
Enterprise plan
The entire Git organization is whitelisted at the organization level. With Enterprise:- Individual users do not need paid seats assigned to receive reviews.
- There is no per-user review limit.
What you’ll see when reviews are paused
When Qodo cannot review a PR because of plan eligibility, it posts a comment on the pull request explaining why and what to do next.Free plan
Situation: Monthly quota reached (30-review limit)Qodo reviews are paused for this user.
This Git user has reached the monthly free-tier review limit (30 reviews) for this Git organization. Reviews resume on the next monthly reset, or you can upgrade your plan to continue now. If you already have a paid seat on a Teams or Enterprise plan, link your Git account so future reviews run under that plan.
Teams plan
Situation: Missing seat or unlinked Git accountQodo reviews are paused for this user.
Reviews on the Teams plan require the developer to have a paid seat and a linked Git account in Qodo. Assign this user a seat in the Qodo Management Portal and have them link their Git account to continue reviews under your team plan.
Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? These deployments require an Enterprise plan.
Enterprise plan
Situation: Unexpected pause messageEnterprise customers are whitelisted at the organization level and should not see paused-review messages. If you do, contact support.
How to continue reviews
| Situation | What to do |
|---|---|
| Free user hit the 30-review monthly limit in a Git org | Wait for the monthly reset, or upgrade to Teams or Enterprise |
| Teams customer, developer has no seat | Assign the developer a seat in the Management Portal |
| Teams customer, developer has a seat but reviews still skipped | Link the developer’s Git account to their Qodo account |
| Self-managed Git (GitHub Enterprise Server / GitLab Self-Managed / Bitbucket Data Center) | These deployments are supported on the Enterprise plan only. Contact us |
| Enterprise customer seeing paused-review messages | Contact support — the whole Git org should be enabled |
Linking a Git account
Linking tells Qodo that a Git identity (for example, octocat on GitHub) belongs to a paid seat.Without linking:
- Qodo treats the PR author as an unidentified user.
- Free-tier limits are applied.
- Sign in at https://app.qodo.ai
- Open Account settings
-
Under Linked accounts, connect each Git provider:
- GitHub
- GitLab
- Bitbucket
- Azure DevOps
- Ensure the linked identity matches the one used in your PRs.