Impact vs. SonarQube, CodeRabbit, and Codacy

We get asked how Impact compares to the usual names. The honest answer: we're playing a different game.

• SonarQube / Codacy grade code quality within a repo. Excellent at it. Blind across repo boundaries and silent about the future.
• CodeRabbit reviews the diff with an LLM. Useful — but it's reviewing text, not a real cross-repo dependency graph.
• Impact holds the whole estate as one graph. We answer what breaks in another repo if you merge this, flag drifting contracts in the PR, forecast the next hotspot, and keep a ledger proving the prevention.

If your systems are more than one repo — and they are — the cross-repo layer is where the expensive outages hide, and it's exactly the layer single-repo graders can't see.