Understanding is the start.
Hyrax ships verified upgrades.
Greptile indexes the full repository and reviews pull requests with that context, which is a real advantage over diff-only reviewers. Hyrax takes the same starting point further: it keeps the map in the repository and turns issues into verified pull requests.
- Hyrax audits roughly 400 of its own repositories.
- Free plan: full access, up to 100 PR reviews a month, a $30 starter credit, and $10/month ongoing.
Verified end to end, with no Greptile handoff
What changes when Hyrax runs above the tools.
The codebase, not the diff
Greptile sees the change in front of it. Hyrax audits the whole repository, so problems that no single pull request touches still surface.
Verified before it arrives
Every change runs the project baseline tests, build and lint, and passes a second reviewer agent, before the pull request exists.
Context that compounds
The map of the codebase lives in the repository and strengthens with every merge, so the next decision starts from everything learned before it.
How Hyrax and Greptile make decisions.
| Decision criteria | Greptile | Hyrax |
|---|---|---|
| Unit of work | The pull request, reviewed with full repository context. | The whole repository, audited continuously across six domains. |
| Codebase context | Indexes the repository into a graph, refreshed as the code changes. | A durable map committed to the repository as HYRAX.md and .hyrax/discovery, so it strengthens as the codebase changes. |
| Output type | Review comments and severity-labelled issues on the diff. | Verified pull requests, plus issues ranked by severity and effort. |
| Verification | Comments are advisory. The team writes and tests the change. | Baseline tests, build, lint and a second reviewer agent run against the project itself before a pull request opens. |
| Human control | The team makes every change. | A human approves and merges every pull request. Hyrax never merges on its own. |
| Delivery surface | GitHub, GitLab and Bitbucket pull requests. | GitHub pull requests, with issues and posture in the Hyrax console. |
| Pricing model | Per seat, commonly around $30 per developer per month. | Free plan with a $30 starter credit and $10/month ongoing. Paid is $30 per user per month and each paid user gets $30/month of credits. |
Read how Greptile describes itself: www.greptile.com(opens in a new tab)
Comments on a diff, or a verified pull request.
- 01A pull request opens and Greptile reads the diff.
- 02Greptile returns comments, summaries and suggested changes.
- 03The team interprets the feedback, makes the edits, and merges.
- 01Maps the codebase and keeps the map in the repository
- 02Applies architectural judgment across six domains
- 03Opens a verified pull request that a human merges
GitHub-native. Human-controlled. Verified before merge. No training on customer code.
From install to the first verified pull request.
Install the GitHub App
Grant read access to the repositories in scope. No card is required to start.
Hyrax maps the repository
Discovery writes HYRAX.md and .hyrax/discovery into the repository, so humans and AI tools read the same context.
Review the first pull request
Approved upgrades arrive as verified pull requests. A human merges every one.
Both tools solve real problems.
Choose Greptile if
The goal is better review comments with real repository awareness, and the team is happy to do the resolving. Greptile is one of the strongest options for that.
Choose Hyrax if
Codebase understanding should produce work, not just commentary. Hyrax commits the map to the repository, audits beyond open pull requests, and returns changes that already passed the project tests.
Per seat, with usage limits by plan.
Free plan with a $30 starter credit and $10/month ongoing. Paid is $30 per user per month, and each paid user gets $30/month of credits.
Questions about Greptile and Hyrax.
Does Hyrax work alongside Greptile?
Yes, and most teams run both. Greptile keeps doing its job. Hyrax works at the level of the whole codebase, decides what is worth changing, and delivers verified pull requests. Nothing about the Greptile setup has to change.
Greptile already has codebase-wide context. What does Hyrax add?
Context is where Hyrax starts rather than where it stops. The map is committed to the repository as HYRAX.md and .hyrax/discovery, so it persists and strengthens with every merge instead of being rebuilt per review. Hyrax then acts on it: issues across six domains, and resolves verified against the project baseline tests, build and lint before a pull request opens.
What does Hyrax change in the repository?
Discovery writes HYRAX.md and a .hyrax/discovery directory, which document the architecture, conventions and risk areas of the codebase. Everything else arrives as a normal pull request on its own branch. Hyrax has no write access to the default branch.
How does pricing work?
The free plan includes full access, a $30 starter credit and $10/month of credits ongoing, with no card required. The paid plan is $30 per user per month, and each paid user gets $30/month of credits. Pull request reviews are included on every plan.
What happens after signup?
Installing the GitHub App and granting access to a repository takes a few minutes. Hyrax maps the codebase, then runs the first audit and returns issues ranked by severity and effort. The first verified pull requests follow once an audit is approved.