Diligence that reads the code. Private repositories included.

Repo Man writes point-in-time technology diligence briefings for GitHub repositories, public or private. A quick scan finds what to worry about. A deep dive reads those areas and writes findings tied to quoted code. Ask the code answers your own questions from what the repository actually contains.

Request early access Sign inEarly access is by invitation.

Who it is for

Anyone who has to form a view of a codebase quickly and stand behind it later.

Deal teams

Private equity, venture and corporate development teams who need a technical read on a target before the term sheet, not after close.

Diligence advisors

Technical advisors who want page one in minutes and evidence they can quote, so their hours go to judgment instead of reading.

Companies being diligenced

Founders and CTOs who want to see what a buyer's team will find before the data room opens.

What you get

Each briefing is a snapshot of the repository at the moment it runs. You start with a quick scan, go deeper where it points, and ask questions whenever you like.

Quick scan

Page one of the briefing: red flags and things to watch, from checks across the repository and a model pass over the leads worth a second look.

Deep dive

Reads the flagged areas and writes findings. Each finding quotes the code it rests on, with the file and lines, so anyone can check it.

Ask the code

Questions in plain English, answered from what the repository contains. When the answer is not in the code, it says so and says what it searched.

Bring your own keys

Repo Man runs on your own Anthropic Claude key (OpenAI keys work too) and a read-only GitHub token. Model usage is billed to your account with the provider, at their prices.

How your code is handled

Your code is read for your run and then deleted, and every briefing shows you where content went.

Cloned into a temporary workspaceUsing your read-only GitHub token, which is handed to git without appearing in URLs or command lines.
Checked and readChecks run inside the workspace. The parts that need judgment go to the model.
Sent only to the model provider you choseExcerpts and your questions go to Anthropic or OpenAI under your own key, and that provider's API terms apply to them.
Workspace deletedWhen the run finishes, the cloned source is deleted.
Briefing saved to your accountBriefings include the excerpts they quote. Each user sees only their own.
Run details recordedEvery briefing ends with run details showing where content was sent and confirming the workspace was deleted.

Your keys

Your GitHub token and model key are stored encrypted, and only the worker that runs your briefings can unseal them.

A sample briefing

Every briefing follows the same shape.

Briefing outline

Page one: Red flags and things to watch, each with the evidence behind it.
Findings: What the deep dive found, with quoted code, file paths and line numbers, and why it matters.
Partner summary: A plain-English version for people who will not read code.
Run details: The models used, where content was sent, and confirmation that the workspace was deleted.

A full sample briefing on a well-known public repository will be published here.

Early access

Repo Man is in early access, and invitations are open to deal teams, diligence advisors and companies preparing for diligence. To request one, email earlyaccess@repoman.tech.

Repo Man comes from the technical diligence work Central Scott LLC does for private equity, where a quick, defensible read of a codebase is the whole job.