Early-access packaging

Start with your code. Expand to every repository.

Four plan bundles provide a path from personal review to shared repository workflows. Exact prices and allowances will be published only after approval and implementation.

  • Two review products
  • No invented usage promises
  • Only verified availability claims

Choose an Enjoyable plan

Early access

For trying focused review

Hobby

Experience Personal Review and a bounded path to repository automation.

Early access Early-access packaging

What's included

  • Hard-capped Personal Review
  • Small Repository Review allowance when available
  • Bounded personal repository connections when verified

Free-package limits and abuse boundaries remain under validation.

Popular

For developers working across projects

Individual

Carry review across your work and optionally connect personal repositories.

Early access Early-access packaging

What's included

  • Expanded portable Personal Review
  • Public and private repository connections when verified
  • Separately attributable Repository Review capacity

Price, included cases, and repository limits remain under validation.

Early access

For shared engineering workflows

Teams

Apply one review workflow across contributors and connected repositories.

Early access Early-access packaging

What's included

  • Organization-sponsored local preflight
  • Pooled Repository Review capacity
  • Shared configuration, administration, and collaboration

Covered-contributor, pool, and price mechanics remain under validation.

Planned

For higher-trust engineering

Enterprise

Extend Teams with verified governance, identity, and service boundaries.

Planned Planned package

Planned package

  • Repository and model controls
  • Identity, access, policy, and evidence capabilities
  • Contracted integrations and support

Enterprise remains planned and sales-assisted until every release gate is verified.

Discuss Enterprise

These packages describe selected early-access direction. They do not activate checkout or promise an unpublished price, allowance, repository limit, or launch date.

Product-specific capacity

Personal work and repository automation stay understandable.

A plan may include both products, but each keeps a clear usage owner so customers can understand where review work belongs.

One-person workspace

Personal Review

Personal Review follows the individual across authorized projects. Local project count is not the usage unit, and a GitHub connection is not required.

Repository workspace

Repository Review

Repository Review belongs to the workspace that owns the authorized connection. Teams and Enterprise share that capacity across connected repositories.

Planned usage model

One logical change, not every model call.

The proposed change-review case includes an initial review and bounded fix-and-re-review work for the same logical change. Exact boundaries remain under validation.

Change-based

Meter the review workflow instead of tokens, comments, or files.

Retry-safe

Validation, authorization, provider, and internal failures do not become completed cases.

Customer-controlled

Show remaining capacity or require clear consent before paid continuation.

Early-access packaging

Packaging questions, answered

What the selected plans mean now and which commercial terms remain open.

Plans may include both products, but their capacity remains separately attributable. Personal Review belongs to a one-person workspace; Repository Review belongs to the workspace that owns the connected repository.