Frequently asked questions
Common questions about Revvu — answered.
Before you ask
These are the questions teams ask most often before installing or while getting started. If yours isn't here, the support form at /support reaches a real person — usually a same-day reply. We'd rather expand this page than have you stay stuck.
Which programming languages does Revvu support?
Any language GitHub PRs are written in. The reviewer reads diffs, not language-specific ASTs, so it works with TypeScript, Python, Go, Rust, Ruby, Java, Kotlin, C, C++, Swift, PHP, and anything else. Quality is highest on languages the model has seen most often — mainstream web and backend stacks. Niche languages still get reviews, but findings may be slightly less specific.
Does Revvu work on private repos?
Yes. The GitHub App installs on any repo you have admin access to, public or private. Permissions and review behavior are identical.
How long do reviews take?
The fast PR summary lands in roughly ten seconds. The deep review with inline comments lands in 30 to 90 seconds for medium PRs (10 to 30 files). Very large PRs may take a few minutes.
What happens on huge PRs?
Files are grouped (1 to 5 per group) and reviewed in parallel, capped at a few groups concurrently to stay within provider rate limits. A 50-file PR completes in roughly the same wall-clock time as a 10-file PR, because the slow part is per-group inference, not the total file count.
Will the bot review every push?
By default, yes — every push to an open PR triggers a fresh review, with reconciliation against previous reviews so you do not see duplicate comments. You can scope this via the triggerEvents setting (for example, only on PR open, never on subsequent pushes), or use a branch allowlist to limit which branches get reviewed.
Will the bot review draft PRs?
Yes by default. If you only want reviews on PRs that are ready for review, enable the skipDraftPrs setting in repo settings.
Will the bot review bot-authored PRs?
Yes by default — Dependabot, Renovate, and other automation PRs all get reviewed. If you trust those updates and want to save review budget, enable the skipBotPrs setting.
How do I disable Revvu on a single repo?
Toggle "Auto-review" off on the repo's settings page in the Revvu dashboard. The GitHub App stays installed, but no reviews fire for that repo. You can re-enable at any time without reinstalling.
How do I uninstall Revvu entirely?
From github.com/settings/installations, find Revvu, and click Uninstall. We delete your repo metadata, settings, and learnings on uninstall — there is nothing left behind in our database.
Does Revvu replace human reviewers?
No. Revvu takes the first pass so your team focuses on architecture, product decisions, and trade-offs that need human judgment. It catches the obvious stuff so the human review can be about the non-obvious stuff.
Can I see what the bot has learned about my repo?
Yes. The Learnings tab on each repo's dashboard page lists every captured rule alongside the conversation that produced it. You can delete individual rules or clear them all.
How do I report a bad review?
Reply to the bot comment on GitHub explaining what was wrong. The bot stores corrections as learnings and adjusts on future reviews. For a broader issue (bot is unresponsive, posting duplicates, missing PRs entirely), use the support form at /support.
What's the pricing?
Revvu is in beta. Contact us via /support for current pricing and to discuss your team's volume.
Where is Revvu hosted?
Revvu runs on Vercel (US-based). Webhooks are processed by Vercel and queued through Inngest. AI inference runs at the model provider's endpoint.
Do you train on my code?
No. Diffs are sent to the AI provider for inference only and are not retained or used for training, per the provider's terms. We do not store raw diffs ourselves either — review records hold metadata and the comment text we posted, not the source.