Source: https://codereviewguide.fyi/perch-vs-greptile/

Perch vs Greptile · reviewed 2026-10-14

# Greptile alternative for checking uncommitted agent edits

Run perch check on the file the agent just edited, before making a commit. Save the requirement as a named rule and rerun it after the repair. Greptile’s documented CLI reviews committed branch changes and ignores uncommitted work.

## Can you review the repair before committing?

Perch checks files on disk with perch check; the repair can remain uncommitted. Greptile's documented CLI ignores uncommitted changes and reviews the committed branch. Choose Perch for a named requirement the agent must rerun during editing. [Greptile branch-review scope](https://www.greptile.com/docs/code-review/greptile-cli).

`perch check` reads working files; `perch scan` reads Git HEAD. Relevant source is sent to TypeSafe’s hosted models. The MIT CLI does not run model inference offline.

[See the rule catch a regression](https://codereviewguide.fyi/perch-vs-greptile/#check)[Install the Perch CLI](https://github.com/lakeday-org/perch/blob/main/docs/install.md)

## Perch

~50¢

per mid-sized pull request · estimate

- 10¢ per 1,000 fresh rule checks
- Cached checks free
- No seat fees · $5 free usage credit
- MIT CLI · English project rules

**Greptile**Pro: $30/seat/month with 50 credits/seat; extra credits $1 each. Starter is free for one active developer.

Perch estimate: approximately 150 methods read, based on September–October 2026 check density. [Compare billing assumptions](https://codereviewguide.fyi/perch-vs-greptile/#pricing).

**Run it locally**Check uncommitted files

**Keep the rule**Version it with the code

**Read each method**Within the selected parsed scope

**Pay for checks**No per-developer subscription

## Release both adjacent expired reservations.

Read release_expired only. It releases every expired reservation, including adjacent expired entries, removes those entries, and leaves unexpired reservations intact. Perch checked the exact public regression and clean-control commits on 2026-10-14, using the same disclosed requirements prepared for Greptile.

### The regression

```
def release_expired(stock, reservations, now):
    for reservation in reservations:
        if reservation.expires_at < now:
            stock[reservation.sku] = stock.get(reservation.sku, 0) + reservation.quantity
            reservations.remove(reservation)
```

Perch flagged release_expired's requirement at 69% in this captured run.

### The clean control

```
def release_expired(stock, reservations, now):
    for reservation in reservations.copy():
        if reservation.expires_at < now:
            stock[reservation.sku] = stock.get(reservation.sku, 0) + reservation.quantity
            reservations.remove(reservation)
```

The same requirement passed on the public clean-control commit.

Code excerpts from the matched inputs; the helper excerpts preserve the source statements. [Public regression source at 46dd1d0](https://github.com/lakeday-org/perch/blob/46dd1d0d0ea7ceb0e690203d24fca21c428818ec/review-evaluation/order_service.py) · [Full protocol, controls, findings, costs and timing](https://reviewbenchmarks.dev/evaluations/order-service/). The CLI used its configured direct SystemOne endpoint; times and price assumptions are recorded in the report. Fresh judgments can vary.

### Matched evaluation status

Perch flagged 4/4 targeted regressions and flagged 0/4 clean requirements. Greptile: review not run; no comparative detection score is claimed.

## Perch vs Greptile: what your team runs.

Perch turns project behavior into focused checks that agents can run before committing. Use these differences to choose the review workflow and billing model your team needs.

Published Perch capabilities and Greptile documentation, reviewed 2026-10-14

| Capability | Perch | Greptile |
| --- | --- | --- |
| Billing | 10¢ per 1,000 fresh rule checks. Cached checks free. No seat fees. | Pro: $30/seat/month with 50 credits/seat; extra credits $1 each. Starter is free for one active developer.[Vendor documentation ↗](https://www.greptile.com/pricing) |
| Before commit | perch check reads the files on disk, including uncommitted edits. | CLI reviews committed branch changes; its documented workflow ignores uncommitted changes.[Vendor documentation ↗](https://www.greptile.com/docs/code-review/greptile-cli) |
| Custom requirements | English ensure rules in perch.yaml: project, file or method scope. No paid custom-rule tier. | Repository instructions and cascading directory-specific standards.[Vendor documentation ↗](https://www.greptile.com/docs/code-review/greptile-cli) |
| Coverage | Each parsed non-test application method in the selected scan scope is read, with caller and callee context. No method-count cap. | Repository-aware PR and branch review; Base, Plus and Apex use 1, 3 and 10 credits.[Vendor documentation ↗](https://www.greptile.com/docs/code-review/greptile-cli) |
| Open source | MIT-licensed CLI. Hosted model analysis is a paid service. | Commercial review service.[Vendor documentation ↗](https://www.greptile.com/pricing) |

## Greptile alternative for checking uncommitted agent edits

Run perch check while the fix is still uncommitted. Greptile's documented CLI reviews committed branch changes; Perch checks the files on disk. For five Pro seats, Greptile's subscription starts at $150/month before extra credits, against Perch's $50 estimate for 100 mid-sized PRs.

## Review before committing

Greptile: CLI reviews committed branch changes; its documented workflow ignores uncommitted changes. [Greptile workflow documentation](https://www.greptile.com/docs/introduction).

Perch reads the current working file with `perch check`. For a known requirement, select its rule name and method instead of requesting another broad review. A local CLI describes where the command runs; Perch sends relevant source to hosted TypeSafe models for analysis.

## How do saved requirements differ?

Greptile: Repository instructions and cascading directory-specific standards. [Greptile rule documentation](https://www.greptile.com/docs/code-review/custom-standards).

Perch stores English `ensure` rules in `perch.yaml` or `.perch/rules/`. Project, file and method scopes determine what is checked. Run the named check after an edit and after the repair; a rule finding can fail the command and a CI gate. [Perch rules](https://github.com/lakeday-org/perch/blob/main/docs/rules.md) · [Working-file checks](https://github.com/lakeday-org/perch/blob/main/docs/check.md).

## What does the review bill depend on?

[Compare Greptile's billing unit and Perch's usage estimate](https://reviewpricing.fyi/greptile/)

## Is the CLI open source and offline?

Greptile: Commercial review service. [Greptile product or license source](https://www.greptile.com/pricing).

Perch’s CLI is MIT-licensed; hosted model inference is a separate paid service included in its published check rate. It does not run the model offline. Unchanged requests can reuse cached answers for free. Fresh judgments can vary, and a passing requirement check does not prove application correctness. [Perch MIT license](https://github.com/lakeday-org/perch/blob/main/LICENSE).

## When does Greptile fit the workflow?

Greptile provides repository-aware branch and PR review with custom standards. Its free Starter PR tier can fit one active developer; local CLI reviews require a trial or paid plan.

## Estimate the review bill

[Perch and Greptile: pricing, allowances and workload calculator](https://reviewpricing.fyi/greptile/)

## Make the agent check its next edit.

### Install the CLI

```
npm install -g @lakeday/perch
```

[Perch installation and quick start](https://github.com/lakeday-org/perch/blob/main/docs/install.md)

### Download the behavior rules

[Order-service rule pack ZIP](https://reviewbenchmarks.dev/evaluations/order-service/rule-pack.zip)

Extract from the public input checkout. The pack installs four saved requirements under .perch/rules/ and keeps your root configuration.

### Check the working file

```
perch check review-evaluation/order_service.py --rules eval-adjacent-expirations
```

Run the check after an edit and after the fix. [Working-tree check documentation](https://github.com/lakeday-org/perch/blob/main/docs/check.md)

Use [perch scan](https://github.com/lakeday-org/perch/blob/main/docs/scan.md) for repository code at Git HEAD and [changed-code CI checks](https://github.com/lakeday-org/perch/blob/main/docs/ci.md) for pull requests. New model judgments can vary. Repeatability comes from cached answers for unchanged requests; a pass does not prove application correctness.

## Keep your project requirements checkable.

Choose Perch when you want an MIT CLI, English behavior rules and usage pricing that stays independent of team size. Give your coding agent a saved check it can run after every relevant edit.

[Install Perch](https://github.com/lakeday-org/perch/blob/main/docs/install.md)

## Sources and price details

Published by Perch. Vendor facts were reviewed on 2026-10-14; plans and allowances can change. Vendor marks belong to their owners.

- [www.greptile.com/pricing](https://www.greptile.com/pricing)
- [www.greptile.com/docs/introduction](https://www.greptile.com/docs/introduction)
- [www.greptile.com/docs/code-review/greptile-cli](https://www.greptile.com/docs/code-review/greptile-cli)
- [www.greptile.com/docs/code-review/custom-standards](https://www.greptile.com/docs/code-review/custom-standards)
- [www.greptile.com/docs/how-greptile-works/graph-based-codebase-context](https://www.greptile.com/docs/how-greptile-works/graph-based-codebase-context)
- [www.greptile.com/docs/code-review-bot/billing-seats](https://www.greptile.com/docs/code-review-bot/billing-seats)

Perch sources and example arithmetic

- [Public CLI source](https://github.com/lakeday-org/perch) · [MIT license](https://github.com/lakeday-org/perch/blob/main/LICENSE)
- [English rules](https://github.com/lakeday-org/perch/blob/main/docs/rules.md) · [Working-tree checks](https://github.com/lakeday-org/perch/blob/main/docs/check.md) · [Method scope and context](https://github.com/lakeday-org/perch/blob/main/docs/scanning.md)
- [Published Perch rate and estimate assumptions](https://codereviewguide.fyi/perch-vs-greptile/pricing-evidence.json)
- [September 20, 2026 refund-rule capture](https://codereviewguide.fyi/perch-vs-greptile/refund-capture.json)

## Compare Greptile with other review tools

- [CodeRabbit vs Greptile](https://codereviewguide.fyi/coderabbit-vs-greptile/)
- [Greptile vs Qodo](https://codereviewguide.fyi/greptile-vs-qodo/)
- [Greptile vs Macroscope](https://codereviewguide.fyi/greptile-vs-macroscope/)
- [Greptile vs Cursor Bugbot](https://codereviewguide.fyi/greptile-vs-cursor-bugbot/)
- [Greptile vs Kodus](https://codereviewguide.fyi/greptile-vs-kodus/)
- [Greptile vs Cubic](https://codereviewguide.fyi/greptile-vs-cubic/)

[Full head-to-head library and tool selector](https://codereviewguide.fyi/tool-comparisons/)

**Code Review Guide**

Tools & workflows.

Published by Perch · © 2026 Verglas LLC. Code Review Guide is a Perch publication.

Perch’s MIT license covers the CLI; hosted model analysis is a paid service. Relevant source is sent to the configured model service.

[Perch CLI MIT license](https://github.com/lakeday-org/perch/blob/main/LICENSE) · [Article text](https://codereviewguide.fyi/perch-vs-greptile/index.md) · [Resource index](https://codereviewguide.fyi/llms.txt)