Re:View fields named specialists — Grace on correctness, Bruce on security, Maya on docs, and eleven more. Flash checks every commit in minutes; the deep reviewers go to work on request.
Free for private repos to start · full cast on open source · no card required
The amount comes straight from the request body with no authorization check — any authenticated caller can refund arbitrary amounts. Gate this on the refunds:write scope and bound amount server-side.
The Stripe secret is echoed into the error log. Rotate it, assume it is compromised, and log the request ID instead.
assumes the diff is hostile until proven safe — Bruce · re-view.ai
The cast
Every persona is a focused reviewer with its own specialty — a distinct failure mode it alone catches. Enable the cast your codebase needs, or summon anyone on a PR by commenting @re-view <name> (or an alias like @re-view security). @re-view all calls the full cast.
Core cast — every paid plan
General review
Reads everything, judges like a senior generalist. Correctness, behavior risk, contract hygiene.
@re-viewgracegeneral
Security
Injection, authz gaps, leaked secrets, weak crypto. Assumes the diff is hostile until proven safe.
@re-viewbrucesecurity
Architecture
Coupling, boundaries, placement, API surface. How it is built outlasts what it does.
@re-viewfrankarchitecture
Documentation
Doc drift, missing reference for new public surface, stale examples. An undocumented change is half a change.
@re-viewmayadocs
Tests
Untested paths, weak assertions, flaky patterns. If it is not tested, it is broken.
@re-viewkenttests
Fast pass
A blocking-issues-only scan of every commit. First feedback before the coffee cools.
@re-viewflashfast
Specialists — Studio plan
Concurrency & distributed
Races, deadlocks, idempotency, partial failure. Time and ordering are her home turf.
@re-viewleslieconcurrencydistributed
Performance
N+1s, accidental quadratic, allocation churn. Finds the hot path before the pager does.
@re-viewbrendanperf
UI/UX & design systems
Design-token drift, missing states, interaction hygiene. The details are the product.
@re-viewjonyuiux
Accessibility
WCAG 2.2 essentials: semantics, keyboard paths, screen-reader experience, contrast.
@re-viewjudya11y
Data & schema
Migrations, constraints, indexes, query shape. Relationships done right.
@re-viewedgardataschema
i18n & localization
Hardcoded strings, broken plurals, RTL, encoding. Every user, their language.
@re-viewcleoi18nl10n
Reliability & observability
Swallowed errors, missing timeouts, log hygiene. You cannot operate what you cannot see.
@re-viewbetsyreliability
Licensing & privacy
Incompatible licenses, PII flows, data sinks. What you may copy, what you must protect.
@re-viewlarrylicenseprivacy
How it works
01
One click from the GitHub marketplace. Pick the repos. No CI config, no workflow files, nothing to maintain.
02
A small YAML in the repo default branch — or the dashboard. Trigger mode, personas, path filters, review language.
03
Flash checks each commit; deep reviewers run on request or mention — @re-view security brings in Bruce on demand.
Built for trust
Re:View reads your code and posts findings. No branches, no commits, no merges.
Every review runs in an isolated, egress-locked container. Your code cannot phone home.
Review on request or Flash on every commit — your choice, not an upsell.
Flat per-seat pricing with unlimited reviews under fair use. No per-file meters, no overage, no surprises.
@re-view review, @re-view security, @re-view fast — summon exactly the review you need, in the PR.
One setting, and the cast writes findings in your team's language.
Pricing
Pay per seat. Paid plans review every pull request your team opens, under fair use. Free covers 25 reviews a month.
$0
$19/user/mo
$39/user/mo
Custom
Annual billing saves ~20%. Open-source repositories get the full cast free under fair-use caps — because public code deserves public-interest review. Paid plans have no overage charges. Prices exclude tax. Every new paid subscription comes with a 30-day money-back guarantee.
FAQ
No. Re:View can read repository contents, and it has read and write access to pull requests and issues so it can post reviews and comments, and it publishes a Re:View approval check that your branch rules can require. It creates no branches, makes no commits, and merges nothing. On small documentation-only pull requests it may post an approving review instead of running the full cast; your branch protection rules decide whether that approval counts. Reviews run in single-use sandboxed containers with network access limited to GitHub's API and our AI model providers.
Reviews are written by Anthropic Claude models, served by Anthropic and reached through OpenRouter. A small Google model first picks which specialists a pull request needs, from the list of changed file paths only. You pay per seat, never per token, and we do not use your code to train models. See Security for what is sent and kept.
Core and Studio have no review quota and no overage charges: every pull request your team opens gets reviewed. Fair use covers normal team development. If automated traffic pushes an account far beyond typical volume, we'll contact you to talk it through. We won't cut reviews off or bill per review. Free includes 25 reviews a month, and open-source repositories run the full cast under a separate fair-use budget.
Your choice, for the whole organization in the dashboard or per repository in .re-view.yml: opened reviews each new pull request, every_push reviews again on every commit, and requested waits until someone adds Re:View as a reviewer or comments @re-view. Requests always work, whatever the setting.
Set the personas list in .re-view.yml on the default branch, or toggle it in the dashboard. Config can only narrow — a pull request can never mute its own review or unlock a persona above the plan.
No. We don't use your code to train models, and we only send it to Anthropic's own API, through OpenRouter, under terms that prohibit training on it. Providers may keep requests briefly for abuse and safety monitoring under their API terms. We don't keep copies of your code after the review.
Yes, within 30 days. If a new Core or Studio subscription isn't working for you, email contact@re-view.ai within 30 days of its first payment, monthly or annual, and we'll refund that payment in full. After that you can cancel any time and keep access until the end of the period you've paid for; other payments aren't refunded except where the law requires. Payments are processed by Stripe through Link, which calculates any sales tax or VAT at checkout. Details are in our Terms.
Enterprise plans can run review workers inside your own VPC. Talk to us about data-residency and compliance requirements.