proofhouse · in private beta
One scorecard across every repository you own, and which way it is moving
In brief
Gives engineering and security leadership one score per repository, and one across the portfolio, that a missing scanner cannot flatter. The trend shows whether the estate is getting better, and the code never leaves the teams' own CI.
Portfolio-wide security and quality posture across every repository an organisation owns. Teams run gandalf in their own CI and push the JSON run record here, where it is stored, projected, aggregated and trended.
What it does
- Nothing runs your code on this side: no clone credentials, no scanner licences, near-zero compute
- A gate whose scanner was missing is reported unavailable rather than counted as a pass, so the score cannot flatter you
- Cross-repo finding groups built on gandalf's versioned fingerprints, so suppressing something once settles it everywhere
A closer look
Select any screenshot to enlarge it.
The proofhouse.cloud landing page
The Proofhouse demo overview, read-only, on an invented organisation
The fleet grid in the Proofhouse demo
The whitepaper behind it
The problem it measures, the method behind it, and what it deliberately does not do.