Stetrel

AI code review

Review the change against the whole book.

Stetrel indexes your repository, then comments on pull requests with that context. It knows the caller three files away. It also knows the proofreader’s mark stet: leave this line.

01

What you get on every PR

Cited patterns

Comments name the existing helper, the caller, and the file that already solved the same job.

Breakage flags

Auth changes, deletions, and cross-module contracts are scored before a human opens the tab.

House voice

Optional learning from how your team actually reviews. Dismissals can train the next pass if you opt in.

02

The index is the product

Embeddings and a graph of how this codebase fits together, refreshed as you merge. The reviewer retrieves. The diff is the question. The tree is the answer.

03

Deploy how legal requires

SaaS. VPC. Air-gapped. Same review quality. Source can stay in your building.

SaaS

GitHub or GitLab app. Private index per org. Comments land in the pull request you already use.

VPC

The same binary in your cloud. Indexes, models, and logs stay inside the perimeter you name.

Air-gapped

No outbound calls after install. You bring the weights. We bring the reviewer and the graph.

From desks that still read the diff

“It catches the bug in the helper nobody opened.”
Example quote, staff engineer
“We kept human review. Rubber stamps got rarer.”
Example quote, engineering manager

Put a reader on every pull request.

Fourteen-day trial on Desk and Floor. VPC walkthroughs start with Rahul.

Install on GitHub