A user is someone who has login access to Sleuth. A developer is someone who contributes code into a source repository under your organization in Sleuth.

Sleuth charges by user, not by developer. Suppose you have an engineering organization split into two teams, and each team has one manager and 5 developers. With our Standard plan, you can purchase a two-user subscription for the two managers, and in Sleuth they will be able to view the contributions of the ten developers.

Yes, this is very common among Sleuth customers. They have found that giving developers agency to find and fix inefficiencies is key to continuous improvement culture. After all, developers often know best where the bottlenecks lie and have a strong incentive to fix issues that encroach upon their flow.

In addition to insights on bottlenecks, Sleuth comes with features developers use daily - such as deployment tracking and notifications, environment drift detection, workflow automation, and more.

We do not limit the number of teams or repositories you can have in Sleuth. Sleuth accurately models how you work today, without forcing you to first make changes to your team or codebase structures or development workflows.
‍
For large organizations, we recommend the Enterprise plan. It includes the ability to see organization-wide trends, compare teams and projects across organization, automatic syncing of team structures, premium support, and more.

Data security is a top-level priority because we understand the level of trust customers put in us when they connect key systems together with Sleuth. We collect and store only the necessary metadata related to your deployment process, such as PR titles and commit messages, and follow best practices to safeguard such data.

Sleuth is SOC2 Type II compliant. Please see our Trust page for complete information on data security, compliance, and privacy policy.


‍