Metrics for data-driven engineering leaders

get it

GitPrime analyzes your codebase, for unprecedented reporting on the software development process. We help data-driven engineering understand work patterns and the people-side of shipping great software.

Around the web


  • Jake PetersCEO & Founder @HelpDocs

    Gives insane visibility into the performance of your engineering team


    None that I've seen. It's a killer product, and the team's made awesome progress over the past few years.

    When I was getting started as a founder, I was admittedly a lacklustre developer. To be fair, as a founder now, I'd still say I was pretty average. That said, I can crack out some decent code when the time comes.

    But y'know what's even harder than writing consistently decent code yourself? Making sure your dev team's writing consistently decent code too.

    GitPrime gives you high level insights into your team's performance, actionable insights and reports. When something catches your eye you can dig in and explore more. Invaluable for anyone running a dev team, no matter your coding experience. Highly recommended.

    Jake Peters has used this product for one year.
  • James MundyCTO @ SailConnect

    Fantastic product with really informative reporting into where your developer's time is being spent.


    It can take a while to start to understand some of the terms and charting but thankfully it is accompanied by good documentation

    I first discovered GitPrime through ProductHunt shortly after it launched and used it as an early customer while working on my first startup. We were unusual in that we were a small team of two developers and while the product is designed for larger and more established teams, we found the reports really useful to analyse our work and see just how much time we were spending contributing new code, dealing with technical debt and refactoring legacy code.

    James Mundy has used this product for one year.


You need to become a Contributor to join the discussion - Find out how.
Charles Naut@charles_naut
Looks cool! Do you support github for enterprise?
Travis KimmelMaker@traviskimmel · CEO, GitPrime
@cnaut Yep! We have run into the occasional wrinkle if you there are specific firewall settings or something similar in play, but we support SSH with port forwarding on a repo-by-repo basis, which works in 95%+ cases. Feel free to ping me directly if you run into anything and we'll work through it.
Ben ThompsonMaker@thebent · Co-founder & Product @GitPrime
@charles_naut yes, we have a full featured on-prem version with all the extras you'd expect (SSO, etc)
Randy Skopecek@rskopecek
To make sure I'm understanding correctly, the analysis is done via git-level information and doesn't get into any code-level analysis static or otherwise (implemented a bad pattern, untested code, etc)? Looks really cool and an easy sell.
Ben ThompsonMaker@thebent · Co-founder & Product @GitPrime
@rskopecek you nailed it! ^^^ I'll let @traviskimmel jump in here to elaborate.
Travis KimmelMaker@traviskimmel · CEO, GitPrime
@rskopecek Exactly. Internally, we think of our mission to report on the work process (stuff in the pipeline) vs the work product. We've steered away from things like cyclomatic complexity for now, though that is also a fascinating body of work.
Randy Skopecek@rskopecek
@traviskimmel @rskopecek Is there a way to provide hints to help extend the determination ability? For example, if I add a word (or js expression) that the code is checked against it can be flagged as more technical debt. Thus when code is changed and that expression is now false...the technical debt is reduced.
Travis KimmelMaker@traviskimmel · CEO, GitPrime
@rskopecek So, something similar to how JIRA integrates with GitHub and ties commits to tickets, but at the level of code? I like it -- going to put that on the roadmap.
Randy Skopecek@rskopecek
@traviskimmel @rskopecek That could be cool too :-). I was thinking along the lines of string level searches. For example, in .Net if a developer leaves //todo: or //hack: which are code-level comments it could be considered technical debt. So as a lead, I could add a hint expression into GitPrime to say if codeFile.Contains("//hack", "//todo") then tag that line/file as increasing technical debt. I can see where static analysis and such would be beneficial to analysis. However, even just having some string level search hints would be of value without adding the overhead of doing language/tech level compilation and such. Make sense?
Travis KimmelMaker@traviskimmel · CEO, GitPrime
If you are anything like us, you have probably had one of those software projects in your career that falls into the “worlds worst” category. Either the specs are laughable or non-existent, the communication lines between engineering and the business are broken beyond repair, and nothing seems to be working. These projects suck. They have happened to all of us, and it feels like nobody knows how to dig out. GitPrime was founded to provide unprecedented visibility into software development. Whether it is a team of 10 or 10,000 — GitPrime uses data buried deep in the code repository to provide real and immediate insight into the software development process for both technical and non-technical leaders. We never wanted to suffer thru the “world’s worst” project again, and now we can share with you a view into engineering that will change your life. Built by engineers, for tough engineering challenges, GitPrime will help you sleep better knowing that your team is on task, on target and cranking code. We are happy to offer all our Product Hunt friends 40% off the GitPrime Subscription! Thanks, drop me a line here with thoughts/questions.
Zack Shapiro@zackshapiro · Core Team at Nano
This looks really interesting, just shared with my team at Splash. Nice work guys!
Ben ThompsonMaker@thebent · Co-founder & Product @GitPrime
@zackshapiro thank you for the kind words. Loving the custom events experiences you're creating with Splash. We’d be honored to be a part of that if GitPrime could help. Our goal is to be especially good at help with that 'scaling pinch’ that everyone hits when growing a team past 6-7 developers. It’s easy to lose the small team intuition about how everyone is doing, and solid analytics can be great answer to that.
Spencer Norman@spencernorman · Software @ Reaction Commerce
Very cool. I'm curious how you measure risk patterns? Seems like an incredibly useful feature - it would be very helpful to know which commits need extra scrutiny, but the site is light on details about how it determines risk.
Travis KimmelMaker@traviskimmel · CEO, GitPrime
@spencernorman There's a bit of secret sauce going on here, and we're constantly improving these sorts of high-level metrics. Broadly speaking, we draw from academic literature on thing like what makes commits "big" (not just lines of code but number of distinct edit locations, for example) or "high impact" (is this big looking change really just a 4-character change that Git is thinking of as a large diff). Cross-referencing this sort of data with patterns for specific engineers, we can start to get a picture of risk. So risk might be better expressed by a narrative like, "This seems like an awfully big and high impact commit for Joe, who generally breaks work up into smaller bits."