Could my colleagues end up seeing the code?▾
Not with the Everyone or Leadership profile: a filter strips code blocks and file paths from answers and, for Everyone, names too. DeployIt also attacks each profile itself with trick questions and warns you if anything gets out. No filter is foolproof, which is why the test shows you what it managed to extract.
Who gets which profile?▾
Everyone who signs up through your company link gets Everyone. An administrator gives Developers or Leadership to whoever they choose. Signing up again with the same address never gives a broader profile.
Is developer tracking individual?▾
Yes, that is its purpose. Each tracked developer has a profile: what they shipped, reviewed, tested, fixed, and the score of their code. During the trial or on a plan, tracking starts as soon as your repositories are connected, with 6 months of history: inform your teams beforehand, or turn statistics off. The terms set out the framework, and we give you what you need to inform people, including an export of one person's data.
What is the code score?▾
A language model reads each commit and scores it from 1 to 5 on five criteria: correctness, maintainability, robustness, tests and security. It is read over a month, a quarter, a half-year or a year, always with the number of commits it covers. It is a clue, not a verdict.
And how is a defect counted?▾
DeployIt finds the commit that a fix came to repair. As long as only the machine has counted it, the defect is "to confirm". An administrator confirms or dismisses it; an investigation that rereads the code can only confirm it. The human decision prevails.
Does it have to be Claude?▾
Yes, to ask questions: sign-up works today from Claude (web and desktop) or from a local client such as Claude Code; Cursor and Windsurf cannot sign up yet. A data warehouse or a BI tool reads the statistics with a Data tool key.
We have several companies.▾
One account, one company per legal entity. Each has its repositories, its link, its profiles, its developers, its log and its plan; nothing passes from one to another. The 30-day trial opens once per account, with the first company; the next ones start on the free plan.
What if we stop?▾
When your subscription ends, your company moves to the free plan: nothing is erased at that moment, but developer tracking stops and the statistics close; the data is kept for its retention period. While your plan or the trial runs, you can export the statistics with a Data tool key: do it before you cancel. Each person's profile can be exported from Developers. Removing a repository from DeployIt erases its working copy and, if you tick the box, its statistics. You can delete the company once the last paid period has ended (a cancellation takes effect at the end of the period): access is cut at once, then a queued job erases the data, usually within the following hours, and retries if it fails. The daily database backups hold the data until they rotate: DigitalOcean keeps them for seven days.