Kodus offers BYOK Community and Teams plans, with provider-token costs added separately. Cubic Team includes managed review and custom agents within reviewed-line allowances. Both support local changes and saved review guidance, so compare total analysis costs and configuration needs.
Code Review Guide · Reviewed October 14, 2026 · Published by Perch / Verglas LLC
Kodus and Cubic at a glance
Documented review inputs, requirements and licensing
Decision
Kodus
Cubic
Review scope
PR, local, CI and agent review; CLI trial has file and line limits.
PR and local review with plan-specific reviewed-line allowances.
Local review input
CLI checks uncommitted, staged, branch and commit changes.
cubic review checks uncommitted edits or changes against a base branch.
Custom requirements
English Kody Rules; Community includes 10 rules.
cubic.yaml custom agents; Team includes 5 agents.
License and service
Public CLI describes an MIT license; backend core is AGPLv3 with enterprise exceptions.
Compare provider-token costs with a managed line allowance
Use the same saved requirement and local changes. Record Kodus model-provider charges and rule count, alongside Cubic reviewed lines, custom agents and any extra-line charges.
Kodus billing
Community is free BYOK; Teams is $10/developer/month monthly or $8 annually, plus model-provider tokens.
Teams annual subscription floor before provider tokens. Free Community is available; its BYOK cost varies. Compare the CLI and backend licenses separately.
Team: $30/developer/month billed yearly. Starter includes 20 PR reviews/month free.
Team annual subscription floor, including 40,000 reviewed lines per seat per period; extra lines cost $20/10,000. Flex usage settings affect whether reviews pause.
Subscription amounts are plan floors or quoted allowances. Repeated reviews, selected effort, provider charges and exclusions can change the bill. Equal review counts do not establish equal analysis scope.
A third option for the agent’s next edit
When Perch is the better choice
Perch is a stronger fit for named semantic requirements with hosted analysis included in the fresh-check rate. A selected rule can be rerun after a repair without a per-developer subscription.
For an agent that repeatedly removes tenant authorization from a database update, save the requirement as a named Perch rule:
- name: tenant-scoped-update
where: "orders.py"
ensure: >-
The cancellation UPDATE must constrain tenant_id to actor.tenant_id
before changing the order. An id-only or owner-only update breaks
this requirement.
This requirement comes from the FastAPI tenant-authorization recipe, which includes the implementation, deliberate regression and captured Perch checks. The same named check can run against the working file after the next agent edit. Perch working-file checks support selecting rules directly; rule selectors cover project, file and method scope.
Use the setup command for your coding agent. Download the focused pack without replacing existing files:
curl -fL 'https://reporules.fyi/fastapi/tenant-cancellation/rule-pack.zip' -o tenant-rule.zip
unzip -n tenant-rule.zip
perch check orders.py --rules tenant-scoped-update --json
# Repair the reported finding after the agent edit.
perch check orders.py --rules tenant-scoped-update --json
Keep your existing root perch.yaml. The ZIP adds its focused rule under .perch/rules/; unzip -n preserves existing files. Review and adapt the selector and application path before running it in your repository. Run the saved check after an edit, repair any finding, and repeat the identical check alongside application regression tests.
Perch charges 10¢ per 1,000 fresh rule checks, with no developer seat fees. Cached unchanged checks are free. About 50¢ per mid-sized PR is a rounded estimate for approximately 150 methods read at the captured September–October 2026 density of 34 questions per method; the unrounded example is 51¢. A single named-rule check is a different scope. Team workload calculations show the assumptions.
The Perch CLI is MIT licensed; hosted analysis is paid and relevant source is sent to the configured model service. Fresh model judgments can vary. Unchanged requests can reuse cached results.
Test the same requirement before choosing
Use one authorized public change with a known regression and a clean control. Pin the base and reviewed code, and keep the documented requirement available to both tools.
Record each tool’s configuration, reviewed files, review effort, findings and false positives. Record cost and elapsed time from the actual run.
Repair the regression and repeat the relevant review. For Perch, preserve existing configuration, run the saved rule after the edit, and repeat the same check after repairing a finding.
This article compares documented product workflows and terms. The public evaluation materials include captured Perch requirement checks; authenticated CodeRabbit and Greptile runs remain unscored. They do not establish a measured accuracy ranking between these tools.
Sources and related comparisons
Reviewed October 14, 2026. Unverified features are marked as unverified rather than treated as absent. Current terms and actual trial results should determine a purchase.