Getting started

Learn how to setup a SourceLevel integration in your organization, and start collecting metrics.

Our Solutions

Built for engineers, by engineers. We have been CTOs, managers and software engineers in the past. We have helped organizations scale their software teams. We know their struggle because it is ours too.

We are building the platform to help technical people manage their teams. We are building the “how” teams should operate in a post-agile world.

SourceLevel brings Engineering Ops Metrics to your workflow, including Pull Requests Metrics, DORA Metrics, Collaboration Metrics and more.

Available Metrics

SourceLevel brings Engineering Ops Metrics to your workflow, including Pull Requests Metrics, DORA Metrics, Collaboration Metrics and more.

Work in Progress

• Drafted Pull Requests
• Time from First Commit to Draft
• Time from Draft to Open

Ready for Review

• Opened Pull Requests
• Time from First Commit to Open

Review Process and Engagement

• Reviewed Pull Requests
• Time to Engage
• Engaged Pull Requests
• Comments per Pull Request
• Time to Discuss
• Reviews per Pull Request
• Time to First Review
• Approvals
• Request Changes
• Comments

Waste

• Closed Pull Requests
• Time from Last Engagement to Close
• Time to Close

Deliveries

• Merged Pull Requests
• Time to Merge
• Time from Last Review to Merge
• Commits per Pull Request
• Added Lines of Code per Pull Request
• Removed Lines of Code per Pull Request
• Total Changed Lines of Code per Pull Request

Frequently Asked Questions

How to remove dependabot PRs from metrics?

You can filter by team, them the dependabot PRs will be ignored.

Which git hosting solutions does SourceLevel support?

Currently SourceLevel supports GitHub® and GitLab® (Gitlab.com and Self Hosted). We have plans on adding Azure DevOps support in the future. If you use other git hosting solution, please let us know.

Does SourceLevel work with GitHub® Enterprise?

Currently no - SourceLevel only supports GitHub.com for now.

Why doesn’t SourceLevel measure averages?

SourceLevel prefers using percentiles instead of averages because averages hide too much information when working with metrics that vary too much, such as velocity.

What do 75th and 95th percentile mean?

Let’s see an example to understand better what they mean. If your organization’s Time to Merge is 14 hours, it means that 75% of all Pull Requests merged in the period was merged up to 14 hours.

The same applies to the 95th percentile. So whatever the metric is, the 95th percentile means that 95% of all analyzed data are below that number.

Why does SourceLevel use 75th and 95th percentiles?

The 75th percentile gives more visibility to the engineering team. It’s a great compromise between optimistic and realistic views. It’s become almost an standard for anyone using metrics for process flow.

The 95th percentile shows an even bigger picture of the teamwork, excluding the 5% that can be considered outliers.

Contact Us

Have Any Questions? Get in Touch! You’ll talk with one of us. Real people, no bots.

Please visit our contact page