Code review, with context
Catch the issue. See why it matters. Inspect the fix. Code Voucher gives your team a clear next step on every merge request.
GitLab todayGitHub planned
A second look. A concrete next step.Follow a one-line change from a missed boundary to a fix you can review.
Try the walkthrough · no sign-in01 / Findings that earn your attention
The diff looks harmless. Follow the evidence to see who can now access the wrong invoice, then inspect a focused fix.
Removing the organization filter lets this lookup return another tenant’s invoice.
The removed line scoped the lookup with organization=org. The replacement uses only the invoice ID, removing that boundary.
invoice_id = 1042owner ≠ requesterExample finding · original changed line 43
Original change shown. Fixes are requested separately.
That is the handoff: the changed line, the consequence, and a next step.
Try it on your repository02 / Deep review · opt-in beta
Follow callers, imports, and surrounding code. Deep review investigates beyond the changed lines, then checks the candidate findings in a separate verification phase.
Context plan / example paths
Tenant filter removed from the lookup.
Trace the organization supplied by the request.
Check whether the model scopes the query.
Suggested starting points. Full snapshots remain available.
The context plan prioritizes changed files, outgoing imports, and incoming callers for investigation.
See how a finding becomes a proposed fix →Opt-in beta for eligible repositories. Broader discovery can produce more false positives; standard review remains the merge-gating review.
03 / Auto-fix, with a clear handoff
Scope the change. Inspect the proposal. See what was checked. Keep the decision to ship in your hands.
Proposed fix
Limit the invoice lookup to the current organization. Keep the change focused on the finding.
Example proposal and checks.
No code is executed in this demo.
The proposed fix restores the filter removed in the original change.
A different organization’s invoice is returned.
expected: Invoice.DoesNotExistRegression reproduced before fix · YESThe scoped lookup rejects the same request.
Invoice.DoesNotExistCross-organization lookup blocked · PASSEvidence ready for inspection.
Your review is the next step.
Illustrative results for this concept. A live proposal would link to its actual test evidence.
Explore the intended end-to-end experience. Verification shown here is illustrative.Open your workspace →
04 / Built around your team
Explore the context, challenge assumptions, and assess code quality. Give your team a clear place to start its review.
Review the change in context, so findings explain the consequence as well as the code.
Keep severity, evidence, and fix planning together. Spend your attention deciding what to do.
Inspect a finding, request a focused fix, and review the proposal before it ships.
05 / Deployment on your terms
Our direction: start hosted, bring your own runners, or self-host the platform. Choose the boundary that fits your team.
Code Voucher infrastructure
Your configured model connection
Connect a repository and use hosted execution. Bring your own API key or supported subscription.
06 / Bring the AI you already use
Bring your own key or supported subscription. Keep the model relationship you already have, and make it useful across your reviews.
Connection preview / illustrative
EXAMPLE ONLY / NO CREDENTIALS COLLECTED
Your model usage is billed through your provider. This example does not collect credentials.
Per-repository spending, model choices, and review limits—so more automation comes with clearer costs.
07 / Open-source release planned
Review infrastructure deserves to be inspectable. We want teams to understand the system, extend it, and keep their options open.
Open-source release and self-hosting are being shaped.Inside Code Voucher / architecture sketch
Back to the work that needs you
Connect a GitLab repository. Open a merge request. Get evidence and a focused place to start your review.