For commissioners

Understand and verify the software you're paying for.

You're paying a freelancer, an agency, or a technical cofounder to build it. You want to understand what you're getting, measure it against what was agreed, and walk into every check-in with more than a feeling.

Code custody

Your code stays yours. We name everyone who touches it.

Read-only GitHub access. The temporary clone used for analysis is deleted when the run ends. Guides retain only the excerpts cited as evidence — and you can delete everything, self-serve, anytime. Every processor is disclosed on our custody page before you connect anything.

Read the full custody disclosure →

What an audit shows you

Evidence a non-reader of code can act on.

You don't need to read source files to understand an audit guide. Each finding states what happened, what it threatens, and what to decide — in founder language, with evidence you can drill into when you want detail.

  • What was promised in the planning documents
  • What was found in the repository at a pinned snapshot
  • What is verified, unverified, or missing — with no scores or false precision
  • A decision brief grouped by product impact, not technical jargon
[ placeholder — screenshot of stakeholder edition ]

Stakeholder editions

Share a clean copy with your developer or cofounder.

When you need someone else to see the same map, share a stakeholder edition — a daylight-readable copy that needs no login. Private by default; shared only when you say so. Findings you flag for suspected accuracy are excluded from new editions by default.

Walk into your next check-in prepared.

Connect the repository and planning documents for the project you are commissioning. Your first Plan guide is free.