acuvis
Sign in

Get started

From PR to plain English. About a minute.

Sign in with GitHub, install the app on the repos you want, open a pull request. The review is waiting when you click through. Nothing to configure first, no API keys.

Start free5 pull requests free. No card.

01Sign in with GitHub

Open app.acuvis.dev and click Continue with GitHub. The OAuth flow asks for your email and public profile. Nothing else.

You'll land on your empty dashboard. The next step is to install the GitHub App on the repositories you want reviewed.

Acuvis sign-in screen with Continue with GitHub button.

02Install the GitHub App

From the sidebar, open Admin → Integrations and click Install on GitHub. GitHub takes over: pick the account or organisation, then either grant access to all repositories or pick specific ones.

For an org, All repositories is the easiest path. Acuvis never touches a repo until a pull request opens on it. Selective access is fine if your org policy requires it.

Permissions in plain English: read code and metadata; read and write checks and pull requests, which is how the summary comment, the merge check and your submitted reviews get posted. No push, no merge, no settings access.
GitHub Install Acuvis screen showing the choice between all repositories and selected repositories.

03Open a pull request

Push a branch and open a PR the way you normally would. The webhook fires the moment the PR moves out of draft. Acuvis reads the diff in a fresh Firecracker microVM, groups the files into clusters, writes the walkthrough and findings, and posts a summary comment and an Acuvis review check with a link into the review.

Most reviews are ready in a few minutes. Larger pull requests take longer; the review page shows progress while it builds.

Draft PRs don't count. Acuvis ignores drafts until you mark them ready for review. That keeps reviews for the changes you actually want a second pair of eyes on.
Acuvis bot comment on a GitHub pull request with a link into the review IDE.

04Read the review in Acuvis

Click the link in the PR comment and the review opens at app.acuvis.dev as a walkthrough: what the change does, then its parts in the order to review them, each with its findings.

The same change is also an architecture map and a Files view built for reviewing. Comments, viewed marks and resolutions carry across all three. Drill into a file, come back to the map, and pick up where you left off.

A review open in Acuvis as a walkthrough: an overview, then numbered sections with their findings.

Reading the review

Three views of the same change.

Every review opens on the walkthrough. Switch views with the tabs at the top, or with Alt 1, Alt 0 and Alt 2. The six concerns keep the same colours in all three.

Walkthrough of a pull request: an overview with file, finding and blocking counts, then numbered sections, each with a summary, a start file and its findings.

Walkthrough

Where every review opens: a short overview, then each part of the change in the order to review it, with its findings and the file to start in. For most pull requests it's the whole review.

Canvas with clusters in lanes for apps/web, apps/api and packages/shared, numbered in review order, with dependency arrows between them.

Canvas

The change as an architecture map: clusters laid out by area of the codebase, with what depends on what and where to start. Select a cluster to see its findings and impact.

Files view with a file rail grouped by cluster on the left and a diff with an expanded blocking finding on the right.

Files

The diff, built for reviewing: files in review order, changed words highlighted, viewed marks, findings on their lines, and comments or suggestions on any range.

Share & teams

Add the whole team. Share a single review with anyone.

Invite teammates

From Admin → Members, add anyone by email. They sign in with GitHub and land in your org. Roles are admin, member or viewer.

You pay per developer who opens pull requests. Reviewers are free, so add everyone who should look.

Public share link

On any review, generate a read-only token. Anyone with the URL opens the review without an Acuvis account. Rotate or revoke the token from the review's share menu at any time.

Good for showing a review to a customer, a contractor, or a colleague who only needs to look once.

Good to know

Six things that catch new users off-guard.

  • Drafts don't count.
    Acuvis only reviews PRs once they leave draft. Convert back to draft to pause; mark ready to trigger a fresh review.
  • Open source is free, on application.
    Approved public repositories get 200 free pull request reviews a month. Apply from Admin → Billing after you install.
  • Re-reviews are free.
    Push as many commits as you like: a pull request counts once a month, and you pay per developer who opens pull requests, not per review.
  • Acuvis never writes to your code.
    It reads code and writes only checks, comments and the reviews you submit. No push, no force-push, no merge.
  • Big PRs take a little longer.
    Most reviews are ready in a few minutes. Diffs over a few thousand lines take longer; the review page shows progress while it builds.
  • You can tune what it flags.
    Write team rules in Admin → Review policy, let Acuvis read AGENTS.md, CLAUDE.md or .acuvis.yml from the repository, and dismiss findings with “don’t flag this again” to turn them into learned rules.

Your next pull request, as a walkthrough.

Sign in with GitHub, install on a repo, open a PR. About a minute, no card, no waiting list. Approved open-source projects review for free.

Start freeRead the FAQOr book a 20-minute demo