Priced per engineer who ships.

It's the number we watch most closely. Check-ins take under two minutes, come at most three times a week by default, can be skipped without penalty, and every answer gets feedback worth reading.

Those tools infer knowledge from git history: who wrote or reviewed a file. Depth starts there too, as an estimate, then verifies it by asking people to explain their own changes, and lets the evidence fade unless it's refreshed. Authorship says who typed. An explain-back shows who understands, which matters more now that AI does much of the typing.

Review checks the code before it ships. Depth checks that someone understands it afterwards, and keeps checking. As AI makes changes larger and reviews faster, that second check is the one disappearing.

No, and that's built into the product rather than promised. Answers and feedback are visible only to the engineer; managers see module status and counts. Our terms forbid using Depth to evaluate, rank or pay anyone.

To write questions, it reads the diff of a merged pull request and keeps only the short excerpt shown with a question, for 14 days at most. The map comes from commit metadata, never file contents. Access is read-only; Depth writes only its own check on pull requests. Everything it reads and keeps.

Someone with admin rights on your GitHub organisation installs the App and chooses the repositories. Everyone else just signs in with GitHub.

An estimated map within the hour of installing. The first week is calibration: check-ins go to the modules the map is least sure about, and verified status replaces the estimate module by module.

Not yet: GitHub today, with Slack optional. GitLab and Bitbucket are on the roadmap; tell us if that's what's holding you back.

Claude, by Anthropic, through its commercial API, which doesn't train on customer data. Every question is drafted, then checked in a separate review pass before anyone sees it.

Your team moves to the Free plan and keeps its map. Uninstall the GitHub App and Depth stops reading anything; ask us and we delete everything, as the privacy policy spells out.

Not yet. We publish exactly what we store and for how long, which never includes your code, sign our standard data processing agreement on request, and will go through SOC 2 when a customer's security review needs it. Trust and security.

It's the share of your critical modules that at least two current people have shown they understand, with evidence that fades unless it's refreshed. The method is an open specification. Read it.