Everything we've been asked more than twice.

Sign in at app.acuvis.dev with GitHub, then open Admin → Integrations and click Install on GitHub. Pick the account or organisation, grant access to all repositories or specific ones, and you're done. The next pull request that leaves draft is reviewed automatically.

Not to start. Your first five pull requests are reviewed free with no card. To keep going, add a card for a 14-day trial (up to 50 pull requests); you aren't charged until it ends and can cancel before then.

Yes. The GitHub App can be installed on any number of accounts and orgs, and a single Acuvis organisation can hold multiple installations. Useful when your code is split across a personal account and a company org.

Nothing, until a pull request opens. The moment a PR moves out of draft (or opens directly as ready for review), Acuvis reads the diff in its own microVM, groups the change into clusters, writes the walkthrough and findings, and posts a summary comment and an “Acuvis review” check on the PR. Most reviews finish within a couple of minutes.

No. Team rules, path-specific instructions and ignore paths live in the dashboard under Review policy. If your repository has AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, CONTRIBUTING.md or .acuvis.yml, Acuvis reads them too.

Per active developer: anyone whose pull request Acuvis reviewed that month, counted once however many pull requests they open. Pushing more commits to a pull request re-reviews it for free. Reviewers, viewers and bots never count.

Yes, on application. Approved public repositories get 200 free pull request reviews a month. Apply from Admin → Billing after you install.

They get a seat automatically, charged pro rata on your next invoice, and your admins get an email. To cap it, set a seat limit in Admin → Billing; pull requests from developers past the limit wait until you raise it.

Every pull request needs reviewing, and reviewing is where Acuvis helps, so the people reading should never be the reason a bill goes up. You pay for the developers whose pull requests get reviewed; add every engineer as a reviewer without thinking about it.

Team: $17 per developer a month billed annually, or $21 monthly. Business ($34 / $42) adds a 3-year audit log and priority support, for teams that have to show how changes were reviewed.

No. Inference goes through Fireworks AI and OpenAI under data processing terms, and neither trains on your code. Fireworks doesn't log or store prompts or outputs for the open-weight models we use. OpenAI may keep API inputs and outputs for up to 30 days for abuse monitoring, then deletes them. The full list of providers is on the sub-processors page.

Application data lives in the EU: the database in France, the analysis sandboxes in Frankfurt. The diff hunks are stored in the review document so the IDE can render them back to you, scoped to your organisation, and in database backups kept for up to 30 days. AI inference runs in the United States (Fireworks AI and OpenAI).

Each pull request runs in its own Firecracker microVM on Fly Machines — the same hardware-virtualisation technology that backs AWS Lambda. Each VM has its own kernel and memory, and the VM is destroyed when the analysis finishes. No shared state between reviews.

Yes. Per-organisation data isolation, standard DPA available on request, right to erasure honoured. The full security posture is on the security page.

Yes. We can delete a single review's data, or an entire organisation, on request. Mail privacy@acuvis.dev and we'll take care of it within 30 days.

Yes. Comments, resolutions, review verdicts, membership and billing changes, and review events chain into a per-organisation SHA-256 log. Append-only, tamper-evident and exportable; kept for 1 year on Team and 3 years on Business.

Any language GitHub knows how to render in a diff. The cluster summaries and concern tags work across languages because the underlying frontier model does. There's no language-specific opt-in.

Yes, for notifications. An admin can connect a Slack incoming webhook under Admin → Integrations, and Acuvis posts there when a review is ready, either for every review or only for high-risk and blocking ones. The GitHub PR comment and check update on every run as well.

Not yet. GitHub is the only code host today. GitLab and Bitbucket integrations are scaffolded in the product but not live; we'll announce them on the changelog when they ship.

Yes. Write team rules and path-specific instructions under Review policy, ignore paths you don't want reviewed, and mark findings Useful or Not useful: Acuvis learns rules from that feedback. The six concern types themselves are fixed.

Yes — book a 20-minute demo. We'll screenshare on one of your real open PRs and you'll see exactly how it'd land for your team.

Yes. From Admin → Billing, the Stripe customer portal lets you change or cancel your plan at any time. No annual lock-in, no cancellation phone call.

The Stripe customer portal (linked from Admin → Billing) hosts every invoice for download. In-app invoice viewing will land in a future update.

Mail hello@acuvis.dev with the details. A human will read it within a few hours during European working hours and we'll make it right.