Step 01
Install on GitHub
Add the Jevlit GitHub App to the repositories you want reviewed. Install opens at launch — the waitlist decides the order.
Meet Jevlit
Code review made cheap.
56 real bugs from BugsInPy, 17 projecten. Jevlit caught 13 and never alarmed on the fix — for $0,00015 per diff.
56 echte bugs uit 17 open-source projecten. Jevlit ving er 13 en sloeg nooit alarm op de fix. Selectie: kleine fixes in één bestand.
Source data: results/jev-prepush-mvp/suite-E/report.json · measured 2026-09-19
Kosten zijn tariefafgeleid ($0,042 per miljoen input-tokens, output gratis), geen facturen. Enkele runs, kleine n; zie de intervallen. Volledig audit-spoor: docs/jevlit/HARNESS-REVIEW.md.
How it works
From install to review in three steps
Step 02
Open a pull request
Work as usual. Every opened or updated pull request is picked up automatically — nothing to trigger by hand.
Step 03
Get review in seconds
Findings arrive as one review comment with inline notes on the flagged lines, plus a status on the head commit. Advisory only — never an approval.
Product tour
See what lands on your pull request
The review lands on your pull request
Every scan posts one review comment and a commit status on the head commit. No new tab to watch, no report to fetch.
Measured, not promised
Four numbers we can prove
- 0 alarms
- on 56 real fixes (Suite E)
- $0,00015
- per review on real code
- 0,69 s
- median scan latency (p50)
- 56 bugs
- BugsInPy, 17 projecten tested
Frozen protocol, offline reproducible evidence
Source: BugsInPy, 17 projecten, measured 2026-09-19 · Costs: docs/jev-prepush-mvp/tables.md · Method in the docs
Why Jevlit
Built for the pull-request flow
One frozen protocol
Every scan runs the same frozen question set at the same frozen threshold, so results stay comparable from the first pull request to the latest — and every figure on this page points at the offline audit trail.
Read the methodWorks where you work
- GitHub App — review comment, status, inline notes
- Advisory pre-push hook — same engine, before you push
- Command line — plan without API calls, review with
- Claude Code skill — findings back in context
- Codex and opencode hooks — same verdicts, your runner
Integrations ship at launch. The documented engine commands are on the console install page today.
Install optionsWhat Jevlit measures — and what it does not
Changed functions only, bounded windows, six independent questions per scope. Small, function-local bugs are the home turf; reachability across a whole program is explicitly out of scope.
TransparencyCheap enough to run everywhere
Per diff
$0,00015
Per push
$0,00009
kosten (USD, log-schaal)
Echte code: $0,0179 / 122 diffs.
Kosten per review op echte code en in de hooktest. Tariefafgeleid — geen factuur.
Kosten zijn tariefafgeleid ($0,042 per miljoen input-tokens, output gratis), geen facturen. Enkele runs, kleine n; zie de intervallen. Volledig audit-spoor: docs/jevlit/HARNESS-REVIEW.md.
Quiet on ordinary commits
Bovengrens: een gewone commit kan zelf een bug bevatten. Van de twee alarmen lijkt er één op een echte gedragswijziging te wijzen.
Kosten zijn tariefafgeleid ($0,042 per miljoen input-tokens, output gratis), geen facturen. Enkele runs, kleine n; zie de intervallen. Volledig audit-spoor: docs/jevlit/HARNESS-REVIEW.md.
Private beta
Access opens in waves. Join the waitlist and start with €3 in credits when your workspace is let in.
Join waitlistTeam
A small team, a frozen engine
Jevlit is built and operated by a small team. The review engine is frozen — protocol, model and threshold are pinned — so trust does not depend on who is on call. Questions about access go through the waitlist; questions about the method are answered in the docs.
Ready to try Jevlit?
Jevlit is in private beta. Join the waitlist — new accounts start with €3 in credits when access opens.