Borehole
Technical due diligence, read from the repository itself
Borehole is technical due diligence for software acquisitions and investments, read from the repository itself.
Paste a repository address. Borehole reads the git history and the working tree, runs 106 diligence checks and rates seven dimensions a deal team cares about: architecture, engineering process, key-person risk, product maturity, security, operations, and fit with the acquirer. Every finding cites the commit, path and lines it rests on, or, when something is missing, what was looked for. What the code can't answer becomes a question for the room.
Public repositories are free. Private repositories are read on your own machine by the collector (pip install borehole), which sends facts and short excerpts of up to 120 characters where a check matched, never whole files. Its dry run prints everything it would send, first.
Built by Andrew Edmond: technical diligence across dozens of Amazon deals; CTO, Woot.com.
Features
- 106 diligence checks, rating seven dimensions a deal team cares about
- Every finding cites the commit, path and lines it rests on
- What the code can't answer becomes a question for management
- Reads GitHub, GitLab, Azure DevOps, Bitbucket, Codeberg, Gitea and SourceHut
- Private repositories read on your own machine by the collector; its dry run shows everything it would send
Use Cases
- Founders preparing to sell or raise, who want to see what a buyer's adviser will see
- Buyers and investors who want a first read on every target before paying for a full review
Comments
Hi Fazier, I'm Andrew. I've done technical diligence on software acquisitions for years, including dozens of deals at Amazon. The first week of every deal went the same way: read the repository, find out who wrote what, check the licences, and list the questions for management. Borehole does that first read. Paste a public repository and you get a report: 106 checks, seven dimensions rated, and every finding tied to the commit, file and lines behind it. What the code can't settle becomes a question to ask in the room. For private code, the collector runs on your own machine and sends facts and short excerpts, never whole files. Its dry run shows everything it would send, first. It's in beta, and public repositories are free. Tell me what it gets wrong: I read every reply.
Premium Products
Sponsors
Buy
Makers
Makers
Comments
Hi Fazier, I'm Andrew. I've done technical diligence on software acquisitions for years, including dozens of deals at Amazon. The first week of every deal went the same way: read the repository, find out who wrote what, check the licences, and list the questions for management. Borehole does that first read. Paste a public repository and you get a report: 106 checks, seven dimensions rated, and every finding tied to the commit, file and lines behind it. What the code can't settle becomes a question to ask in the room. For private code, the collector runs on your own machine and sends facts and short excerpts, never whole files. Its dry run shows everything it would send, first. It's in beta, and public repositories are free. Tell me what it gets wrong: I read every reply.
Premium Products
New to Fazier?
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved