Hyrax helps engineering teams understand what's happening across their codebase, identify what matters, and turn improvements into production-ready changes. It maps your codebase and understands how your product is built, then six specialized agents evaluate security, correctness, maintainability, performance, architecture and operations. The highest-leverage work becomes verified pull requests in GitHub. An engineer reviews and merges every one.

How does pricing work?

Free gives every workspace full access to Hyrax, a $30 starter credit, $10/month ongoing credit, and up to 100 PR reviews a month for free, with no card required. Paid is $30 per user per month, and each paid user gets $30/month of credits. Credits meter usage across repository mapping, verified improvements, and PR reviews; there are no feature walls. Overage is opt-in with budget caps.

When do I need a paid seat?

When a developer wants deeper access: opening full summaries in Hyrax, asking Hyrax to fix an issue, or running more workflows than the free credits cover. Each paid user gets $30/month of credits, and paid workspaces can opt in to overage with a budget cap they set.

What is the 13-step verification?

The 13-step verification gate checks an improvement before it reaches your team as a pull request. It covers isolated worktree execution, the tests it started with, the tests after the change, your build, lint and formatting, a size limit on the diff, a second review by an independent agent, a re-scan to confirm the original issue is gone, and CI. If a required check fails, the work stops and never becomes a PR.

How is Hyrax different from AI coding assistants?

AI tools write code. Hyrax architects the system that code enters. Assistants edit what you point them at, and their context starts empty every session. Hyrax holds the map of your codebase, and six specialized agents reason about security, correctness, maintainability, performance, architecture and operations before anything ships. Use both.

Scan reads the whole codebase first, so it understands your architecture and conventions, then looks for problems the way a reviewer would. It produces a ranked list of findings and easy wins, each with a plan for the fix.

Every change ships as a pull request with the [Hyrax] prefix. PR Review reviews every opened pull request automatically against the codebase conventions, leaving comments that update as the code changes. It can block merge on must-fix findings. You get up to 100 PR reviews a month for free.

What languages are supported?

Hyrax works across 19 languages: Python, TypeScript, JavaScript, Go, Rust, Swift, Ruby, Java, Kotlin, C#, C++, C, PHP, Scala, Dart, Elixir, Shell, Lua, and MDX. It works with the frameworks built on them: React, Next.js, Vue, Svelte, Angular, Node.js, Django, Rails, Spring, FastAPI, Express, React Native, and Flutter.

What integrations are supported?

GitHub for source control. Linear for ticket management. Tickets are created on audit and closed automatically when fixes merge.

Hyrax works through GitHub with human control, and it never merges on its own. Verification runs before a pull request reaches your team, and your engineers make the final call. All inference runs in the Hyrax AWS Bedrock account, and Hyrax does not train on customer code.

New: Hyrax MCP gives Claude Code, Cursor, and Copilot live codebase context.Read the announcement

Product

How it works

Pricing

Resources

Knowledge Base Learn Blog Agent rules Compare FAQ

← Blog

software architecturesystem designdistributed systems

Architecture & Systems

Design decisions, tradeoffs, and the architectural patterns that age well. Long-form technical writing for the engineer who keeps a copy of Fowler nearby.

Architecture & SystemsAugust 12, 20265 min read
Go Is Good for AI Review. What About Everything Else?
Google's case for Go as the ideal AI-assisted language implies that TypeScript, Python, and Rust teams carry more review debt. Here is what that actually means.
Architecture & SystemsJune 5, 202611 min read
How Hyrax reviews code
The technical thesis behind Hyrax: six agent groups in parallel, isolated worktrees per fix, 13 verification steps, and a deliberate choice to submit pull requests rather than auto-merging.
Architecture & SystemsMay 30, 20269 min read
Monorepo vs polyrepo in 2026: the tradeoffs nobody admits
Both have real costs. Monorepo fans undercount the tooling investment. Polyrepo fans undercount the coordination cost. A clear-eyed comparison with data from teams that have run both.
Architecture & SystemsMay 28, 20269 min read
The verification gate: how Hyrax decides a fix is safe to ship
Independent verification is not a linter. A walk through the 13-step gate that stands between a candidate change and a pull request.
Architecture & SystemsMay 20, 20268 min read
Inside the audit: six agent groups and a deterministic scanner
How Hyrax reads every file in a repository — combining six specialized agent groups with a deterministic scanner so nothing depends on a single model's mood.
Architecture & SystemsMay 12, 20267 min read
What discovery writes to the repo: HYRAX.md and the .hyrax bundle
Before remediation, Hyrax learns the codebase and commits what it learned — a HYRAX.md and a .hyrax context bundle any IDE assistant can read.

Architecture & Systems

Go Is Good for AI Review. What About Everything Else?

How Hyrax reviews code

Monorepo vs polyrepo in 2026: the tradeoffs nobody admits

The verification gate: how Hyrax decides a fix is safe to ship

Inside the audit: six agent groups and a deterministic scanner

What discovery writes to the repo: HYRAX.md and the .hyrax bundle