Private beta · wave 2 opens Jan 2027

Code review that reads the whole repo

Kestrel reviews every pull request with your entire codebase in context, and only speaks up when a change breaks something the diff can’t show.

412 teams on the list for wave 2
Reads todayTypeScriptJavaScriptGoPython · wave 2Ruby · wave 2
How it reads

Your diff touched 3 files.
Kestrel read 2,184.

changed in the PRaffected: callers, tests, helpersread for context
Same pull request

Twenty-three nits, or the one bug.

Most review bots comment on everything they can see. Kestrel stays quiet until something is wrong, then tells you where the fix already lives.

A typical review bot

23 comments
Consider renaming grossstyle
Missing JSDoc on refundTotaldocs
This PR changes how refunds are rounded.summary
Prefer const destructuringstyle
Magic number 100style
Line exceeds 80 characterslint
Consider adding a testtests
Great job on this change!praise
Typo in comment: “refnd”style

Kestrel

1 comment
Kestrelread 42 filesBlocking

Floats lose the cent here. toCents() in billing/cents.ts already works in integer cents.

Suggested change
+ const rounded = toCents(order.total, share);
Apply suggestion
No style notes. Your linter already has those.
No summary of what you just wrote.
How it works

Ten minutes to set up. Then it just reviews.

One app on your repositories, one read of the codebase, then a comment only when a change breaks something.

01

Install the app on your repos.

One GitHub or GitLab app. Pick the repositories; Kestrel asks only for what a reviewer needs.

  • No CI changes
  • No config file to start
02

It reads the whole repository once.

Kestrel maps every caller, import and test, then keeps the map current as you merge.

  • A mid-size repo maps in about four minutes
  • Code is deleted when the review ends
03

It reviews every pull request.

Comments land in the pull request like a teammate’s. Blocking issues fail one check; notes never do.

  • Under a minute for most pull requests
  • Reply to it, and it answers in the thread
Wave 1, in numbers

1.4 comments per pull request, across forty teams.

northwind/checkout · Kestrel reviewsLast 7 days
#490Split refunds by line itemReading 1,204 of 2,184 files
#489Add Apple Pay to checkoutPassed, no comments41s
#488Bump stripe-node to 17.4Passed, no comments12s
#482Fix currency rounding on refunds1 blocking: toCents() in billing/cents.ts already works in centsOutside the diff38s
#486Retry failed webhooksPassed · 1 note on the backoff cap52s
#485Copy for the refund e-mailPassed, no comments9s
#484Move order dates to utc()1 blocking: invoices/issue.ts still calls new Date()Outside the diff1m 04s
#483Filters on the orders tablePassed, no comments47s
1.4 comments per pull request in wave 131% of blocking comments pointed outside the diff0 style notes, ever
It caught a timezone bug in a file nobody had opened in two years. That one comment paid for the beta.
Maya ReyesStaff engineer, Northwind
The first review bot we turned on that people kept on. It doesn’t talk unless it has to.
Jonas TveitPlatform lead, Fjordpay
Our seniors were the only ones who knew where the money helpers lived. Now every pull request gets that review.
Aiko KimuraCTO, Ledgerline

SampleSample quotes and numbers. Replace them with your own before you publish.

The beta

We let teams in a wave at a time.

Each wave gets a direct line to the people building it. Places go in the order people join.

Sep 2026

Wave 1

Forty teams on TypeScript and Go, reviewing real pull requests every day.

Closed
Jan 2027

Wave 2

Python and Ruby join, and GitLab support lands. This is the list you’re joining.

Open now
Later in 2027

Public

Beta teams keep their price for a year.

12 monthsat the beta price after launch
Date to come
Questions

Before you join

Anything else goes to the team directly: reply to the confirmation e-mail.

Does my code leave our servers?

Code is read in an isolated workspace, used for the review and deleted when it ends. Nothing is kept to train a model.

Which languages work today?

TypeScript, JavaScript and Go in wave 1. Python and Ruby arrive with wave 2.

What does it cost?

Nothing during the beta. We’ll publish pricing before the public launch, and beta teams keep their price for a year.

Does it replace human review?

No. It catches what a reviewer can’t see from the diff, so people can spend their review on design and intent.

How many e-mails will I get?

One to confirm, one when your place opens. No newsletter.

Wave 2 · January 2027

Get on the list for wave 2.

Places open in the order people join. One e-mail when yours is ready.