- Product
- Pricing
- Customers
- Learn
BlogInsights for software leaders, managers, and engineers
ChangelogCheck out our latest product updates and improvements
Engineering Unblocked↗Catch bi-weekly interviews with software leaders
BenchmarksFind the biggest opportunities for improvement
Book: BuildRead for free, or buy a physical copy or the Kindle version - About Us
- Careers
The healthy alternative to traditional Git analytics
Forget about toxic Git statistics. Instead, focus on improving software development productivity with a balanced set of metrics.
Trusted by effective engineering organizations
Git analytics, the Swarmia way
Connect the dots between your version control and issue tracker
Adopt healthy, research-backed habits and track progress
No harmful leaderboards or data on individual performance
Much more than a Git dashboard
Drive positive change with Working Agreements
The big problem with most Git analysis tools is that they don’t help teams to make concrete improvements.
Working Agreements in Swarmia, on the other hand, encourage your team to adopt healthy habits to limit work-in-progress, increase collaboration, prioritize code reviews, and more.
Get holistic insights from Git and your issue tracker
Instead of only surfacing simple Git repository statistics like commits and PRs, Swarmia combines useful Git-based metrics with data from your issue tracker.
This way, you’ll be able to connect the dots between planned work with the work that has actually happened across your repos.
Improve your team’s workflows
Bookmark the pull request view in Swarmia to get easy access to all the open PRs in your team — regardless of the repo they’re in.
You can also turn on handy notifications that allow you to quickly react and reply to comments in GitHub without ever leaving Slack.
It’s hard to improve what you don’t measure
Here are some of the engineering metrics you’ll see in Swarmia.
Cycle time
Understand how long it takes for your team to complete pull requests, tasks, stories, and epics.
Deployment frequency
Keep track of how often you’re deploying — and how often the deployments are failing.
Investment distribution
Know what your engineering teams are working on and establish the right balance between roadmap work and other work.
Bug Insights
Stay on top of the bugs your team is working on and the time it takes to fix them.
Batch size
Keep your batch size small to roll out features to customers faster and with less risk.
CI insights
Spot flaky tests and improve the performance of your CI pipeline.
Review time
Identify review bottlenecks and get your work merged faster.
Review rate
Maintain high code quality by maximizing the percentage of code that gets reviewed before it’s merged.
WIP limits
Allow teams to set their own work in progress limits to boost focus and productivity.
The Git metrics we don’t track
Developer stack ranking
Swarmia focuses on improving development productivity on the team and organization level. That’s why you won’t find Git commit leaderboards or other harmful activity metrics in Swarmia.
Lines of code (LOC)
Lines of code is a terrible way to measure engineering productivity. In fact, Swarmia only records lines of code in the context of batch size and code review notifications.
Code churn and rework
We believe that rewriting your own code is a perfectly acceptable way to solve complex problems. That’s why you won’t be able to track code churn or rework with Swarmia.
Explore next
Working Agreements
Tracking the right metrics is just the first step. To make sure your insights don't just sit on a dashboard, Swarmia allows your teams to set their own Working Agreements.
