You decide when a pull request gets reviewed.
You comment @useboson review on a pull request. Boson reads that diff once, traces the changed lines through their callers, and quotes exactly where it breaks. Ask again next time you want another pass.
Boson is in early access: sign in with Google to request access.
example-dev commented just now
@useboson review
useboson commented moments later
blockerpayments/retry.py:142
if retry_count < MAX_RETRIES: schedule_retry(job)Path
- payments/retry.py:on_decline changed line
- payments/webhooks.py:replay caller
- payments/charge.py:capture failure
This runs two lines before the idempotency key is set below it. A retry scheduled in that window double-charges the customer when the webhook replays.
This comment does not approve or block the pull request.
Three steps to your first review
Sign in with Google
At app.useboson.com.
Start the free trial
5 reviews over one month. A card is collected to start it. The trial itself is never charged.
Install the GitHub App
Then comment @useboson review on a pull request.
What happens after you comment
You ask for a review
Comment "@useboson review" on an open pull request in a repo where the GitHub App is installed. There is no config file to add to the repo.
Deterministic checks run first
Boson checks the diff against the merge-base commit: is the line actually changed, does the snippet match, what does blame say, has this already been flagged. A model never sees a diff that fails these.
What's left gets read for a reason to reject it
Boson reads the change the way a reviewer looking to reject it would, following each line through its callers until it lands on a concrete, reproducible outcome.
One comment, evidence attached
Boson quotes the code and the path from that line to the failure it causes. Reading the comment is enough to check the finding yourself.
Credits, pooled at the organization
One credit pays for one review, at the same depth every time, and nothing multiplies the cost. The balance sits at the organization, shared by every developer, and drains only when someone asks for a review.
Free trial
The free trial gives you 5 reviews over one month. When it ends there is no access until you start Pro or Teams.
It runs once per customer. A card is collected when you start it, and the trial itself is never charged.
Pro
$30per month- Credits a month
- 30
- Cost per credit
- $1.00
- Extra credits
- Opt in, $1.50 each
Teams
$100per month- Credits a month
- 125
- Cost per credit
- $0.80
- Extra credits
- Opt in, $1.00 each
Enterprise
CustomQuote onlyCredits, rate and extra credits: set in your quote
What extra credits cost
An extra credit costs more than a credit inside your plan: $1.50 against Pro's $1.00, and $1.00 against Teams' $0.80.
We price extra credits that way on purpose: past a certain volume, moving up a plan costs you less than staying put and running on extras. Teams gets the cheaper extra credit as well as the cheaper included one.
How prices are set
We set these prices before we finished measuring what a review costs us. They hold even if that cost comes in higher.
Turning on extra usage
You buy a plan here, and extra usage is not part of it. If you turn extra usage on later in the dashboard, anything past your included credits is added to your next invoice.
Nothing is charged at the moment of a review, so a review that returns nothing costs you nothing.
Extra usage has three settings, and it is off until you pick one:Automatic stops extra usage once it has cost what your plan costs, so a month can at most double.Ask each time refuses any review that would use extra credits and tells you what it will cost, in credits and in dollars, before you approve it. Nothing is held while you decide.Off, the default, refuses any review past your included credits.
What you can verify yourself
We haven't run enough reviews yet to publish an accuracy number we'd stand behind, so here are none. Pull up an actual comment Boson posts and check each line below against it.
- Every finding quotes the exact code and traces a path from that line to a concrete, user-visible failure.
- Deterministic checks run before any model sees the diff: line in diff, snippet match, blame, duplicate detection.
- It's a comment. Nothing else on the pull request changes because Boson ran.
Try it on your next pull request.
Start the free trial, install the GitHub App on a repo, then comment @useboson review the next time a pull request needs someone hunting for the way it breaks.