Greptile uses active-author credits and review effort levels. Cubic Team uses developer subscriptions with reviewed-line allowances and custom agents. Cubic also documents uncommitted local review, while Greptile CLI requires committed branch changes.
| Decision | Greptile | Cubic |
|---|---|---|
| Review scope | Repository-aware PR and branch review; Base, Plus and Apex use 1, 3 and 10 credits. | PR and local review with plan-specific reviewed-line allowances. |
| Local review input | CLI reviews committed branch changes; its documented workflow ignores uncommitted changes. | cubic review checks uncommitted edits or changes against a base branch. |
| Custom requirements | Repository instructions and cascading directory-specific standards. | cubic.yaml custom agents; Team includes 5 agents. |
| License and service | Commercial review service. | Commercial review service. |
| Official references | Greptile sources | Cubic sources |
Compare a high-volume author with a large-diff author. Record effort credits, reviewed lines and repeated repair passes separately. Keep the base branch and exclusions fixed.
Pro: $30/seat/month with 50 credits/seat; extra credits $1 each. Starter is free for one active developer.
Pro subscription floor before extra credits. Base, Plus and Apex reviews consume 1, 3 and 10 credits respectively. The free Starter tier covers PR reviews; CLI reviews need an active trial or paid plan. Included credits and flex overages are per active author, not pooled across the team.
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
Perch is a stronger fit when the same project requirement must be checked after each local repair. Select that requirement directly and reuse unchanged cached answers without a seat 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.
npm install -g @lakeday/perch
perch login
perch setup claude-code
# Or choose: perch setup codex
# Or choose: perch setup cursorUse 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 --jsonKeep 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.
Download the tenant-authorization rule pack · Inspect pack contents and agent task
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.
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.
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.