For the people who ship it
Impact, per merge request
Not “which tests failed”. Which parts of the product this change can reach, before anyone runs anything.
One request against BookStack, measured by the map
A real request against a real product. The map knew what it touched before anyone opened the diff.
The map · hover or tap a feature
What it is reading
Your code, not your test suite
The routes it found
Controllers, routes and their anchors are read out of the repository at a pinned commit. No annotations to add, no SDK to install.
What the change touched
The diff is matched against the files each feature is anchored to, so the footprint is a fact about the code, not a guess about intent.
What still has no cover
A feature with no scenario behind it is drawn as empty rather than quietly skipped. The gaps are the point.
Want this on your product?
We are building the first version with a handful of teams. Tell us what you test with and what breaks.