Skip to content

Pricing

Choose the plan that fits your team.

Plans are based on team size and monthly review volume.

Startup

Up to 15 engineers

AI code review for smaller teams.

$750/ month

Includes

  • Self-healing code review
  • 300 reviews / month ($1 per review after)

Scale

16–50 engineers

More review capacity as the team grows.

$2,500/ month

Includes

  • Self-healing code review
  • 1,000 reviews / month ($1 per review after)

Enterprise

Custom

For larger teams and advanced requirements.

Custompricing

Includes

  • Self-healing code review
  • Agent Insights
  • Model Router
  • Knowledge Base
  • Self-hosting

Before you buy

Security, compliance and deployment, in writing.

Everything below is available for review before a contract, and confirmed in the order form.

COMPLIANCE

SOC 2 Type II

Request the current report, scope, and bridge letter.

soc 2 type ii
  • current reporton request
  • scopeon request
  • bridge letteron request

ACCESS

Workspace controls

Review roles, repository access, and connected destinations.

workspace
  • rolesper member
  • repository accessper repo
  • destinationsallow-listed

DEPLOYMENT

Confirm your data boundary

Review architecture, storage, and deployment commitments for your setup.

your network
  • architecture
  • storage
  • deployment

confirm the data boundary before rollout

ANALYTICS

Use metrics with context

Signals are diagnostic, not a score for individuals.

read as
  • signalsdiagnostic
  • individualsnot a score

What teams usually want to know before a pilot.

If yours isn’t here, ask a founder. We read everything.

  • Commercial terms can vary by plan, billed seats, usage, product access, and deployment. The values in your current workspace and signed order form are the source of truth.

  • Yes. Start with one measurable workflow, a small set of repositories or users, and a baseline you can compare against. Expand after you verify the result and operational fit.

  • Depending on your workspace, Billing can include subscription state, billed seats, LLM usage and overage, invoices, and Model Router credits or balance where routing is enabled.

  • No. Product access and rollout can vary by plan, connectors, deployment, role, repository, and rollout state. Start with the workflow you need now.

  • Agent Insights is included in Enterprise. It is not included in Startup or Scale.

  • Choose the problem with the clearest baseline: review quality, AI spend, delivery friction, or recurring production risk. A good pilot should give you something concrete to compare before and after.

  • Yes. Review the product's visible controls, then request the current security and contractual documents for deployment boundaries, retention, model-provider terms, compliance scope, and other commitments.

  • Agent Insights is designed for workflow and cost diagnosis, not standalone employee scoring. Its metrics should be interpreted with repository, task, coverage, and team context, not used alone as individual performance measures.

  • We will review the workflow you are trying to improve, the systems it depends on, any security or deployment requirements, and the smallest pilot that can give your team a useful answer.

Start with one workflow. Expand when it proves value.

Pick one measurable workflow, run a small pilot, and compare against your own baseline.

  • No credit card required
  • SOC 2 Type II
  • Deploy in your cloud, your own keys