The use case: how Clerk deploys CodeRabbit
Clerk's engineers use CodeRabbit as an always-on first reviewer on pull requests, catching bugs, security weaknesses and specification violations (such as incorrect OAuth error codes) before human reviewers look at the code. This lets human reviewers focus on design and architecture.
More reported results
Figures published in CodeRabbit’s case study. They are not independently measured by usedby.
Clerk’s 70% acceptance rate of all potential bugs CodeRabbit flags shows the tool has earned trust.
95% of the PRs that I open, I can get a review really quickly.
In the customer’s words
Since adopting CodeRabbit, our confidence is up and our bugs are down; it catches the edge cases humans skim past and helps us merge faster with more confidence.Other AI tools used by Clerk
Other public relationships recorded on usedby.
Explore Clerk’s AI stackCodeRabbit users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
See all CodeRabbit customersGo straight to the source
Based on CodeRabbit’s published case study. We check the public evidence; the results are reported by the vendor.
coderabbit.ai- Last checked
- Nov 10, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 40%Checked
Printed word for word on the page, near the name of Clerk.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Clerk.
- Clerk uses CodeRabbitChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Thanks to CodeRabbit, the Clerk team was able to merge their PRs 40% faster. Brandon credits CodeRabbit for catching bugs early, before they trigger rejection cycles.








