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. No config file, no API keys, no per-repo setup.
Sign 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.
Install 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.
Open 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 summaries at four levels, and posts a comment with a link into the review IDE.
The whole pipeline usually finishes in under a minute. Larger PRs take longer; you'll see a status while the review is being built.
Read the review on the canvas
Click the link in the PR comment and the review opens at app.acuvis.dev. The cluster canvas shows the architecture first: groups of files that move together, edges between them, one sentence per cluster.
The same change is also available as an outliner tree and a file-by-file deep dive. Comments and resolutions sync across all three views. Drill into a hunk; come back to the canvas; pick up where you left off.
Three views of the same change.
Every review opens on the canvas by default. Switch with the view tabs in the top-right, or with the keyboard shortcuts shown next to each. Concerns stay colour-coded across all three — see the five categories.
Canvas
Clusters as nodes, with blast radius, risk score, and concern badges on each. Start here when the PR is large or the codebase is unfamiliar.
Outliner
Hierarchical tree of clusters, files, and definitions with a code preview on the right. The closest thing to how GitHub shows a PR, with the architecture wrapped around it.
Files
File-by-file deep dive: side-by-side diff in the middle, file tree on the left, per-hunk AI commentary on the right. Where you go once the canvas tells you which files matter.
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 or member.
Acuvis is priced per review, not per seat. Add as many reviewers as you want — the bill doesn't change.
Public share link
On any review, generate a read-only token. Anyone with the URL opens the canvas and outliner 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.
Six things that catch new users off-guard.
Stop scrolling diffs. Start reading what changed.
Sign in with GitHub, install on a repo, open a PR. About a minute, no card, no waiting list. Open-source projects stay free forever.