An AI code reviewer is a CI job on two of the three forges, and the third has no job runner at all. On GitLab the review runs on a runner you tag yourself, on Azure Repos it competes for organization-level parallel jobs, and on Bitbucket Data Center it runs inside whatever build server you already operate. What limits the review in each case is the queue for compute, not the model behind it.
That distinction gets lost because almost every comparison of AI review tools talks about models, prompts, and findings. The compute side decides whether a review appears at all, and each forge hands you a different amount of control over it.
On GitLab the reviewer runs on a tagged runner
GitLab's Code Review Flow is explicit about this. Its prerequisites include configuring your own runners with the gitlab--duo tag and an executor that supports Docker images, or turning on GitLab hosted runners for the project. The flow runs as a CI/CD job and needs a runner to execute.…