Billing Tied to Pull Request Creators

CodeRabbit has chosen the meter that sits closest to actual code output, which makes revenue rise with development activity rather than org chart size. In practice, a company does not pay for every employee who can view a repo. It pays for the people, and eventually the agents, that open pull requests and trigger reviews. As AI tools increase PR volume, that turns more software output directly into billable usage.1 2

• This is a cleaner fit for how the product works. CodeRabbit lives inside GitHub, GitLab, and Azure DevOps pull requests, where it posts inline comments, summaries, diagrams, and security findings. Charging on PR creators lines the bill up with the users who actually generate review work.2 3
• It also widens the paid user base over time. Older developer tools often sold seats to a fixed engineering team. CodeRabbit can add product managers, designers, contractors, or AI coding agents once they start shipping code through PRs, because each new code producer creates review load and a natural reason to pay.1 2
• That helps explain the speed of expansion. CodeRabbit scaled from an estimated $25M ARR at the end of 2025 to $50M by July 2026, while building on a funnel of 100,000 plus open source projects, 8,000 plus paying customers, and top installation rank on GitHub Marketplace. More PR creators means more chances to convert free usage into paid seats.1 2

The next phase is that AI code generation and AI code review start compounding each other. As coding agents create more pull requests, tools priced on PR creators become usage ramps rather than fixed seat contracts. That should favor review products that stay embedded in the PR workflow and can monetize every new source of code creation.2