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, pooled credits, cheap linear overage. No per-file meters, 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
Credits pool across your team and refresh monthly. A full-cast review costs 10 credits; a Flash commit check costs 1.
$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. Overage is $0.10/credit: a 40-file PR over quota costs one dollar, not ten.
FAQ
Not today. Re:View holds only read access to repository contents and pull-request read/write for posting reviews — it creates no branches, makes no commits, and merges nothing. Reviews run in single-use sandboxed containers with network egress limited to GitHub and our inference backend.
We operate our own multi-tenant inference backend and route each review to the capacity that serves it best. The specific model and account behind a review is part of our infrastructure, not part of your bill — you pay per seat and credits, never per token anxiety.
Your choice per repo: on_request — when a reviewer requests Re:View or someone comments @re-view review — or on_commit, where Flash reviews every push and the deep cast runs on request. Both modes are on every plan.
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. Repository contents are used only to produce the review for that pull request and are not used to train models.
Enterprise plans can run review workers inside your own VPC. Talk to us about data-residency and compliance requirements.