Kodus

Tool snapshot
Best fitDeveloper Tools
In one lineKodus reviews pull requests using repository context, team rules and linked requirements. Its AGPL core can be self-hosted, while bring-your-own model keys keep provider usage...

Kodus is a pull-request review platform with an open-source core and hosted or self-hosted options. The official site describes Kody reading diffs, mapping related code and posting review comments inside the Git-provider workflow. Teams can configure review rules and discuss findings in the pull request.

Give the reviewer useful context

Kody maps callers, callees and tests around a change, including code in linked repositories. Teams can write rules in plain language or import existing instructions from files such as AGENTS.md and CLAUDE.md. Requirements can also come from Jira, Linear or Notion.

Choose rules that express a real project constraint, and inspect whether a finding demonstrates a violation. A generated comment is an engineering review input; it should not substitute for tests or a maintainer's understanding of the change.

Greptile also reviews pull requests with repository context and plain-language standards. Compare the review evidence, supported deployment and billing model on representative changes rather than assuming either service catches every cross-file issue.

Decide where code and model calls go

Kodus lists GitHub, GitLab, Bitbucket, Azure DevOps and Forgejo/Gitea support, with particular self-managed routes and a beta qualifier for GitHub Enterprise Server. Confirm your provider and required repository scope before installation.

The core is AGPL-licensed, and self-host setup is described through Docker Compose or Helm. Bring-your-own-key use can target a supported provider or OpenAI-compatible endpoint, including a self-hosted model. Self-hosting the application does not itself prove that a selected external model keeps inference inside your infrastructure.

The publisher says it does not store source code or train on customer data. Review those terms alongside the chosen model provider's data controls and your integration permissions. Access can be controlled and revoked through the Git-provider connection.

Separate platform access from model cost

The pricing page distinguishes Community, Teams and Enterprise. Community includes limited counts for rules and active plugins, while paid offers add capabilities and support. The trial includes a bounded number of reviews; it is distinct from ongoing bring-your-own-key operation.

Kodus describes no added markup on provider tokens. With your own key, provider rate limits still apply, and larger diffs or more reviews increase model usage. Unlimited PR review access does not establish a zero-cost model bill.

Track useful findings, false alarms and missed issues during a pilot. Team feedback can become saved review memory, so inspect what gets retained before turning one correction into a rule for future changes.