Konrad Sopala
April 09, 2026
3 min read
April 09, 2026
3 min read
Share
Cut code review time & bugs by 50%
Most installed AI app on GitHub and GitLab
Free 14-day trial
Think about your last big sprint.
You're pushing through a high-velocity release. The whole org is shipping in parallel. Large PRs are stacking up. CodeRabbit has been reviewing everything, keeping pace as always.
Then it stops as you've hit your plan's review limit.
You start asking:
Now what? Do we wait for the reset? Should half the team pause? Are we merging without review?
Now you have more options to tackle that.
The PR Usage-based Add-on lets your team keep reviewing PRs even after hitting a subscription limit - without upgrading your plan, manual intervention or per-reviewer setup.
Once enabled through CodeRabbit dashboard, the rabbit automatically continues processing PR reviews beyond the limit, billing only the over-limit usage as pay-per-use. Credits kick in after the limit is reached, not before. Your regular usage stays on your plan. Only the overflow gets charged.
The mental model is simple. Your subscription covers your baseline. If your team has a burst like a large rollout, a complex refactoring sprint, an unusually active week, the add-on acts as a pressure valve.
Here's what happens:
Admins manage the add-on from the CodeRabbit dashboard via an org-level pay-per-use toggle. Reviewers don't need a separate billing configuration. They don't need to do anything differently per PR. Once an admin enables the add-on, the system handles the rest.
Speaking of which: if your team uses the CodeRabbit CLI to trigger reviews, the same rules apply. CLI-originated reviews follow the same billing path and the same opt-in logic as reviews from GitHub, GitLab or Bitbucket PR pages. You don't manage two different systems. There's one toggle, credit balance and billing path.
You could. But not every team that occasionally bursts past their limit actually needs a higher tier month after month.
Things like big sprints, org-wide rollout happens, genuinely gnarly PRs are rather irregular events. Paying for a permanently higher plan to handle occasional spikes isn't the right trade-off for every team.
The add-on is designed for exactly that. You pay for what you use, when you use it.
The PR Usage-based Add-on is available now. Head to your CodeRabbit dashboard, turn on pay-per-use in org settings, and make sure you have credits loaded.
