Source: https://codereviewguide.fyi/perch-vs-rovo-dev/

Perch vs Rovo Dev · reviewed 2026-10-14

# Rovo Dev comparison for checks independent of the work suite

Perch keeps each behavior requirement in the repository and runs it through a standalone MIT CLI. A coding agent can check the selected rule after editing without tying that check to a work-management seat.

`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-rovo-dev/#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

**Rovo Dev**Standalone Rovo Dev is transitioning into eligible Jira and Teamwork Collection subscriptions.

Perch estimate: approximately 150 methods read, based on September–October 2026 check density. [Compare billing assumptions](https://codereviewguide.fyi/perch-vs-rovo-dev/#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

## Catch the fix an agent removes later.

A saved requirement makes a recurring mistake checkable. In this Perch capture from September 20, 2026, the same rule flags a missing guard and passes after the guard is restored.

### The regression

```
def refund(order, payment):
    payment.refund(order.total)
    order.status = "refunded"
    return order
```

1 check, 1 broken. Refunded orders cannot be refunded again.

### The guarded method

```
def refund(order, payment):
    if order.status == "refunded":
        return order
    payment.refund(order.total)
    order.status = "refunded"
    return order
```

1 check, nothing to report.

Source: [public order-service checkout.py at the linked commit](https://github.com/lakeday-org/perch/blob/4af67af46d76ac99398d61c7ad0a45441760d4dc/test/fixtures/order-service/checkout.py). The captured standalone file is refund.py. [Perch command output and timestamp](https://codereviewguide.fyi/perch-vs-rovo-dev/refund-capture.json). This saved-rule demonstration does not measure Rovo Dev's detection rate.

## Perch vs Rovo Dev: 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 Rovo Dev documentation, reviewed 2026-10-14

| Capability | Perch | Rovo Dev |
| --- | --- | --- |
| Billing | 10¢ per 1,000 fresh rule checks. Cached checks free. No seat fees. | Standalone Rovo Dev is transitioning into eligible Jira and Teamwork Collection subscriptions.[Vendor documentation ↗](https://www.atlassian.com/software/rovo-dev/pricing) |
| Before commit | perch check reads the files on disk, including uncommitted edits. | CLI coding and AI review integrations with Bitbucket and GitHub.[Vendor documentation ↗](https://www.atlassian.com/software/rovo-dev/pricing) |
| Custom requirements | English ensure rules in perch.yaml: project, file or method scope. No paid custom-rule tier. | Review can use Jira acceptance criteria and project context.[Vendor documentation ↗](https://www.atlassian.com/software/rovo-dev/pricing) |
| Coverage | Each parsed non-test application method in the selected scan scope is read, with caller and callee context. No method-count cap. | Coding and review within Atlassian's work-management products.[Vendor documentation ↗](https://www.atlassian.com/software/rovo-dev/pricing) |
| Open source | MIT-licensed CLI. Hosted model analysis is a paid service. | Commercial Atlassian service.[Vendor documentation ↗](https://www.atlassian.com/software/rovo-dev/pricing) |

## Rovo Dev comparison for checks independent of the work suite

Keep project requirements runnable as work-suite packaging changes. Perch stores behavior rules with the code and exposes a direct shell command for the agent to check edits. Its published check rate and MIT CLI remain independent of an Atlassian seat bundle.

## Review before committing

Rovo Dev: CLI coding and AI review integrations with Bitbucket and GitHub. [Rovo Dev workflow documentation](https://www.atlassian.com/software/rovo-dev/pricing).

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?

Rovo Dev: Review can use Jira acceptance criteria and project context. [Rovo Dev rule documentation](https://www.atlassian.com/software/rovo-dev/pricing).

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 Rovo Dev's billing unit and Perch's usage estimate](https://reviewpricing.fyi/rovo-dev/)

## Is the CLI open source and offline?

Rovo Dev: Commercial Atlassian service. [Rovo Dev product or license source](https://www.atlassian.com/software/rovo-dev/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 Rovo Dev fit the workflow?

Rovo Dev connects coding and review to Atlassian workflows. Current bundle availability and credits need to be verified rather than treating a legacy standalone price as a guaranteed quote.

## Estimate the review bill

[Perch and Rovo Dev: pricing, allowances and workload calculator](https://reviewpricing.fyi/rovo-dev/)

## 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)

### Save a behavior rule

```
perch rules add refund-once \
  --where refund.py --each method \
  --ensure "Refunded orders cannot be refunded again."
```

The captured rule checks the requirement shown above. [Rule syntax and selectors](https://github.com/lakeday-org/perch/blob/main/docs/rules.md)

### Check the working file

```
perch check refund.py::refund --rules refund-once
```

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.atlassian.com/software/rovo-dev/pricing](https://www.atlassian.com/software/rovo-dev/pricing)

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-rovo-dev/pricing-evidence.json)
- [September 20, 2026 refund-rule capture](https://codereviewguide.fyi/perch-vs-rovo-dev/refund-capture.json)

## Compare Rovo Dev with other review tools

- [CodeRabbit vs Rovo Dev](https://codereviewguide.fyi/coderabbit-vs-rovo-dev/)

[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-rovo-dev/index.md) · [Resource index](https://codereviewguide.fyi/llms.txt)